kernel panics in fc6 post-2.6.20-1.2962 kernels

[smcs <darbnet@xxxxxxxxx>]

ever since yum provided updated kernels past the one listed in the subject line (so far 2.6.22.1-32 and 2.6.22.2-42) in the past week or so, I have been unable to boot, getting a kernel panic executing the init script from the initrd image, right around the command 'resume /dev/VolGroup00/LogVol01'. I have two SCSI disks and 1 IDE. sda has 2 partitions and sdb 1. sda1 (100 MB) is /boot and sda2+sdb1 (about 10G) make up my single VolGroup, which has 2 LogVols. Root is on LogVol00 and swap is on LogVol01. It seems that LVM is not being started anymore in my system (in 
2.6.20-1.2962 lvm works fine). 

there was a LABEL for /boot (LABEL=/boot) in my fstab which I changed back to /dev/sda1 as I read in one post during my googling that there was some sort of new issue with LVM and labels, but that has not affected the problem.

I looked at the difference between the two init scripts from the initrd image (2962 and 32) and found only one new module being loaded:

echo "Loading mbcache.ko module"
insmod /lib/mbcache.ko 

ahead of kbd.ko. I have been unable to find out more about what mbcache is or why it was added.

The only other obvious difference i saw was in the grub entry added for the new kernel. Whereas the entry for the 2962 kernel referenced root=/dev/VolGroup00/LogVol00 in the kernel statement, the entry for the 32/42 kernels specifies root=/dev/mapper/VolGroup00-LogVol00. I'm not sure what, if any, difference this makes but it is a change.

can anyone shed some light on what's going on here? From my looking, I am not the only one having this problems since these new kernels were released.
-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list