Created attachment 641169 [details] Picture of kernel panic Description of problem: I just updated to kernel-3.6.5-1.fc17.x86_64 and found my system will not boot. It fails with a kernel panic. I have reverted back to 3.5.4-1_1 Version-Release number of selected component (if applicable): kernel-3.6.5-1.fc17.x86_64 How reproducible: Always. Steps to Reproduce: 1. Update to kernel-3.6.5-1 2. Boot computer 3. Kernel panic Actual results: Kernel panic Expected results: Computer boots successfully. Additional info: System is a ThinkPad T430. Contents of dmesg (of successful kernel) for informational purposes attached. Also contents of /proc/cpuinfo attached.
Created attachment 641170 [details] dmesg for informational purpose only (not from failing kernel)
Created attachment 641171 [details] Contents of /proc/cpuinfo
The kernel can't find the rootfs. Please verify that: 1) You have an initramfs file corresponding to this kernel version in /boot 2) The initramfs file is of similar size to the rest of the initramfs files 3) The grub or grub2 configuration file contains an 'initrd' line for this kernel.
(In reply to comment #3) > The kernel can't find the rootfs. Please verify that: > > 1) You have an initramfs file corresponding to this kernel version in /boot > 2) The initramfs file is of similar size to the rest of the initramfs files > 3) The grub or grub2 configuration file contains an 'initrd' line for this > kernel. Thanks Josh -- it the initramfs was missing from /boot . I would expect Grub to complain and not let the kernel boot.
Perhaps a coincidence, but I have experienced the same error with kernel-3.6.6-1.fc17.x86_64. As with the original reporter this turned out to be a missing initrd (and this bug was the clue leading to the solution, thanks!). Would this be the domain of yum, rpm, or dracut? Although I've just updated to another kernel using yum from the command line and the initrd has successfully generated.