[SOLVED] Latest kernel update causes panic

[QuantumKnot]

After the latest round of updates to kernel-3.2.9-1.fc16.x86_64, I get a kernel panic during bootup (after about 8 seconds). The debug trace is long and goes off the screen. There's nothing in the logs about it.

Version 3.2.7-1 works, so was wondering if anyone had an issue with the latest kernel update?

[Chilly Willy]

so far, so good, for me. 32B-PAE, though.

[diamond_ramsey]

Originally Posted by QuantumKnot

After the latest round of updates to kernel-3.2.9-1.fc16.x86_64, I get a kernel panic during bootup (after about 8 seconds). The debug trace is long and goes off the screen. There's nothing in the logs about it.

Version 3.2.7-1 works, so was wondering if anyone had an issue with the latest kernel update?

I was okay with the 3.2.9-1.fc16.x86_64 kernel.

May be a review of the entries listed between 3.2.7-1 until 3.2.9-1 at:

- koji.fedoraproject.org/koji/buildinfo?buildID=30385

"...* Wed Feb 29 2012 Josh Boyer <jwboyer@redhat.com> 3.2.9-1
...
* Mon Feb 20 2012 Dave Jones <davej@redhat.com> 3.2.7-1..."

FYI, there's a kernel-3.2.9-2.fc16 now -

- koji.fedoraproject.org/koji/buildinfo?buildID=304798

Hope this helps.

[Chilly Willy]

This is just thinking out load, but I wonder if they are trying to pack to much into these kernels as to why they seem to have so much trouble as of late. But at least someone was thinking when they incorporated the feature in the OS of being able to go back to a previous one.

I'm just glad I'm not on the repair end of these kernels, when they work for some & not for others - that's like trying to fix an intermitting nightmare! My best of wishes to those that DO!

Keep us posted if you find anything, & sorry I can't be of any [real] help.

[donnie3543]

I had problems on both computers not booting, under 3.2.9-1, it is not accepting my password for the encrypted drive when the system boots, it says it's wrong but it works under the old kernel. My other computer just won't boot at all with it.

[AlanSac]

I had similar problems. I used my working kernel to troubleshoot. If you haven't already, install yumex, and beesu - see their website http://honeybeenet.altervista.org/beesu/ This will let you graphically review all logs and messages in root. Think of it as a graphical front end for command line file utilities. Yumex is a similar front end for yum - when it runs, click on installed, and you can see what you have and need to remove. Like yum, it will give you a chance to review before final action.

It solved my problems, hope this helps for you!

[jtorri]

Had similar problem after yum update (kernel panic at boot). Looked at /boot/grub2/grub.cfg and noticed the initrd /initramfs-3.2.9-1.fc16.i686.img line was missing. Executed yum update kernel-3.2.9-1.fc16.i686. It now boots cleanly and /boot/grub2/grub.cfg contains the missing line. In as much as I only sorta know what I am doing this "fix" may or may not make sense. I try never to exclude luck.

---------- Post added at 10:29 PM ---------- Previous post was at 10:12 PM ----------

Oops! Rather than yum update I meant to say yum reinstall kernel-3.2.9-1.fc16.i686. Sorry....

[TK492]

Originally Posted by jtorri

Had similar problem after yum update (kernel panic at boot). Looked at /boot/grub2/grub.cfg and noticed the initrd /initramfs-3.2.9-1.fc16.i686.img line was missing. Executed yum update kernel-3.2.9-1.fc16.i686. It now boots cleanly and /boot/grub2/grub.cfg contains the missing line. In as much as I only sorta know what I am doing this "fix" may or may not make sense. I try never to exclude luck.

---------- Post added at 10:29 PM ---------- Previous post was at 10:12 PM ----------

Oops! Rather than yum update I meant to say yum reinstall kernel-3.2.9-1.fc16.i686. Sorry....

Thank you very much, your updated comment solved a panicking kernel for me!

[Magickman]

I got the update and installed kernel-3.2.9-1.fc16.x86_64 yesterday. All went fine, and it works great.

[QuantumKnot]

Updated to the new kernel-3.2.9-2.fc16.x86_64 and it still does a panic during startup.

[QuantumKnot]

Even the latest kernel-3.3.0-4.fc16.x86_64 panics.

Found out the same issue in https://bbs.archlinux.org/viewtopic.php?pid=1073958

After blacklisting the ite_cir module, booting now works