xeno74 wrote: Tue Feb 25, 2025 2:50 pm
You could report this to Michael Ellerman and to Rob Herring if you like.
I was thinking about this. But as I'm the only known one who currently has the issue I wanted to make sure it wasn't some fault caused by my system. I've raised issues in the past (on OS4) and found I was only one who had some issue, because I had an apparent rare hardware combination that caused it, which no one else had so it couldn't be tested and confirmed.
So, I need to track down more info, such as what kernel release it first occurred and what kernel you had compiled to correlate with it. And, I expect to submit a device tree, with what cell sizes it should have. After looking it up I've found other people, such as those working for Samsung, also faced the same issue. The code gives a warning, but it ends up worse, since it technically causes a crash. It's not a kernel panic, and recovers, but it's clearly some kind of core dump in the log.
In the meantime, I've booted and tested 6.14 RC4. On both an Ubuntu Mate install and my new Fresh Fienix. Worked fine in use. I finally created a new Fienix volume for testing using the live image. Unfortunately, Disks utility doesn't support GZ images, only XZ. Which I find strange as GZ is in more common use, so would have been convenient to use as direct image file. So I had to jump through hoops unpacking the live image to a partition, because on all my Ubuntu's I kept getting errors unpacking the image to a folder. I ended up downloading it again on my laptop, unpacking to a USB HDD, then imaging that file (more slowly) to a partition back on the X1000. I suspect it's a 64-bit GZ error as the file came up as 3GB, but it's double that. Even on my laptop (with Mint) the GZ unpack size is still wrong, even though it works, so it looks like an old issue they still haven't fixed on recent x64 builds of the Archive Manager.
