Kernel panic after 9.4 kernel="/boot/vmlinuz-5.14.0-427.13.1.el9_4.x86_64"

When I boot using kernel=“/boot/vmlinuz-5.14.0-427.13.1.el9_4.x86_64” I get a kernel panic on boot. If I use kernel=“/boot/vmlinuz-5.14.0-362.24.2.el9_3.x86_64” everything start up just fine. Not sure what next steps I should take to troubleshoot. I am running as a VM on esxi.

1 Like

Do you perhaps have any DKMS or kmods that didn’t finish compiling after you updated? I know some of the Nvidia stuff from rpmfusion runs compilations in the background even after dnf is complete, for example.

No DKMS, and no kmods. I did upgrade another vm in another cluster from 9.3 to 9.4 and I have the same kernel panic on boot.

I’m having similar problems. When I boot to /boot/vmlinuz-5.14.0-427.13.1.el9_4.x86_64 as a VM on Microsoft Hyper-V 2022, the Almalinux server hangs. I have to boot back to /boot/vmlinuz-5.14.0-362.24.2.el9_3.x86_64 to get it operational again.

1 Like

I’m experiencing a similar issue, a server patched earlier this evening and locks up when I get to the login prompt. I switched to the previous kernel and no issues as of yet.

I think I tracked my kernel panic down to an incompatibility between the new kernel and Crowdstrike.

1 Like

Just a quick followup, Crowstrike sensor 7.13 or newer will have Kernel Panics with kernel 5.14.0-427.13.1.el9_4.x86_64. Short term, I am rolling the sensor back until I get a new sensor.


Thanks for this! We’re also running crowdstrike on our servers so I’ll try a rollback.