Public bug reported: Binary package hint: linux-image
After upgrading Kubuntu Jaunty to Karmic Alpha 1, the system no longer boot and hungs just after probing the storage devices. The last lines shown on the screen before the system hangs are: [ 15.127391] sd 7:0:0:0: [sdi] Attached SCSI removable disk [ 15.127544] sd 7:0:0:0: Attached scsi generic sg9 type 0 [ 15.128724] sd 7:0:0:1: [sdj] Attached SCSI removable disk [ 15.128829] sd 7:0:0:1: Attached scsi generic sg10 type 0 [ 15.130599] sd 7:0:0:2: [sdk] Attached SCSI removable disk [ 15.130705] sd 7:0:0:2: Attached scsi generic sg11 type 0 [ 15.133155] sd 7:0:0:3: [sdl] Attached SCSI removable disk [ 15.133266] sd 7:0:0:3: Attached scsi generic sg12 type 0 Normally, at this point, Jaunty would display: [ 29.822891] PM: Starting manual resume from disk [ 29.822933] PM: Resume from partition 252:0 [ 29.822936] PM: Checking hibernation image.[ 29.823106] PM: Resume from disk failed. ... and proceed booting, and reading files required by boot (I guess this is just read-ahead). With Karmic, instead, the system hangs and after a while, the CPU fan goes full throttle which means something is chewing CPU but not making any progress. I think this might be a bug related to the kernel itself or the initial ram disk (or perhaps udev). I can reliably reproduce this with linux- image-2.6.30-5-generic and udev-142-2. My system has 1 internal SATA disk, 5 external SATA disks plugged to a Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01), plus 1 external USB 1TB disk and 1 external FireWire 400 1TB disk. The internal SATA disk is configured to use LVM. The 5 external SATA disks are arranged into a RAID-5 volume (that seems to be properly set up and recognized during boot). The two USB+FireWire disks are also arranged into a striped LVM volume. Please let me know if you need additional information from my side. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- Karmic Alpha 1 hangs after probing storage devices https://bugs.launchpad.net/bugs/377747 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs