Booting works with USB set to 1.1 only, but not with USB 2.0 enabled (Asus K8N-E)

Bug #49552 reported by schneeland
22
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I have the following problem (at least since Flight 6, but not with Breezy or earlier):

I own a ASUS K8N-E board (Nforce 3 250GB) that has a number of USB 2.0 ports - these used to work in Breezy without problem. Yet, if I start Dapper (live cd, alternate cd, installed system) I can only boot when USB is set to "1.1 only" in BIOS.
If I boot without "quiet splash", the boot process shows an error about "SET - Misaligned resource pointer" in the stage of initialising the USB ports.

Revision history for this message
Stephan Huiser (stephan-huiser) wrote :

Same problem here:

Ubuntu Dapper 6.06 AMD64 on Asus A8N-SLI Premium.
"SET - Misaligned resource pointer"

Revision history for this message
schneeland (schneeland) wrote :

Any progress on this?

Revision history for this message
Greg T. (gjtbiz) wrote :

I'm having the same problem. I did an upgrade tonight and couldn't boot afterwards. I have a Asus A8N-SLI Deluxe, booting off an SATA drive. If I turn off USB 2.0 (allowing only USB 1.1), I'm fine. Otherwise, I'm dead in the water.

This is the same problem I had with Dapper, which caused me to have to upgrade early to Edgy months ago, 'cause I kinda like USB 2.0. I can't believe that it's returned. Where do I file a bug report?

Booting hung on this message:

[17179584.168000] ohci_hcd 0000:00:0b.0: new USB bus registered, assigned bus number 1

Greg T. (gjtbiz)
Changed in linux-source-2.6.15:
status: Unconfirmed → Confirmed
Revision history for this message
Greg T. (gjtbiz) wrote :

One other note: I can boot without disabling USB 2.0 if I disconnect from my computer the USB hub in my monitor. I've got a Dell 2405FPW. If I do that, nothing is connected to the USB slots on my PC.

Revision history for this message
schneeland (schneeland) wrote :

The same applies to my - if I disconnect all usb devices, the system brings me up to the GUI. I can plug the devices in again and they work. This is with Edgy RC.

Revision history for this message
Greg T. (gjtbiz) wrote :

Bug #62072, #64873, and #66122 all may be duplicates of this bug.

Revision history for this message
Greg T. (gjtbiz) wrote :

The "noapic" argument and other variations seem to have no effect with my setup.

Revision history for this message
schneeland (schneeland) wrote :

62072 really seems to be a duplicate of this bug, 64873 and 66122 look slightly different, as none of "noapic", "nolapic", "acpi=off" have an effect on booting for me.

Revision history for this message
Greg T. (gjtbiz) wrote :

See bug #55967 for a possible workaround. It worked for me.

Revision history for this message
schneeland (schneeland) wrote :

Many thanks. Adding "usb-handoff" indeed helps. I wonder why it has never been mentioned before.

Revision history for this message
Lytenian Savol (madpaladin) wrote :

Thanks. This solution (usb-handoff) worked for me, whereas the solutions posted in the duplicates (bug #62072 & bug #64873) did not. If someone for whom those solutions works could test this in place of them, it would help determine whether they are true duplicates or not.
FYI - My mobo is an MSI K8N Diamond Plus. Situation otherwise exactly as Greg describes in comment 3.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Adam Petaccia (mighmos) wrote :

I had this issue a while ago, but haven't had it in a long time.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Having received no other feedback. I'm closing this based on the previous comment. Thanks.

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.