Created attachment 425703 [details] 1. configuration of the boot menu; 2. system info; 3. hardware info Description of problem: Booting the default kernel 2.6.33.5-124.fc13.i686.PAE results in kernel panic. The older kernel 2.6.33.3-85.fc13.i686.PAE works, though. Version-Release number of selected component (if applicable): 2.6.33.5-124.fc13.i686.PAE How reproducible: Install Fedora 13, run the update and then reboot. Additional info: See the attachment.
Created attachment 425704 [details] photo of the kernel panic
(In reply to comment #0) > Created an attachment (id=425703) [details] > 1. configuration of the boot menu; 2. system info; 3. hardware info Did you edit /boot/grub/grub.conf by hand or work was done by rpm ? There is lack of initrd entry for 2.6.33.5-124 kernel.
(In reply to comment #2) > Did you edit /boot/grub/grub.conf by hand or work was done by rpm ? There is > lack of initrd entry for 2.6.33.5-124 kernel. It was done by RPM I guess. I made no edits to /boot/grub/grub.conf since I upgraded to Fedora 13. Before, when I had Fedora 12, I added intel_iommu=off there, that's all.
Perhaps you have somehow malformed grub.conf and rpm/grubby scripts do not cope well with it. Let's check it: Copy your grub.conf somewhere. Then uninstall 2.6.33.5-124 kernel by "rpm -e". Copy grub.conf again.Then install kernel again by rpm or yum. See if there is no initrd entry. If so attach all 3 grub.conf's here. Otherwise we have to assumed initrd line was removed by mistake by you :)
Seems we really have a problem with initrd on PAE kernels, Alexjan notes it here: https://bugzilla.redhat.com/show_bug.cgi?id=605845#c6
I just installed PAE kernel and have initrd entry in grub.conf. There must be something special on your system or installation process that make no initramfs, do you have any idea what?
I don't have the initramfs.... i try to reinstall and to remove and install both version (PAE or not) I don't have the file of initramfs
Does below command gives any error: > new-kernel-pkg --package kernel-PAE --mkinitrd --dracut --depmod --update 2.6.33.5-133.fc13.i686.PAE
I have used the command that you have indicated (even if I use the 2.6.33.5-124 and not the 133).... and only with that instruction works perfectly all... thank you a lot... Now, I'm only worried that the problem will come back in next kernel release.... does it's possibile?
(In reply to comment #9) > Now, I'm only worried that the problem will come back in next kernel > release.... does it's possibile? That's I'm trying to find out, if there is some problem with installation scripts. Maybe there was no space on /boot partition ? How do you install kernel before, do you remember command you used, it was performed some kind different? Could you try remove kernel and them install it again, i.e: # rpm -e 2.6.33.5-124.fc13.i686.PAE # yum --enablerepo=updates-testing update kernel And see if that still initramfs is there.
I have a lot of space in my boot partition. Usually I have only update the system.. I Will try your advice
(In reply to comment #4) > Perhaps you have somehow malformed grub.conf and rpm/grubby scripts do not cope > well with it. Let's check it: > Copy your grub.conf somewhere. Then uninstall 2.6.33.5-124 kernel by "rpm -e". > Copy grub.conf again.Then install kernel again by rpm or yum. See if there is > no initrd entry. If so attach all 3 grub.conf's here. Otherwise we have to > assumed initrd line was removed by mistake by you :) I did that and it fixed the problem, the new kernel now boots correctly. Thanks a lot! I'm attaching kernel.tar.bz2, which contains all the 3 grub.conf files and a log of what I did in terminal.
Created attachment 427124 [details] kernel.tar.bz2 (log of successful fix of the problem and all 3 grub.conf files that existed during the process)
Comment on attachment 427124 [details] kernel.tar.bz2 (log of successful fix of the problem and all 3 grub.conf files that existed during the process)
Not found anything suspicous in Petr grub.conf's provided here. I'm not sure why initramfs was not created. Perhaps this was some script bug that is now fixed. I'm closing this bug with WORKSFORME resolution. If this will happen again, please reopen bug.