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:
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 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
