Am Do, 21.05.2009, 19:25, schrieb Felipe Alfaro Solana: > I tried and it doesn't make any difference. Perhaps, it's because my > machine has a built-in CF reader. These are the last lines logged during > boot before the system hangs and starts chewing CPU:
For how long did you let it "sit" before you decided that It wouldn't continue to boot? The server I've seen it with seems to take a few minutes before it continues, at least it takes look enough for me to get bored and leave the room to do something else in the meantime. When I come back some time later the machine has managed to get to the login prompt. (While a number of wild running blkid processes give their best to use up all available CPU time.) Cheers Mike > scsi 6:0:0:0: Direct-Access Generic- Compact Flash 1.00 PQ:0 ANSI: > 0 CCS > scsi 6:0:0:1: Direct-Access Generic- SM/xD-Picture 1.00 PQ:0 ANSI: > 0 CCS > scsi 6:0:0:2: Direct-Access Generic- SD/MMC 1.00 PQ:0 ANSI: > 0 CCS > scsi 6:0:0:3: Direct-Access Generic- MS/MS-Pro 1.00 PQ:0 ANSI: > 0 CCS > sd 6:0:0:0 Attached scsi generic sg5 type 0 > sd 6:0:0:1 Attached scsi generic sg6 type 0 > sd 6:0:0:2 Attached scsi generic sg7 type 0 > sd 6:0:0:3 Attached scsi generic sg8 type 0 > sd 6:0:0:0: [sde] Attached SCSI removable disk > sd 6:0:0:1: [sde] Attached SCSI removable disk > sd 6:0:0:2: [sde] Attached SCSI removable disk > sd 6:0:0:3: [sde] Attached SCSI removable disk > > And I think this is a udev/blkid issue: I took a snapshot of my Jaunty > installation and did an upgrade to Karmic again. During the process, > towards the end of the installation, the CPU fans went full speed. I > checked with top and two blkid processes spawned from udev where > constantly eating ~90% of the CPU. > > Any ideas? > > -- > Karmic Alpha 1 hangs after probing storage devices > https://bugs.launchpad.net/bugs/377747 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in âlinuxâ source package in Ubuntu: New > > Bug description: > 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. > -- 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
