In Fedora 32 Silverblue, I guess the Linux kernel 5.6.15-300.fc32.x86_64 crashes, because of my NVMe disk (a WDC WDS100T2B0C-00PXH0 aka WD Blue SN550 1TB).
Randomly (I assume when it accesses the file system/the NVMe SSD disk quite much, it just freezes and shows me a fullscreen error. It’s always some kind of ext4 error, but it’s a new installation, so the file system is intact.
Here are some errors:
t 4948.2505971 EXT4-fs error (device dm-2): __ext4 find_emtry-1536: inode 83829000: comm gdb-session-wor: reading directory lblock 0
I assume some kind of this also caused another error: the TPM seems to have been corrupted and I had to regenerate it.
What I actually saw is: At some boot, the BIOS/UEFI showed me a message that claimed I had switched the CPU (of course, I did not, it’s the built-in AMD Ryzen CPU) and it needs to regenerate the fTPM values or so.
As I do not have anything that relies on the TPM, I could just choose Y (yes) to regenerate it.
(Note: This happened after all photos IIRC.)
Also I’ve managed to catch dmesg output when this occured. This time, it was not noticeable in the graphically, but I could actually still use the system. However, in the background, it seems to have mounted the whole file system as readonly (and did not tell me lol) – do have a look at the end of that kernel log:
Funny how the system is still able to run when it throws all these kinds of error…
I guess debugging this is hard if you have no file system where coredumps or so could be written too. (I guess this is why the systemd coredumps fail too)
So anything I can still do here? Anything else I can provide for debugging?
And if I can, where do I report Linux kernel bugs? Just at https://bugzilla.kernel.org/ or is there some place to report kernel bugs for Fedora?
Hi! I don’t have too much to add, but I have run into this same issue myself, and did spot a couple other reports of what seem to be the same issue (one in Amazon comments, another on Reddit). Combination of a Ryzen processor and the SN550 hard drive leading to hard freezes that require holding the power button to reset. Looks like from the kernel bug you already discovered that the kernel flag resolves it as a workaround at least.
Let me know if I can add anything to your bug reports that might help out!