Did an update thjis morning which updated the kernel to 3.2.0-19. Result is that this version will not even boot into recover mode. Boot hangs right after kernal load. I am running on Intel I5. Anybody else see this. Work around was to boot to 3.2.0-18
-
-
Anything interesing in your syslog? -
I am looking at the console window after selecting Linu 3.2.0-19-generic (recovery mode)
Things go pretty fast than stops with these as the last three lines:
kernel_thread_helper +0x4/0x10
start_kernel+0x3c7/0x3c7
gs_change+0x13/0x13
There it just stops. If I reboot to 3.2.0.18 it worksComment
-
Wow. So when you boot into 3.2.0-18 and take a look at the logs, I'm guessing you won't see anything from the failed boot?Comment
-
Yes thats right. Here is something of interest I just did a apt-get remove on linux--image-3.2.0-19-generic
It gives me the following output:
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-18-generic
Found initrd image: /boot/initrd.img-3.2.0-18-generic
Found linux image: /boot/vmlinuz-3.2.0-17-generic
Found initrd image: /boot/initrd.img-3.2.0-17-generic
Found memtest86+ image: /boot/memtest86+.bin
ERROR: ddf1: wrong # of devices in RAID set "ddf1_44656c6c202020201000006010281f0c37ddad1b5013 3c3b" [1/5] on /dev/sdc
Found Windows 7 (loader) on /dev/sda1
done
The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
you may need to re-run your boot loader[grub]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
you may need to re-run your boot loader[grub]Comment
-
Well, I'm afraid I can't offer much guidance. I'm not much of a kernel expert.
I doubt the RAID error is causing the problem with 3.2.0-19, though.
And the bit about damaged links -- that's normal, I see it routinely when I remove one kernel after replacing it with another one.Comment
Comment