1. Please describe the problem: after upgrade to latest kernel from both fedora 33 and fedora 34 kernel panic happens on boot. system is dell precision 5500 with dual cpu x5690 72G of ram 2. What is the Version-Release number of the kernel: 5.11.11-300.fc34.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 : this started happening a few kernels back on fedora 33 i tried the beta to see if anything changed it didnt. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: install latest kernel and boot 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``: havent tried will try later. 6. Are you running any modules that not shipped with directly Fedora's kernel?: no 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. there are no kernel logs but what the serial output from kernel boot up with earlyprintk enabled.
Created attachment 1768428 [details] serial console log from kernel boot up
so i update to to the rawhide kernel kernel-5.12.0-0.rc5.180.fc35.x86_64.rpm and the error still exists, I haven't hooked up the laptop to the serial to log the output but it still hangs and kernel panics.
Same problem on Fedora 33. Any 5.11.x kernel produces above error during boot. Dell precision dual xeon 5690 with 128g ram. Video of boot https://drive.google.com/file/d/1pfDAnu3DVG-V-HWVGDpWiNONZO7gZjGP/view?usp=sharing
From kernel.org ticket "Can you add "mminit_loglevel=4 ignore_loglevel" to the kernel command line and post the log please?" I don't have a way to get logs from serial port (and have not done it before), so posting in case you can do this easily.
I don't have a way to get the console output into a file, but here's the video in case that helps: https://drive.google.com/file/d/1pxIa8e9lP49_ayrPPkqb1EtPVp_U2LnD/view?usp=sharing
kernel.org ticket https://bugzilla.kernel.org/show_bug.cgi?id=213073
I logged as much as I could in the attached file. at the top of this bug. I also fixed this bug in the short term by removing numa node functionality in the bios. without numa node functionality the kernels have been booting up fine.
Created attachment 1786561 [details] reoder-memmap-init-v2.patch I've proposed this fix for the kernel.org ticket, but apparently it does not work. I'd appreciate if it could be tested with serial console enabled to see what went wrong there...
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 '34'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.