Created attachment 1953214 [details] Screen shot of kernel panic 1. Please describe the problem: kernel panic on 6.2.7 2. What is the Version-Release number of the kernel: vmlinuz-6.2.7-200.fc37.x86_64 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : vmlinuz-6.1.18-200.fc37.x86_64 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Yes, happens every time boot is attempted. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Yes. 6. Are you running any modules that not shipped with directly Fedora's kernel?: Don't think so. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. The failed boot doesn't show in kernel logs. I have only successful ones going back to 4/2022.The log is 19Mb. See attachment photo.
I can report the same failing to boot issue on our AMD-based reverse proxy. We are seeing “Kernel panic - not syncing: timer doesn’t work through Interrupt-rempped IO-APIC” when using Fedora Kernel 6.2.7-100.fc36. Machine Details. Gigabyte A320M-S2H (fully patched bios) Fedora Kernel 6.2.7-100.fc36 (also fails with 6.1.18) Fedora 36 Server 1st Gen Ryzen 1200 Processor RX550 Radeon gpu Last known working kernel 6.1.15 Related Discussion? https://discussion.fedoraproject.org/t/fedora-37-workstations-cant-boot-6-2-7/79982/3 Possibly GPU related?
Per the Fedora discussion, it appears to affect 1st gen Ryzen systems.
I cannot use the laptop with 6.2.7-200, it freezes after login: Dell Precision 7560 Fedora Kernel 6.2.7-200.fc36 Fedora Linux 37 (Workstation Edition) 11th Gen Intel® Core™ i9-11950H × 16 Software Rendering / Mesa Intel® UHD Graphics (TGL GT1) Last known working kernel 6.1.18-200
The previous commenter's issue differs from what the rest of us are seeing, as in that case, the machine boots to the login screen. For the rest of us, the kernel panics before boot up starts.
(In reply to H from comment #4) > The previous commenter's issue differs from what the rest of us are seeing, > as in that case, the machine boots to the login screen. For the rest of us, > the kernel panics before boot up starts. Please let me know how can I help. Where can I look for logs or something, I would be happy to help to make it stable since I use this OS to work.
Just to verify, this is still an issue with the latest rawhide kernels as well?
It's still an issue with 6.2.8-200.fc37. I tried running ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel`` and got "Nothing to do. Complete!". Let me know if there's a more recent kernel you need me to test, and how to go about installing it.
Hi, this continues to be an issue for me with kernel 6.2.9-200.fc37. This kernel panic condition has now been present in four consecutive updates (6.1.18, 6.2.7, 6.2.8, and now 6.2.9). If I hadn't used 'dnf versionlock' to preserve 6.1.14, I'd have two completely unbootable systems right now. Is there anything I can do to help get this issue addressed?
Issue seems to be addressed in 6.2.11, system boots normally. Thanks!
(In reply to Luis Henrique S Rocha from comment #3) > I cannot use the laptop with 6.2.7-200, it freezes after login: > > Dell Precision 7560 > Fedora Kernel 6.2.7-200.fc36 > Fedora Linux 37 (Workstation Edition) > 11th Gen Intel® Core™ i9-11950H × 16 > Software Rendering / Mesa Intel® UHD Graphics (TGL GT1) > Last known working kernel 6.1.18-200 Just to update my case here. After Fedora issued a BIOS update on my laptop, I don't have any issue anymore. Thanks
I was able to boot using 6.2.12 However, a pop-up appeared asking for my password for running /bin/sh. Not sure what that is all about but seems normal after that. Thank you for all your efforts. I like to keep up to date.
Based on the discussion linked in comment 1 and various other reports and some research, it seems like this was effecting ACPI revisions < 6.3 in certain configurations, where a bit from ACPI 6.3 not being available was interpreted as the CPUs being offline which lead to the cryptic panic here. Looks like this was fixed in 6.2.11 by: x86/acpi/boot: Correct acpi_is_processor_usable() check https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.2.11
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on 2023-12-05. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.