Booting computer with attached USB-storages causes lockup

[torb]

If I boot my computer with any external USB-storages (harddrive, ipod) attached, it locks during "Mounting root file system" (the second item outputted by usplash).
Removing USB-storages solves the problem.

My USB-mouse causes no problem.

I'm attaching my fstab, please ask for other items you need.

Note: the original reporter indicated the bug was in package 'linux-image'; however, that package was not published in Ubuntu.

[torb (torrb)]

my fstab

[Soren Hansen (soren)]

During the boot process you're given the option to press ESC before af few seconds pass. Do that and choose recovery mode. It will bypass the usplash screen and possibly give you some valuable info.

If you can, try posting the last few lines here.

[torb (torrb)]

The last lines go (replace "(rightbracket)" with a right bracket, the swedish xmodmap-file is broken):

usbcore: registered new driver usbfs
usbcore: registered new driver hub
*** SET: Misaligned resource pointer: dfc10942 Type 07 Len 0
ACPI: PCI Interrupt Link [LUS0(rightbracket) enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:02.0[A(rightbracket) -> Link [LUS0(rightbracket) -> GSI 11 (level, low) -> IRQ 11
ohci_hcd 0000:00:02.0: OHCI Controller

Hope this is of any help. By the way, is there any way to log these messages instead of typing them by hand?

[torb (torrb)]

Is there anything else I can do to help you debug this problem?

[schneeland (schneeland)]

I guess, I am experiencing king of the same bug. Yet I have no active USB storage devices attached (the only usb harddrive is inactive), others are an USB-cardreader, a USB printer and an USB mouse, all attached via a hub and a USB keyboard and USB webcam (attached directly to the computer).

I get the above-mentioned error of the misaligned resource pointer (with the latest text-mode install daily build as well as beta1, beta2 and flight 7) when I switch off quiet mode.

[Mlt (mlt)]

I have this problem as well.

On my system it is the internal memory card reader that connects by internal USB. If this is not connected it boots with out any problem. Connected it may boot 1 in 4 times of trying.

My other USB devices to not affect the boot up sequence.

[Ian Oliver (hvy4-idbo)]

I had exactly this problem this weekend when building some new machines. They have Asus A8N VM CSM motherboards in Antec Aria cases. The Aria has front panel memory card slots connected to an internal USB connector.

With the memory card slots connected, the Dapper live CD would hang at "Mounting root file system"

I didn't play with boot: options - it was easier to just pull the memory card connector - with this done Dapper boots just fine.

Note that the Asus BIOS does some kind of floppy/HD emulation with the USB devices, but I'm a big fuzzy regards exactly what.

BIOS 1001 on the A8N if someone is looking to reproduce and fix this bug. It's pretty bad if the Live CD won't boot on such mainstream hardware.

Ian

[Mlt (mlt)]

Funnily enough, I am using the same motherboard/case combo as Ian Oliver. I have updated my bios which has cured other problems but not this one.

Etch and FC5 installed and booted without any problems. I was able to get the live CD to run without any problem, it has been the installation that has caused problems for me (32 and 64 bit).

[Rich Johnson (nixternal)]

I cannot confirm this as I have USB drives hanging out of every port on this machine and I never disconnect them unless I am moving them.

Are you still experiencing these problems with a stable release?

[Michael Truscott (mltruscott)]

Yes I can unfortunately.

As I put in the bug report it doesn't like the card reader in my Aria case
either. I don't know if it is the Asus board that is the particular problem
but it is top of the list of suspects.

On Wednesday 13 December 2006 05:48, Richard Johnson wrote:
> I cannot confirm this as I have USB drives hanging out of every port on
> this machine and I never disconnect them unless I am moving them.
>
> Are you still experiencing these problems with a stable release?
>
> ** Changed in: Ubuntu
> Sourcepackagename: None => linux-source-2.6.15
> Importance: Medium => Undecided
> Status: Unconfirmed => Needs Info

[Philip Paquette (pcpaquette)]

Can you confirm this bug still happens in edgy/feisty?
Thanks.

[Michael Truscott (mltruscott)]

On Wednesday 18 April 2007 23:26:07 Philip Paquette wrote:
> Can you confirm this bug still happens in edgy/feisty?
> Thanks.

This bug does not occur in feisty and the computer boots.

[Philip Paquette (pcpaquette)]

Setting status to fixed.