3

Upgrade to 3.5.0-2 kernel causes boot failure

view full story
linux-howto

http://forums.fedoraforum.org – I've just upgraded the linux kernel from 3.4.6-2 to 3.5.0-2 and am now unable to boot the new kernel. The boot process ends with the following message displayed: fixing recursive fault but reboot is needed If I reboot the machine I get the same message. I can still boot into the the old kernel with no problem. What steps do I need to do to further determine the cause of this error and then to fix it? (HowTos)

xiooo's picture
Submitted by xiooo on 08/06/2012 – Made popular on 08/06/2012

Stories similar to Upgrade to 3.5.0-2 kernel causes boot failure

Problem with kernel package. 37 weeks 2 days ago

I am running Fedora 15 on a second machine.

I had trouble booting Linux and I found that while grub started off trying to boot vmlinuz-2.6.43, I had to backtrack to vmlinuz-2.6.42 in order to boot. rpm -qa | grep kernel shows both kernel packages installed and rpm -ql ... shows the newer kernel should be in /boot, but it isn't.

Hi guys

I have a problem here which is getting frustrating now..

several weeks ago i have upgraded one of our ubuntu-server machines here, previously we were running it on kernell image 2.6.32-21 , after upgrading it to 2.6.32-41 problems started.

on boot up, if for any instance the machine needs rebooting, the boot menu pops up and it will select new kernell image, but then it gets stuck on

I'm using both a Bluetooth mouse and keyboard, and frankly it's really annoying having to go grab a physical keyboard in order to boot into another kernel version or into Windows on another partition.

Hello just upgraded to kernel 3.4.3-1.fc17.x86_64 and it went panic after 2 minutes.

Now I get a kernel panic message when booting the machine:

Code: Kernel panic - not syncing: VFS: Unable to mount root fs n unknown-block(0,0) Pid: 1, comm: swapper/0 Not tainted 3.4.3-1.fc17.x84_64 #1 and the call trace which I'm not reporting. Using old kernels gives me a filesystem error, requiring to ex

Fedora 16.x86_64 Kernel 3.3.2-1.fc16.x86_64 NVidia binary blob.

Well, I thought it would never happen to me, but I installed a kernel update and its borked my system - and as luck would have it, this is my pride-and-joy "production" machine... BAH.

I just updated my kernel to kernel-2.6.29.5-191.fc11.x86_64 on my x64 system, after I reboot my machine, the Fedora loading bar comes up and finishes but then no gui comes up. I attempt to issue commands at the hanging prompt that comes up but nothing happens. I can boot into my older kernel just fine but not the updated one.

What can I do?

I have started reading the book Essential Linux Device Drivers. I am following the process for compiling and booting into a new kernel.

I had the unlucky situation to have a power failure in the middle of a Kernel upgrade using Pacman. System came back up and the kernel was not installed. So I have NO working OS on the machine.I can boot into a live USB environment and chroot into my install. I can run Pacman, and thought I could just pacman -S linux and let it do it's thing and I'd be all good. but...

Hey Everyone,

Thank you for your help with this. During the upgrade process I had an error and the machine rebooted. After getting my grub repaired I was able to finally get booted up and I finished up the installation of the packages that was left over. Now if I boot up into the 3.5 kernel I have no Network or USB. This is kind of a PITA since my keyboard is USB.