Right after I ran a “sudo rpm-ostree upgrade” and then “systemctl reboot” I got a kernel panic after the grub menu, which doesn’t ever show up on the first boot for my Silverblue and just chooses the first ostree commit, and before the LUKS2 lock screen. After a cold boot I can see the various ostree commits and choose the one with a working 5.3.16 kernel.
This has happened to me one other time on Silverblue, about a year ago, and I ditched for regular Workstation but I’d like to resolve the issue this time. I really don’t know where to begin to troubleshoot so all suggestions are open. I attached a picture of the kernel panic screen and there is some more information below, but please tell me if I can troubleshoot more to potentially repair my machine.
Please post your experience on the BugZilla report. This seems to be a bug that only affects AMD hardware with Ryzen. I’m trying to get some momentum on this thing so they will fix it.
I had the same issue with similar or identical panic screen as mpphill2.
Disabling Secure Boot in the BIOS Setup Utility allowed the laptop to boot and run without issues.
Workaround: If you want to keep secure boot enabled, boot into the 5.3 kernel and open Terminal. Run “sudo rpm-ostree kargs --editor” and add “trace_clock=local” to the line (I did it right after the word “quiet”). Run your update and boot into the new kernel with no issues.
I’ll be periodically trying new kernels without that argument and also checking the BugZilla, I’ll report back when the issue is fixed.
Workaround booting in on older kernel version. You can also increase number of kernels that are saved. I have 7 saved atm in the hopes that this issue will be resolved in a later version!
