[Bug 222799] Re: Hardy kernel panic after upgrade

[Michael]

I've upgraded to 8.10 today and it's asking me to reboot the system.

Again, there's no initrd line for the new kernels in /boot/grub/menu.lst
Here's the first auto generated kernel entry:
title           Ubuntu 8.10, kernel 2.6.27-7-generic
root            (hd0,2)
kernel          /boot/vmlinuz-2.6.27-7-generic root=UUID=924b1a6f-3d78-4fac-9957-55ffd2ddd0f8 ro 
savedefault

The kernel seems installed:
$ dpkg -l |grep linux-image-2.6.27-7-generic
ii  linux-image-2.6.27-7-generic               2.6.27-7.16

The initrd image exists:
$ ls -l /boot/*-2.6.27-7-generic 
-rw-r--r-- 1 root root  507665 2008-11-04 22:00 /boot/abi-2.6.27-7-generic
-rw-r--r-- 1 root root   91364 2008-11-04 22:00 /boot/config-2.6.27-7-generic
-rw-r--r-- 1 root root 9261441 2008-11-13 21:30 /boot/initrd.img-2.6.27-7-generic
-rw-r--r-- 1 root root 1029585 2008-11-04 22:00 /boot/System.map-2.6.27-7-generic
-rw-r--r-- 1 root root    1073 2008-11-04 22:02 /boot/vmcoreinfo-2.6.27-7-generic
-rw-r--r-- 1 root root 2244464 2008-11-04 22:00 /boot/vmlinuz-2.6.27-7-generic

According to term.log, update-grub was only run once, when memtest86 was
updated. It was not run after the kernel install (ie, after "update-
initramfs: Generating /boot/initrd.img-2.6.27-7-generic")

I've just checked kernel-img.conf:
$ cat /etc/kernel-img.conf 
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no

Looks like I disabled grub update... So the missing update-grub is
right. I will enable it again (I don't remember exactly why I did that).

But the update-grub run on memtest86 is probably wrong. Should we
disable it when do_bootloader is "no"? Or should we run it after the
kernel images are fully installed?

Right now, upgrading at the same time memtest86 and a kernel image,
while having do_bootloader set to "no" will leave the system unbootable.

I'll let the system in this state for some hours, if anyone want fresh
data. But then I'll run update-grub, reboot and use it again.

** Attachment added: "term.log"
   http://launchpadlibrarian.net/19642540/term.log

-- 
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.