usb change between 2.6.15-23 and 2.6.15-26 breaks working setup

[Robert Penz]

This link points to an bug report which got fixed in 2.6.15-26 :

https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/49367

But it creates also a problem on my computer. With 2.6.15-23-386 its working on my VIA EPIA board and with
2.6.15-26-386 it stopped. I added an comment to the above bug, but I was not able to reopen it so I openning a new one. Sorry.

Here are some log entries with the 2.6.15-26-386 kernel:

Jul 28 00:06:53 jumpgate kernel: [17179878.780000] usb 1-2: new high speed USB device using ehci_hcd and address 2
Jul 28 00:06:54 jumpgate kernel: [17179879.780000] ehci_hcd 0000:00:10.3: Unlink after no-IRQ? Controller is probably using the wrong IRQ.
Jul 28 00:07:05 jumpgate kernel: [17179890.324000] usb 1-2: device not accepting address 2, error -110
Jul 28 00:07:05 jumpgate kernel: [17179890.448000] usb 1-2: new high speed USB device using ehci_hcd and address 3
Jul 28 00:07:16 jumpgate kernel: [17179901.992000] usb 1-2: device not accepting address 3, error -110
Jul 28 00:07:17 jumpgate kernel: [17179902.108000] usb 1-2: new high speed USB device using ehci_hcd and address 4
Jul 28 00:07:27 jumpgate kernel: [17179912.532000] usb 1-2: device not accepting address 4, error -110
Jul 28 00:07:27 jumpgate kernel: [17179912.648000] usb 1-2: new high speed USB device using ehci_hcd and address 5
Jul 28 00:07:38 jumpgate kernel: [17179923.072000] usb 1-2: device not accepting address 5, error -110

If I unload the ehci_hcd modul the dvd writer is accessable at once

Jul 28 16:08:22 jumpgate kernel: [17237138.096000] ehci_hcd 0000:00:10.3: remove, state 1
Jul 28 16:08:22 jumpgate kernel: [17237138.096000] usb usb1: USB disconnect, address 1
Jul 28 16:08:22 jumpgate kernel: [17237138.100000] ehci_hcd 0000:00:10.3: USB bus 1 deregistered
Jul 28 16:08:22 jumpgate kernel: [17237138.100000] ACPI: PCI interrupt for device 0000:00:10.3 disabled
Jul 28 16:08:22 jumpgate kernel: [17237138.340000] usb 2-2: new full speed USB device using uhci_hcd and address 2
Jul 28 16:08:23 jumpgate kernel: [17237138.664000] SCSI subsystem initialized
Jul 28 16:08:23 jumpgate kernel: [17237138.692000] Initializing USB Mass Storage driver...
Jul 28 16:08:23 jumpgate kernel: [17237138.696000] scsi0 : SCSI emulation for USB Mass Storage devices
Jul 28 16:08:23 jumpgate kernel: [17237138.696000] usb-storage: device found at 2
Jul 28 16:08:23 jumpgate kernel: [17237138.696000] usb-storage: waiting for device to settle before scanning
Jul 28 16:08:23 jumpgate kernel: [17237138.696000] usbcore: registered new driver usb-storage
Jul 28 16:08:23 jumpgate kernel: [17237138.696000] USB Mass Storage support registered.
Jul 28 16:08:28 jumpgate kernel: [17237143.732000] Vendor: HL-DT-ST Model: DVDRRW GSA-2164D Rev: 1.01
Jul 28 16:08:28 jumpgate kernel: [17237143.732000] Type: CD-ROM ANSI SCSI revision: 00
Jul 28 16:08:28 jumpgate kernel: [17237143.744000] usb-storage: device scan complete
Jul 28 16:08:28 jumpgate kernel: [17237143.832000] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Jul 28 16:08:28 jumpgate kernel: [17237143.836000] Uniform CD-ROM driver Revision: 3.20
Jul 28 16:08:28 jumpgate kernel: [17237143.836000] sr 0:0:0:0: Attached scsi CD-ROM sr0
Jul 28 16:08:28 jumpgate kernel: [17237143.872000] sr 0:0:0:0: Attached scsi generic sg0 type 5

on 2.6.15-23-386 it looks like that:

Jul 28 17:13:45 jumpgate kernel: [4294678.112000] usb 4-2: new high speed USB device using ehci_hcd and address 2
Jul 28 17:13:45 jumpgate kernel: [4294678.202000] Attempting manual resume
Jul 28 17:13:45 jumpgate kernel: [4294678.288000] SCSI subsystem initialized
Jul 28 17:13:45 jumpgate kernel: [4294678.295000] Initializing USB Mass Storage driver...
Jul 28 17:13:45 jumpgate kernel: [4294678.296000] scsi0 : SCSI emulation for USB Mass Storage devices
Jul 28 17:13:45 jumpgate kernel: [4294678.297000] usb-storage: device found at 2
Jul 28 17:13:45 jumpgate kernel: [4294678.297000] usb-storage: waiting for device to settle before scanning
Jul 28 17:13:45 jumpgate kernel: [4294678.297000] usbcore: registered new driver usb-storage
Jul 28 17:13:45 jumpgate kernel: [4294678.297000] USB Mass Storage support registered.
Jul 28 17:13:45 jumpgate kernel: [4294678.307000] EXT3-fs: mounted filesystem with ordered data mode.
Jul 28 17:13:45 jumpgate kernel: [4294678.340000] kjournald starting. Commit interval 5 seconds
Jul 28 17:13:45 jumpgate kernel: [4294683.333000] Vendor: HL-DT-ST Model: DVDRRW GSA-2164D Rev: 1.01
Jul 28 17:13:45 jumpgate kernel: [4294683.333000] Type: CD-ROM ANSI SCSI revision: 00
Jul 28 17:13:45 jumpgate kernel: [4294683.333000] usb-storage: device scan complete
Jul 28 17:13:45 jumpgate kernel: [4294684.685000] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Jul 28 17:13:45 jumpgate kernel: [4294684.685000] Uniform CD-ROM driver Revision: 3.20
Jul 28 17:13:45 jumpgate kernel: [4294684.685000] sr 0:0:0:0: Attached scsi CD-ROM sr0
Jul 28 17:13:45 jumpgate kernel: [4294684.728000] sr 0:0:0:0: Attached scsi generic sg0 type 5

[Robert Penz (robert-penz-name)]

does at least someone read that bug report? A working system is broken due a "security update" - thats a major problem. I cannot use the security hole free kernel !!!

[Ben Collins (ben-collins)]

Sorry, this bug kind of slipped through my bug mbox. I am aware of this problem.

The problem was introduced in 2.6.15-24.41, with this change:

  * usb: Enable CONFIG_USB_EHCI_SPLIT_ISO and CONFIG_USB_EHCI_ROOT_HUB_TT
    - Malone #28840
    - Malone #49367

The change was made so that other devices would work. In effect it seems to have broken others. The devices that were broken were a regression from breezy, so in essence we have a dual problem where we had to have this fix to keep things from breaking between breezy and dapper, but in doing so we broke machines that were once working in dapper.

The workaround is likely to remove the ehci_hcd module by performing this command:

sudo modprobe -r ehci_hcd

If you would like to make this permanent, then do:

sudo sh -c 'echo blacklist ehci_hcd > /etc/modprobe.d/blacklist-ehci'
sudo update-initramfs -u -k `uname -r`

This process can be reversed by removing the /etc/modprobe.d/blacklist-ehci file and rerunning the update-initramfs command.

Hope this helps in the interim until this is resolved.

[wannes (wannes)]

I experience the same when inserting an USB-memory stick or CF-card in my card-reader. The modprobe -ehci_hcd thing works so I blacklisted the module ...

[wannes (wannes)]

Is this going to be fixed in edgy? After all, it _doesn't_ work out of the box ...

[Robert Penz (robert-penz-name)]

what means it does not work out of the box. if I blacklist the ehci module, i've no usb2 only usb1 - or is that assumption not correct?

[Ulrich Lukas (ulrich-lukas)]

On my computer, I'm running Kubuntu dapper with kernel 2.6.15-27-686 on a dual-Pentium-3-Mainboard (output of lspci attached).

I don't know it that's connected with this issue, but I get sporadic problems with my USB-2.0-memory stick not being properly recognized by the kernel.

Right after booting the computer, it usually works, but (Murphy's Law...) always when I need to quickly transfer a file, there is no /dev/sda... entry created, and dmesg says something like:

[quote]
[17393482.236000] usb 5-1: new high speed USB device using ehci_hcd and address 4
[17393483.236000] ehci_hcd 0000:00:0f.2: Unlink after no-IRQ? Controller is probably using the wrong IRQ.
[17393493.780000] usb 5-1: device not accepting address 4, error -110
[17393493.892000] usb 5-1: new high speed USB device using ehci_hcd and address 5
  [....]
[17393958.608000] usb 5-1: new high speed USB device using ehci_hcd and address 9
[17393970.152000] usb 5-1: device not accepting address 9, error -110
[17394247.388000] ehci_hcd 0000:00:0f.2: remove, state 1
[17394247.388000] usb usb5: USB disconnect, address 1
[/quote]

OK, right before inserting the USB-2.0-memory stick, I plugged in a USB-1.1-USB-connected-USB-storage-capable digital camera, and it was successfully recognized*. (I'm attaching the full output of dmesg too; the according messages are just before the dmesg lines quoted above in this posting)

After entering "sudo rmmod ehci_hcd" and "sudo modprobe ehci_hcd", the USB-2.0-stick works again; dmesg:

[quote]
[17394247.400000] ehci_hcd 0000:00:0f.2: USB bus 5 deregistered
[17394247.400000] ACPI: PCI interrupt for device 0000:00:0f.2 disabled
[17394253.320000] ACPI: PCI Interrupt 0000:00:0f.2[C] -> GSI 19 (level, low) -> IRQ 185
[17394253.320000] ehci_hcd 0000:00:0f.2: EHCI Host Controller
[17394253.324000] ehci_hcd 0000:00:0f.2: new USB bus registered, assigned bus number 5
[17394253.324000] ehci_hcd 0000:00:0f.2: irq 185, io mem 0xe3040000
[17394253.324000] ehci_hcd 0000:00:0f.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[17394253.324000] hub 5-0:1.0: USB hub found
[17394253.324000] hub 5-0:1.0: 4 ports detected
[17394259.484000] usb 5-1: new high speed USB device using ehci_hcd and address 2
[17394259.636000] scsi2 : SCSI emulation for USB Mass Storage devices
[17394259.636000] usb-storage: device found at 2
[17394259.636000] usb-storage: waiting for device to settle before scanning
[17394264.640000] Vendor: memory Model: USB2.0 Rev: 1.00
[17394264.640000] Type: Direct-Access ANSI SCSI revision: 02
[17394264.640000] SCSI device sda: 1999360 512-byte hdwr sectors (1024 MB)
[17394264.640000] sda: Write Protect is off
[17394264.640000] sda: Mode Sense: 03 00 00 00
[17394264.640000] sda: assuming drive cache: write through
[17394264.644000] SCSI device sda: 1999360 512-byte hdwr sectors (1024 MB)
[17394264.644000] sda: Write Protect is off
[17394264.644000] sda: Mode Sense: 03 00 00 00
[17394264.644000] sda: assuming drive cache: write through
[17394264.644000] sda: sda1
[17394264.644000] sd 2:0:0:0: Attached scsi removable disk sda
[17394264.644000] sd 2:0:0:0: Attached scsi generic sg0 type 0
[17394264.648000] usb-stor...

[Ulrich Lukas (ulrich-lukas)]

Sorry, forgot to mention: There are two USB-controllers in this computer: the onboard "VT82xxxxx UHCI USB 1.1 Controller", and an add-on USB-2.0-PCI-card.

[kjivan (kjivan)]

I am having the same problem. I did a clean install to Edgy upon release and currently have the kernel vmlinuz-2.6.17-10-generic. I am getting the same error and i can try to attach files but I am not very well versed with linux. Also i would like to note that I had dapper for at least 6 months and have been regularly updating and had no trouble with my usb then. Now i get that error "device not accepting address 3, error -110" in my syslog.

I have tried

To temporary solve the problem, disable USB 2.0 by this way :
$sudo modprobe -r ehci_hcd
$sudo echo "blacklist ehci_hcd" > /etc/modprobe.d/blacklist-ehci

To get USB 2.0 back :
$sudo rm /etc/modprobe.d/blacklist-ehci
$sudo modprobe ehci-hcd

but it didn't seem to work and I am unsure as to how to change the kernel exactly

[inflamestory (dory-thibault)]

I had exactly the same problem as you guys on a 2.6.17 kernel (edgy) and I've tried to unload the ehci_hcd module.
That worked, but only with usb1.1 and not all the time...

After some research on google I've found this that worked great!
Just add "irqpoll' to the boot option of your kernel in menu.lst...

With this fix, I've usb2.0 and my usb memory key work all the time...

Hope it help.

[Robert Penz (robert-penz-name)]

Initial tests comfim that also on my system, but I need to do addition checks to be really sure. If I don't write an other comment it means that it is also true for me.

[wannes (wannes)]

Adding irqpoll works for me (edgy).
Yay, got back my USB2 speed :-)

[Jacob Winski (winski)]

Bug confirmed. Neither rmmod ehci_hcd nor irqpoll are acceptable solutions because ehci_hcd disables USB 2.0 support and irqpoll is ridden with a lot of bugs for users (doing a quick irqpoll search on the internet reveals this). Also, adding kernel options such as irqpoll for all users should not acceptable. There must be another fix for this.

One small tidbit that may help: using almost identical hardware, with identical USB controllers, the computer with two USB ports has problems, the one with only one USB ports does not.

OUTPUT OF 1 USB PORT COMPUTER (w/o problems):

$ lsusb
Bus 004 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000

$ lspci
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)

$ cat /proc/bus/usb/devices
T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.17-10-generic uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.2
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.17-10-generic uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.1
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.17-10-generic uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:1d.0
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.17-10-generic ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:1d.7
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms

$ cat /proc/interrupts
           CPU0
  0: 1439132 XT-PIC timer
  1: ...

[Jacob Winski (winski)]

Apologies for the long output above - it was meant to be attached.

One small correction. The lsmod output differs because on one computer, a usb device was plugged in and then removed while on the other it was not. If both computers have a usb device plugged in and then removed, they show the same outputs. For example, once a usb device is plugged and then removed from the computer with 1 usb port (and w/o problems), the output changes to:
$ lsmod | grep usb
usb_storage 75072 0
scsi_mod 144648 3 sg,sd_mod,usb_storage
libusual 17040 1 usb_storage
usbcore 134912 5 usb_storage,libusual,uhci_hcd,ehci_hcd

[SirKillalot (sirkillalot)]

Confirming that it DOESN'T work for me neither adding irqpoll to the boot options. Awaiting a bugfix...

[Joel Oliver (joelol75)]

Confirming as well. I believe it is a problem with the BIOS in my case as I cannot mount 2 different USB devices in WinXP (Dual boot, no I never really use XP) and these work fine on my other Edgy system. One is a 80GB hard drive usb and the other is a ATI remote wonder. WinXP sees them right off the bat and says they are 'MALFUNTIONING' and to replace them. The device name usually pops up, doesn't get the name though....

System is GigaByte GA-M55plus-S3G (F6 BIOS)
Athlon 64x2 4200+ (32bit Edgy)
Integrated Geforce6100
NForce 430

I believe the 6100/430 part is the important one as my 'google' research shows this problem all over with 6100/6150 on ASUS boards as well.

Things I tried:
modprobe -r ehci_usb

Booting with the irqpoll noapic nolapic acpi=off options (In various combos and created a keyboard that doubles everything i type.

dmesg attached

[Joel Oliver (joelol75)]

OK, all the usb things I have been testing are ending up with corrupt firmware. Moved my gripe to #77358

[Simon Marlow (simonmar)]

Also confirmed here, dmesg & lspci attached.

Workaround 1: "rmmod ehci_hcd" does *not* work, at least with the USB flash key I'm testing with here.

Workaround 2: adding 'irqpoll' kernel parameter *does* work (although there are some odd-looking log messages with this USB key plugged in, see attached dmesg output).

[Simon Marlow (simonmar)]

oops, trying attachment again.

[Akkana Peck (akkzilla)]

Yet another case. It just started happening to me: I've been running Edgy on this machine since shortly after it released, and I use external usb-storage devices (cameras and mp3 players) at least every couple of days, without any problems until today.

A few days ago I dist-upgraded and picked up some seemingly innocuous packages: gnupg_1.4.3, tzdata_2007b, mozilla-thunderbird, tcpdump_3.9.4, libxine-main1_1.1.2, libxine1_1.1.2. None of these seem like they could possibly have any effect on the kernel, udev or hal. Yet now, when I plug in my camera or mp3 player (to either a usb2 hub or a usb1 hub, both of which have worked in the past), I get various error messages in dmesg (a little different each time) and /dev/sde either isn't created, or it's created briefly but as soon as anything tries to read from it (e.g. to read the partition table and create sde1), the device disappears again.

It's sde because I have a built-in multicard reader (cf, sm, ms, sd/mmc) which takes up sda through d. The four usb multicard devices are seen at boot time and work just fine. It's just hotplugged devices that don't work.

Kernel is 2.6.17-11-generic (but the problems happen with -10 too). lspci says the USB controller is a Via VT82xxxxx UHCI USB 1.1 Controller (rev 81).

After googling and finding lots of people with similar problems and reading their workarounds, I tried modprobe -r ehci_hcd followed by modprobe ehci_hcd, and that worked -- this time, but the pages I found suggest it won't be a reliable fix. And nobody seems to have come up with a way to get the system to do this on its own (well, I suppose I could add a line like
modprobe -r ehci_hcd; sleep 10; modprobe ehci_hcd
to one of the boot scripts, but ick).

Attaching a log of dmesg snippets.

If anyone comes up with an explanation for why this might have suddenly started happening, or suggestions for good automated ways of solving it, I'd be most grateful!

[matthewj (mattnalley)]

I have 2 USB2.0 keys that work fine under with Ubuntu Edgy 2.6.17-11, but my iPod cannot be (auto)mounted. I did a lot of google'ing and asking questions on IRC, but no matter what I tried I couldn't mount the iPod manually.

I also tried adding "irqpoll" to the boot options...no help there.

The only way I can get Ubuntu to recognize the iPod is by running "sudo modprobe -r ehci_hcd" at which point it automounts within 5-10 seconds, but it only has USB1 support, which is painfully slow for MP3 transfers. Activating ehci_hcd again unmounts the iPod and produces similar error messages from dmesg, so no luck getting USB2 support.

Attached is the output from dmesg with comments indicating my actions that produced the notices/errors.

[Chris Tan (chris-tan)]

My computer is not USB 2.0, but I have the same problems with my printer.

When I turn my printer off, and then back on at a later time, it just doesn't work. I've tried using irqpoll, but to no avail. A temporary solution is to just unload and reload the USB module:

sudo modprobe -r uhci_hcd
sudo modprobe uhci_hcd

[Akkana Peck (akkzilla)]

To anyone still fighting this bug, I might have a clue. I just upgraded to Feisty to see if the bug might be fixed. I plugged in an mp3 player which had almost always triggered the "dead device" I/O errors in edgy, then checked dmesg.

It didn't show up as sde as it should have -- but it gave a much more helpful error message. Like a dufus I forgot to write down the exact error message, and now I'm no longer seeing it, but it had something to do with "not enough power." All my testing has been through unpowered hubs. That was never a problem in the past, but maybe the kernel has become more picky about that recently.

I found a power connector for my USB2 hub, plugged it in, and now the device seems to be working under feisty. We'll see if it keeps working; but anyone still having this problem, try using a powered hub or no hub at all.

[BobMcD (mcbobbo)]

Disclaimer: This could be COMPLETELY UNRELATED, but...

I solved this same persistant problem on my system (Feisty 2.6.20-16) by using the instructions at this link:

http://www.vmware.com/community/message.jspa?messageID=575305#575305

Specifically:

<quote>
Found this information from another post in the Ubuntu Linux forums, maybe it is relevant in other linux ditros...

USB Devices Are Not Available on Some Linux hosts, the VM > Removable Devices > USB Devices Menu Is Empty

In short, the problem was Ubuntu not mounting USBFS to /proc/bus/usb.

Solution:
sudo mount -t usbfs none /proc/bus/usb

and add the following line in the /etc/fstab file:
usbfs /proc/bus/usb usbfs auto 0 0
</quote>

[Victor Mendonça (victorbrca)]

  I'm having similar problem, difference is that is only my iPod that does no work, and it worked today. Reloading and/or disabling modules does no work...

  I'm using a laptop, power is plugged. Tried different USB ports. Tried "rmmod uhci_hcd" "modprobe uhci_hcd", "modprobe -r uhci_hcd" "modprobe uhci_hcd", "modprobe -r ehci_hcd" "modprobe ehci_hcd", "modprobe -r uhci_hcd", none of these worked.

  The only thing I remember doing today was "apt-get clean", "aptitude clean" and "aptitude autoclean".

  I've been having problems with the iPod for a while. Sometimes mount, others don't. But now it won't mount after many, many attempts.

  Using Ubuntu Edgy, 2.6.17-11-generic.

Vic.

[Victor Mendonça (victorbrca)]

Ok, I got more data...

I plugged another iPod nano (2G) and it worked. Umounted it and plugged mine, it also worked. Umounted a couple of times and now is not recognizing anymore. It's not even charging or giving the msg to not unplug.

I them tried plugging a non-powered USB hub (with a half inch cable), plugging and external USB HD, a USB pen and iPod 4G on hub. Also did not work.

Attached is a file with the mesgs I got from dmesg as I did all of these steps.

Regards,

Vic.

[Victor Mendonça (victorbrca)]

Sorry for posting so many times consecutive. I have resolved the issue. Discovered it was all due to a defective cable....

Regards,

Vic.

[Henrik Nilsen Omma (henrik)]

Moving milestone.

[Matt England (launchpad-net-mengland)]

Is a fix for this bug available? I notice the bug is confirmed.

I experience similar symptoms in this scenario:

Transferring large files (600MB+) _to_ an external USB2 device.

I'm confident this is not a hardware problem because:

Transfers of the exact same files in WinXP experience no issue or performance loss.
Transfers of files *from* the USB2 device in the same linux-Ubuntu environment (6.06.1 with upgrades; kernel 2.6.15-26-386) works with no problems (ie, writes to device don't work, reads do).

So...when if ever will this bug be fixed? I'd like to try said fix on my system to see if it fixes my issue. If this is not scheduled for a fix, it would be nice to no workarounds--eg, recommended kernel flavor(s), patches, different distributions?

[Marc Horowitz (marc-mit)]

I haven't tried these patches on a newer kernel, but I bet they would help if they were updated and included in the kernel:

http://web.mit.edu/xiphmont/Public/kernel/

Unfortunately, Monty told me they were rejected. Perhaps someone reading this can get that decision revisited?

[Zenigata (drebon)]

Hello,

I just found that bug report, and I'd like to say that I have exactly the same issue with a laptop under gutsy (kernel 2.6.22-14-generic).

The odd thing is that it seems to me that sometimes I have that problem (during boot I can see usb "6-3 not accepting addres X error -110") and some other I just do not get any error messages (and the boot time is much shorter).

[Gord Wait (gordwait)]

Many cases of this seem to be related to bad cabling - either your external USB cable, or internal USB may not be able to run at USB "High Speed"/

Details:
http://ubuntuforums.org/showthread.php?p=3991125#post3991125
Enhancement request:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/177430/

[Robert Penz (robert-penz-name)]

Hi

I my case its a software problem, because the old kernel works and it works also with newer kernels if I activate irqpoll.

[Leann Ogasawara (leannogasawara)]

Hi All,

Just curious if this is still an issue with the latest Hardy Heron 8.04 Alpha release which is to be the next LTS release. The Hardy Heron Alpha series was recently released which contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha release from http://cdimage.ubuntu.com/releases/hardy/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/ . Thanks.

[Leann Ogasawara (leannogasawara)]

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.

[Jean-Baptiste Lallement (jibel)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks,

[Maxim Levitsky (maximlevitsky)]

I have a usb printer, HP1018 and I suspect that it has this bug

I have messages like this one:

usbfs: USBDEVFS_CONTROL failed cmd python rqt 128 rq 6 len 255 ret -110

and removing ehci-hcd _or_ removing uhci_hcd makes it work perfectly

[Maxim Levitsky (maximlevitsky)]

I think I have this bug in ubuntu 8.10

[Maxim Levitsky (maximlevitsky)]

Also removing CONFIG_USB_EHCI_ROOT_HUB_TT fixed this issue for me

[Leann Ogasawara (leannogasawara)]

I'm reclosing the Dapper task and will reopen against the actively developed "linux" kernel package. @Maxim, could you test the latest jaunty 9.04 Release Candidate? Please let us know your results.

http://cdimage.ubuntu.com/daily-live/current/

[Maxim Levitsky (maximlevitsky)]

@Leann Ogasawara

I have jaunty, and I use -git kernels anyway.
What I eventually found out that I am not affected by this bug, my printer doesn't always work anyway
I don't use it much now, but in future I will test it with better cable which I suspect.

[tmeller (thomas-meller)]

root@lina:~# dmesg | tail
[ 3400.542571] usb 1-2: device descriptor read/64, error -62
[ 3400.814093] usb 1-2: new full speed USB device using ohci_hcd and address 12
[ 3401.221494] usb 1-2: device not accepting address 12, error -62
[ 3401.397248] usb 1-2: new full speed USB device using ohci_hcd and address 13
[ 3401.804666] usb 1-2: device not accepting address 13, error -62

This is what I get on a hardy Install on a ASRock 939sli32 eSATA2 mobo.
I have exactly the same hardy on an IBM T40 notebook, where the symptom never showed up.
Kernel:
ASRock 2.6.24-24-generic #1 SMP Wed Apr 15 15:54:25 UTC 2009 i686 GNU/Linux
T40 2.6.24-24-generic #1 SMP Wed Apr 15 15:54:25 UTC 2009 i686 GNU/Linux

I had the problem to use a garmin etrex venture hc, firmware 2.70.
The notebook was connected to a hub which was connected to the GPSr. With or without hub, the device would always show up. With dapper perfectly, with hardy I hat to 'lsusb -t' first, when connected via hub.
The ASRock was connected directly to the garmin when the above dmesgs showed up.
I then connected the hub, using the same cable, and it worked. This time it worked with the ehci driver.

The hub is powered optionally. The notebook was not able to drive an external disk when connected via hub, so I bought the power supply.
Up to now, I did not test on the sli32 with this hub unpowered as that's no option for me.

If you ask me, this is a hardware rather than a driver problem. USB is cheap. :-)

[tmeller (thomas-meller)]

root@lina:~# lsusb
Bus 004 Device 003: ID 091e:0003 Garmin International GPSmap (various models)
Bus 004 Device 002: ID 05e3:0606 Genesys Logic, Inc. D-Link DUB-H4 USB 2.0 Hub
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
root@lina:~#

Just forgot to add this...

[Leann Ogasawara (leannogasawara)]

Closing per the previous comments.