I have two machines that can’t boot any kernel newer than 6.1.14. I’ve tried to research the problem, but the only similar bug reports I’ve been able to find seem irrelevant since I’m not using nvidia or realtek hardware (as most people reporting similar issues are).
Machine 1: ASRock X370 Gaming K4, Ryzen 7 1700, AMD Radeon RX 480. Disk encryption with luks. UEFI mode.
Machine 2: Gigabyte AX370 Gaming K7, Ryzen 5 1400, AMD Radeon RX 560. No disk encryption. BIOS mode.
I’ve been running Fedora on both machines for years, however both have had a fresh F37 install within the past 4 months. Both work flawlessly on kernel 6.1.14, but neither one can boot 6.2.7.
Machine 1: Freezes on the ASRock splash screen. Never shows luks passphrase screen. No disk activity, LED keyboard not illuminated/doesn’t accept CTRL-ALT-DEL. Requires a hard reset to access grub menu. Note that this machine also has 6.1.18 installed, and it can’t boot that kernel either.
Machine 2: After Gigabyte splash screen, kernel panic ending with the message “
---[end Kernel panic - not syncing: timer doesn't work through Interrupt-remapped IO-APIC ]---”. Able to reboot with CTRL-ALT-DEL to access grub menu.
Incidentally, I have a third machine on F37 Workstation (an Intel-based Dell laptop) that boots just fine on kernel 6.2.7.
Can anyone point me to a relevant bug report, or do I need to file a new one? Besides
versionlock-ing the one working kernel, what are my options here? I tried to build a vanilla 6.2.8 kernel based on the 6.1.14 config, but ran into an unhelpful error message and wanted to stay focused on trying to address the main problem.
EDIT: I see someone has posted a similar error message related to Silverblue. I’m using standard F37 Workstation, but their kernel panic looks like the one I’m seeing on Machine 2. This is different than what I see on Machine 1, but maybe the same cause?