Comment 86 for bug 387161
Revision history for this message
| Mark Robinson (launchpad-zl2tod) wrote | #86 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I just ran into this situation too:
Feb 5 02:48:28 terrorbite kernel: [ 1478.220053] usb 2-1: new full speed USB device using ohci_hcd and address 32
Feb 5 02:48:28 terrorbite kernel: [ 1478.400385] usb 2-1: device descriptor read/64, error -62
Feb 5 02:48:29 terrorbite kernel: [ 1478.690035] usb 2-1: device descriptor read/64, error -62
Feb 5 02:48:29 terrorbite kernel: [ 1478.980039] usb 2-1: new full speed USB device using ohci_hcd and address 33
Feb 5 02:48:29 terrorbite kernel: [ 1479.160866] usb 2-1: device descriptor read/64, error -62
Feb 5 02:48:30 terrorbite kernel: [ 1479.450878] usb 2-1: device descriptor read/64, error -62
Feb 5 02:48:30 terrorbite kernel: [ 1479.740931] usb 2-1: new full speed USB device using ohci_hcd and address 34
Feb 5 02:48:30 terrorbite kernel: [ 1480.160031] usb 2-1: device not accepting address 34, error -62
Feb 5 02:48:30 terrorbite kernel: [ 1480.340098] usb 2-1: new full speed USB device using ohci_hcd and address 35
Feb 5 02:48:31 terrorbite kernel: [ 1480.760017] usb 2-1: device not accepting address 35, error -62
Feb 5 02:48:31 terrorbite kernel: [ 1480.760030] hub 2-0:1.0: unable to enumerate USB device on port 1
It turned out that the plug was not pushed fully home at the computer home.
I assume that one or both of the data lines were not making contact.
Sooo ... check your cables and connections before getting too keen on hacking at your system.
There would probably be some value in the drivers checking for the possibility of broken data lines and reporting them to the user. Something like "Data error on USB device. Check your cables and connections."