ehci fails but ohci does not initiate

[penguin]

ehci_hcd fails to fall back to ohci if USB 2.0 port is NOT working
(i.e. hardware USB 2.0 is not working or is defective)... if ehci
fails to initiate, it does not fall back to ohci

USB 2.0 port of laptop not functioning.... ehci_hcd fails... doesn't
fall back to ohci... usb 1.1 devices work (e.g. mouse)

Hardware: Thinkpad T41, FireGL Radeon Mobility 9000 (RV250), 2 USB ports - USB 2.0 (Southbridge issue)
This was tested in Ubuntu and Lubuntu 10.04 (same result/outcome):

$ lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 062a:0000 Creative Labs Optical mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

$ dmesg | tail
[ 492.360449] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 492.548420] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 492.736393] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 492.924366] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 493.112335] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 493.300432] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 493.488406] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 493.610605] end_request: I/O error, dev fd0, sector 0
[ 493.610621] Buffer I/O error on device fd0, logical block 0
[ 493.732089] usb 1-4: new high speed USB device using ehci_hcd and address 64

$ dmesg | grep usb
[ 4.348048] usb 1-4: new high speed USB device using ehci_hcd and address 17
[ 5.600043] usb 1-4: new high speed USB device using ehci_hcd and address 23
[ 11.304988] usb 1-4: new high speed USB device using ehci_hcd and address 26
[ 11.860401] usb 1-4: new high speed USB device using ehci_hcd and address 28
[ 13.488058] usb 1-4: new high speed USB device using ehci_hcd and address 36
[ 13.800141] usb 1-4: new high speed USB device using ehci_hcd and address 37
[ 15.056100] usb 1-4: new high speed USB device using ehci_hcd and address 43
[ 16.308036] usb 1-4: new high speed USB device using ehci_hcd and address 49
[ 18.500045] usb 1-4: new high speed USB device using ehci_hcd and address 60
[ 19.376043] usb 1-4: new high speed USB device using ehci_hcd and address 64
[ 19.876063] usb 1-4: new high speed USB device using ehci_hcd and address 66
[ 21.504071] usb 1-4: new high speed USB device using ehci_hcd and address 74
[ 22.380061] usb 1-4: new high speed USB device using ehci_hcd and address 78

ETC.

[penguin (teleguitar)]

Any USB 2.0 drive (incl. flash drives) such as SATA drive in enclosure connected via USB applies...

[penguin (teleguitar)]

$ modprobe -r ehci_hcd
FATAL: Module ehci_hcd not found.

$ dmesg | grep USB
OUTPUT BELOW - GOES ON AND ON...

 usb 1-4: new high speed USB device using ehci_hcd and address 68
[ 1772.432275] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 1772.620423] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 1772.808399] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 1772.996362] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 1773.240073] usb 1-4: new high speed USB device using ehci_hcd and address 72
[ 1773.308284] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 1773.496423] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 1773.684384] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 1773.872353] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 1774.060330] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 1774.248298] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 1774.436403] hub 1-0:1.0: unable to enumerate USB device on port 4
[ 1774.624379] hub 1-0:1.0: unable to enumerate USB device on port 4

[Mackenzie Morgan (maco.m)]

Reporter added (on IRC) that this bug does not affect Debian Squeeze, so there's another data point.

[penguin (teleguitar)]

Debian Squeeze is also installed and compared to Ubuntu 10.04 with this issue. USB 2.0 drives have to be mounted in Squeeze manually... most of the time... can't determine yet when drive mounts automatically. The procedure above works for mounting at 1.1 speeds in Squeeze.

STEPS
1) $ dmesg | tail
2) $ dmesg | grep usb
3) modprobe -r ehci_hcd

Then steps #1 and #2 are repeated. When this is input in Debian Squeeze, the usb 2.0 drives mount but using 1.1 speeds.

Same attempt in Ubuntu/Lubuntu doesn't work.

Steps #1 and #2 display same output (as given in initial posts of bug) but step #3.... gives following output:
$ modprobe -r ehci_hcd
FATAL: Module ehci_hcd not found.

sudo fdisk -l shows only PATA/IDE HDD in computer. USB 2.0 devices still not mounted...

[kernel-janitor (kernel-janitor)]

Hi penguin,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 614180

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]