Description of problem: panic on boot, quick look over the spagetti on screen I see a message about "error trying to sync" kernel-smp-2.6.14-1.1696_FC5 boots fine I can try to get a digicam screencapture again if you want it, but seem to be very bad at that. -jef
are you using raid by any chance ?
nope a custum LVM partitioning but no raid. df -h: /dev/mapper/VolGroup00-LogVol00 5.8G 4.7G 864M 85% / /dev/hda1 99M 77M 17M 82% /boot none 251M 0 251M 0% /dev/shm /dev/mapper/VolGroup00-LogVol02 15G 10G 3.8G 73% /home /dev/mapper/VolGroup00-LogVol03 16G 9.9G 4.7G 68% /usr/local kernel-smp-2.6.14-1.1715_FC5 still fails with the same sort of error about syncing. Is this a mkinitrd problem? Should I downgrade mkinitrd to 5.0.10 and see if the newer kernels work with regenerated initrd images? -jef
might be worth a shot, there seem to have been some changes there recently which broke some peoples setups, though I've not read enough bug reports yet to get the big picture on what broke altogether.
Okay I'll report back when I get a chance to get in front of that box again and reboot it with a regenerated initrd. -jef
grrrr reverting back to mkinitrd-5.0.10 and regenerating the initrd for kernel-smp-2.6.14-1.1715_FC5 didn't help. I'm still getting a message: kernel panic not syncing bad locking or something close to that on the console during the boot up. Last kernel i was able to boot is kernel-smp-2.6.14-1.1696_FC5 -jef
The panic mentioned in comment #5 would be bug #174438. Is that the same message you reported before as 'error trying to sync'?
you can grab 1720 from http://people.redhat.com/davej/kernels/Fedora/devel/ which should have a fix for that problem
1720 works here... closing