[Bug 222799] Re: Hardy kernel panic after upgrade

[Thorsten Glaser]

*** This bug is a duplicate of bug 154199 ***
    https://bugs.launchpad.net/bugs/154199

** This bug has been marked a duplicate of bug 154199
   gforge install/remove failure loop w/ broken dpkg

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to memtest86+ in Ubuntu.
https://bugs.launchpad.net/bugs/222799

Title:
  Hardy kernel panic after upgrade

Status in The Linux Kernel:
  Invalid
Status in “gforge” package in Ubuntu:
  Triaged
Status in “memtest86+” package in Ubuntu:
  Fix Released

Bug description:
  I've got a problem with the new kernel. After upgrade Gutsy->Hardy
  which went fine reboot welcomes me with Kernel panic - not syncing:
  VFS: unable to mount root on unknown-block(0,0). Trying to boot Gutsy
  kernel ends in BusyBox. Quick look around in it showed no hard drive
  devices (sda/sdb/hdc/hdd in /dev). I did boot with System Rescue CD,
  mounted /boot and rolled back initrd to the one generated during gutsy
  install for 2.6.22. I successfully booted Gutsy kernel then. update-
  initramfs successfully actualized initrd for 2.6.22 so there has to be
  some problem with the kernel. I've tried to reinstall it, install
  2.6.22-16-386, server and pci=nomsi option with kernel panic
  everytime. Ubuntu Live CD recognizes all drives correctly, but
  overwriting 2.6.24 kernel with the one from Live CD doesn't help.
  Recompilation of Hardy kernel doesnt either. This bug is also valid
  for vanilla 2.6.24.3 and 2.6.25 kernels. I've got lvm on software
  raid, but that shouldn't matter here. System installed on sata drives,
  and besides those two, I've got one hdd and dvd-rw on pata. Chipset is
  nforce2, sata controller PDC20376.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/222799/+subscriptions