Kernel Panic in F14 since kernel updated to 2.6.35.10-74.fc14.x86_64

[multipitch]

My kernel updated to 2.6.35.10-74.fc14.x86_64 sometime around the end of December 2010.
Ever since, when I reboot, I get a kernel panic message.
I have typed it in by hand below, since I can't think of any other way to retrieve it (so it might not be 100% accurate, but I did check it as best I could!)

[    1.684025] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    1.684140] Pid: 1, comm: swapper Not tainted 2.6.35.10-74.fc14.x86_64 #1
[    1.684249] Call Trace:
[    1.684382]  [<ffffffff81467e2a>] panic+0x8b/0x10d
[    1.684495]  [<ffffffff81ba2228>] mount_block_root+0x255/0x280
[    1.684605]  [<ffffffff81ba23e1>] mount_root+0x56/0x5a
[    1.684714]  [<ffffffff81ba2555>] prepare_namespace+0x56/0x5a
[    1.684823]  [<ffffffff81ba1f00>] kernel_init+0x2ac/0x2c0
[    1.684934]  [<ffffffff8100aae4>] kernel_thread_helper+0x4/0x10
[    1.685044]  [<ffffffff81ba1c54>] ? kernel_init+0x0/0x2c0
[    1.685153]  [<ffffffff8100aae0>] ? kernel_thread_helper+0x0/0x10
_

...this happens every time I reboot.

If I hold down shift when rebooting and select 26.35.10-72.fc14.x86_64, it boots fine, but it is becoming a bit irritating to have to do this.

The computer is a Toshiba Satellite A100-920 laptop with a Core 2 T5500 1.66 GHz CPU, 1 GB ram, 100 GB HDD. It is switched off when not in use, so gets rebooted a lot.

I don't know how to go about solving this issue. Any advice is welcome!

[SlowJet]

Read the kernel log on koji.fedoraproject.org/koji/ for package kernel

I think you need >= 76 or 78 to get aorund some crashes.

I'm running 81 32 bit fine.

SJ

[dd_wizard]

I had crashes with 81, and had to switch back to 78 on 64 bit. Something seems to be going on lately with the 2.6.35 kernel. Right now I'm on Linux 2.6.37-2.fc15.x86_64 and it cleaned up some long standing graphic glitches in Compiz. It takes forever to compile on my laptop, so I'm hoping one of the people building the 2.6.37 kernel for F14 puts a copy on fedorapeople.

dd_wizard

[multipitch]

I'm afraid I don't know much about changing the kernel and I don't want to do something and remove the working (..72..) kernel.
At the moment, if I boot into the grub menu, I can select:

1. 12.6.35.10-74.fc14.x86_64 ...this is selected by default
2. 12.6.35.10-74.fc14.x86_64 ...this is the one that works
3. ...and another older one (not at my computer now & can't remember the version)

How can I either
A) Have the working kernel selected by default, or
B) Install a newer kernel (76 and 78 have been mentioned), without losing the working one from the list
...And which of the two options is the best?

[stevea]

As root execute this ...
grubby --remove-kernel=/boot/vmlinuz-2.6.35.10-74.fc14.x86_64

This just removes the offending kernel entry from grub.

[multipitch]

Thanks stevea, that solved the booting issue.

Is there a way of debugging the root cause though, e.g. being able to say "that must be the wireless driver" or whatever, and filing it as a bug?

[janw1]

Originally Posted by stevea

As root execute this ...
grubby --remove-kernel=/boot/vmlinuz-2.6.35.10-74.fc14.x86_64

This just removes the offending kernel entry from grub.

I thought this might well be my problem too, so I executed the above command, (after checking that the active kernel number reported by the system was NOT the one in the above command) --but now the system is entirely dead! If I switch it on, it makes its usual sounds, this falls silent after a few seconds, then nothing. Screen remains black whatever I do. I have created a live USB: with this it makes more sounds, and more varied, but nothing on the screen.
What can I do?