Bug 2057391
| Summary: | kexec-tools built with gcc 12 will fail kexec/kdump jumping to 2nd kernel with kexec_load interface | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Baoquan He <bhe> |
| Component: | kexec-tools | Assignee: | Baoquan He <bhe> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 36 | CC: | bcotton, bhe, coxu, mattdm, ruyang, ryncsn, xiawu |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | Flags: | bcotton:
fedora_prioritized_bug-
|
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | kexec-tools-2.0.23-6.fc36 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-07 04:18:42 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Baoquan He
2022-02-23 10:21:05 UTC
After investigation, the kdump failing to switching into 2nd kernel is caused by gcc 12 upgrading. In fedora rawhide, gcc has been upgraded from 11 to 12. Then kexec-tools built with gcc 12 will fail the swithing with kexec_load interface. With kexec_file_load interface, kdump and kexec reboot all works well. The kexec reboot with kexec_load is also caused failure by this. The root cause why kexec-tools built with gcc 12 will fail the jumping into 2nd kernel hasn't been made clear. By the way, kernel built with gcc 12 doesn't matter with kdump/kexec jumping. *** Bug 2056876 has been marked as a duplicate of this bug. *** Note: kexec reboot also fails with a reset to bios with below test steps: kexec -l /boot/vmlinuz-`uname -r` --initrd /boot/initramfs-`uname -r`.img --reuse-cmdline reboot Expect test result: reboot into new kernel without going through bios Actual result: reset to bios and a hard reboot happens. An upstream kexec-tools patch is posted this week, it will be merged soon. Hi Dave! Can you clarify what action would be helpful as a prioritized bug? Is it concern with getting that patch into the Fedora package, or with testing it? Does this affect F36 in addition to Rawhide (and if so, would a freeze exception be a good idea?)? In today's Prioritized Bugs meeting, we agreed to defer a decision on this bug pending the input requested in comment 6 https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-06/fedora_prioritized_bugs_and_issues.2022-04-06-14.01.log.html#l-72 Hi Matthew, I do not know the exact Fedora process, just add the flag so that people can be aware of this bug, and I hope we can fix the bug in F36 :) Coiby, the kexec-tools Fedora maintainer said he has merged the fixes in Fedora 36 branch and made a build today. Yes, it affect F36 and rawhide as well, I moved the bz to F36. For rawhide we can have a rebase later to include the fixes automatically. An exception is good if the process requires it to be added in F36. Thanks Dave Yes, kexec-tools-2.0.23-6.fc36 [1] has been released to fix this bug. [1] https://koji.fedoraproject.org/koji/buildinfo?buildID=1941936 FEDORA-2022-c7080eb130 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c7080eb130 FEDORA-2022-c7080eb130 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-c7080eb130` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c7080eb130 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. In today's Prioritized Bugs meeting, we agreed to reject this as a Prioritized Bug as a fix is already in the updates-testing repo and it does not seem to affect a large number of Fedora Linux users. https://meetbot.fedoraproject.org/fedora-meeting-1/2022-04-20/fedora_prioritized_bugs_and_issues.2022-04-20-14.01.log.html#l-52 FEDORA-2022-c7080eb130 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. |