Lastest breezy update makes kernel panic on boot and attempt to kill init

[David Capel]

I installed the Breezy PR cd, and it worked fine until I apt-get update/upgrade'd it.
After rebooting, when I attempt to turn it on again, GRUB loads the kernel, the kernel
does a little big, then panics when it gets to init. After attempting to kill it,
citing a memory on 0x I believe, the whole box freezes.

After that happened every time after a few reboots, I reinstalled from disk,
update/upgraded again, and lo and behold it happens again.

Lucky I kept a hoary partition, so I can report this ;) (I can mount the breezy
installation if any information can be gotten out of it that you guys want)

[Kaloyan Raev (k-raev)]

I have absolutely the same problem. I installed the 510 Preview on 17 Sep, ran
apt-get update/upgrade the next day. Yesterday I shut down the pc and this
morning it fails come up with the same kernel panic error.

[JasonCohen (jcohen07)]

I think this is the same bug as 15707.

[Kaloyan Raev (k-raev)]

I managed to recover my system. I boot from the live cd, then mounted the
filesystem of the broken installation (in my case to /mnt). I executed "ls -l
/boot" and "ls -l /mnt/boot" and noticed that the kernel files on my broken
installation and on the live cd are different in size. On my broken installation
I renamed the files to *.bad and copied those from the live cd. Finally, my "ls
-l /mnt/boot" shows:

raev@raev-mobile:~$ ls -l /mnt/boot
total 13228
-rw-r--r-- 1 root root 64045 2005-09-19 22:19 config-2.6.12-8-386
-rw-r--r-- 1 root root 64090 2005-09-16 00:12 config-2.6.12-8-386.bad
drwxr-xr-x 2 root root 4096 2005-09-18 18:09 grub
-rw-r--r-- 1 root root 4781647 2005-09-19 22:19 initrd.img-2.6.12-8-386
-rw-r--r-- 1 root root 5159722 2005-09-18 18:09 initrd.img-2.6.12-8-386.bad
-rw-r--r-- 1 root root 94664 2005-06-30 18:49 memtest86+.bin
-rw-r--r-- 1 root root 897036 2005-09-16 01:52 System.map-2.6.12-8-386
-rw-r--r-- 1 root root 1206596 2005-09-19 22:19 vmlinuz-2.6.12-8-386
-rw-r--r-- 1 root root 1206600 2005-09-16 01:52 vmlinuz-2.6.12-8-386.bad

You can see the differences in the file sizes. After reboot the broken
installation came up successfully. During the boot the loader reported that
there is one broken file on the root filesystem. I don't know if this is related
to the issue.

I suppose that the apt-get upgrade got broken kernel files from the update
repository. I paste my /etc/apt/sources.list:

--------- PASTE BEGIN ---------
raev@raev-mobile:~$ cat /etc/apt/sources.list
deb cdrom:[Ubuntu 5.10 _Breezy Badger_ - Preview i386 (20050908)]/ breezy main
restricted

## Uncomment the following two lines to fetch updated software from the network
deb http://bg.archive.ubuntu.com/ubuntu breezy main restricted
deb-src http://bg.archive.ubuntu.com/ubuntu breezy main restricted

## Uncomment the following two lines to fetch major bug fix updates produced
## after the final release of the distribution.
deb http://bg.archive.ubuntu.com/ubuntu breezy-updates main restricted
deb-src http://bg.archive.ubuntu.com/ubuntu breezy-updates main restricted

## Uncomment the following two lines to add software from the 'universe'
## repository.
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## universe WILL NOT receive any review or updates from the Ubuntu security
## team.
deb http://bg.archive.ubuntu.com/ubuntu breezy universe
deb-src http://bg.archive.ubuntu.com/ubuntu breezy universe

deb http://security.ubuntu.com/ubuntu breezy-security main restricted
deb-src http://security.ubuntu.com/ubuntu breezy-security main restricted

deb http://security.ubuntu.com/ubuntu breezy-security universe
deb-src http://security.ubuntu.com/ubuntu breezy-security universe
---------- PASTE END ----------

I hope this workaround helps for everybody fallen in this situation.
I still haven't run the apt-get upgrade again.

Greetings

[Matt Zimmerman (mdz)]

This bug has been marked as a duplicate of bug 21922.