device descriptor read/64, error -62, USB Not functioning

Asked by Slevin57 on 2007-03-18

dmesg:

[ 59.276000] hub 3-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
[ 59.332000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 59.332000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 59.540000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 59.540000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 59.744000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 59.744000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 59.948000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 59.948000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 60.152000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 60.152000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 60.152000] hub 3-0:1.0: Cannot enable port 4. Maybe the USB cable is bad?
[ 60.208000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 60.208000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 60.412000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 60.412000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 60.616000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 60.616000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 60.824000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 60.824000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 61.032000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 61.032000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 61.032000] hub 3-0:1.0: Cannot enable port 4. Maybe the USB cable is bad?
[ 61.092000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 61.092000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 61.296000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 61.296000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 61.504000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 61.504000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 61.712000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 61.712000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 61.920000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 61.920000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 61.920000] hub 3-0:1.0: Cannot enable port 4. Maybe the USB cable is bad?
[ 61.976000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 61.976000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 62.180000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 62.180000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 62.384000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 62.388000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 62.592000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 62.592000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 62.796000] ehci_hcd 0000:00:13.2: port 4 reset error -110
[ 62.800000] hub 3-0:1.0: hub_port_status failed (err = -32)
[ 62.800000] hub 3-0:1.0: Cannot enable port 4. Maybe the USB cable is bad?
[ 63.148000] usb 1-4: new low speed USB device using ohci_hcd and address 10
[ 63.328000] usb 1-4: device descriptor read/64, error -62
[ 63.616000] usb 1-4: device descriptor read/64, error -62
[ 63.896000] usb 1-4: new low speed USB device using ohci_hcd and address 11
[ 64.060000] usb 1-4: device descriptor read/64, error -62
[ 64.336000] usb 1-4: device descriptor read/64, error -62
[ 64.616000] usb 1-4: new low speed USB device using ohci_hcd and address 12
[ 65.028000] usb 1-4: device not accepting address 12, error -62
[ 65.208000] usb 1-4: new low speed USB device using ohci_hcd and address 13
[ 65.616000] usb 1-4: device not accepting address 13, error -62

My USB ports are not functioning at all.

lsusb:
chris@chris-laptop:~$ lsusb
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

It reveals all three are there, it just doesn't recognize anything thats plugged in. I'm trying to get my USB Mouse, keyboard and HP 1020 printer working.

I've searched the forums many times over and none of those solutions have worked.

I have an Acer Aspire 5100 w/ AMD 64 Turion X2 Processor

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
2007-03-18
Last reply:
2010-12-03
Fox3 (pmudmap5) said : #1

Problems with USB under Feisty (7.04). This was not a problem under Edgy.

While this fails at boot after the system comes up, I can unplug/replug and everything appears normal.

Happens with the supplied kernels (2.6.20.12-generic and .13) as well as my custom version.

Messages out of dmesg:

[ 5917.628000] usb 3-2: new full speed USB device using ohci_hcd and address 2
[ 5918.761000] hub 3-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
[ 5919.891000] hub 3-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
[ 5921.021000] hub 3-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
[ 5922.151000] hub 3-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
[ 5922.412000] usb 3-2: new full speed USB device using ohci_hcd and address 6
[ 5922.594000] usb 3-2: configuration #1 chosen from 1 choice
[ 5922.731000] usbcore: registered new interface driver usbserial
[ 5922.732000] drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
[ 5922.733000] usbcore: registered new interface driver usbserial_generic
[ 5922.733000] drivers/usb/serial/usb-serial.c: USB Serial Driver core
[ 5922.744000] drivers/usb/serial/usb-serial.c: USB Serial support registered for Garmin GPS usb/tty
[ 5922.744000] garmin_gps 3-2:1.0: Garmin GPS usb/tty converter detected
[ 5922.745000] usb 3-2: Garmin GPS usb/tty converter now attached to ttyUSB0
[ 5922.745000] usbcore: registered new interface driver garmin_gps
[ 5922.746000] drivers/usb/serial/garmin_gps.c: garmin gps driver v0.28
[ 6166.246000] usb 3-2: USB disconnect, address 6
[ 6166.247000] garmin_gps 3-2:1.0: device disconnected
[ 6454.553000] usb 1-2: new low speed USB device using ohci_hcd and address 12
[ 6454.718000] usb 1-2: device descriptor read/64, error -62
[ 6454.984000] usb 1-2: device descriptor read/64, error -62
[ 6455.242000] usb 1-2: new low speed USB device using ohci_hcd and address 13
[ 6455.407000] usb 1-2: device descriptor read/64, error -62
[ 6455.673000] usb 1-2: device descriptor read/64, error -62
[ 6455.931000] usb 1-2: new low speed USB device using ohci_hcd and address 14
[ 6456.337000] usb 1-2: device not accepting address 14, error -62
[ 6456.494000] usb 1-2: new low speed USB device using ohci_hcd and address 15
[ 6456.900000] usb 1-2: device not accepting address 15, error -62
[ 6481.556000] usb 1-2: new low speed USB device using ohci_hcd and address 16
[ 6481.720000] usb 1-2: device descriptor read/64, error -62
[ 6481.985000] usb 1-2: device descriptor read/64, error -62
[ 6482.243000] usb 1-2: new low speed USB device using ohci_hcd and address 17
[ 6482.407000] usb 1-2: device descriptor read/64, error -62
[ 6482.672000] usb 1-2: device descriptor read/64, error -62
[ 6482.930000] usb 1-2: new low speed USB device using ohci_hcd and address 18
[ 6483.334000] usb 1-2: device not accepting address 18, error -62
[ 6483.491000] usb 1-2: new low speed USB device using ohci_hcd and address 19
[ 6483.895000] usb 1-2: device not accepting address 19, error -62

Hope this helps! Thanks.

Fox3 (pmudmap5) said : #2

Just an update.

WIth all the updates to feisty, the problem still exists.

HTH!

Thanks!

Fox3 (pmudmap5) said : #3

Further update. Now camera and palm pilot will not spawn the /dev/ttyUSB* entries :-(.

Trying re-installing udev.

Fox3 (pmudmap5) said : #4

re-installing udev makes no difference, lsusb shows the devices and they do show up in usbview, but I am unable to use them anymore.

Was OK yesterday, after updates (still telling me that there is a new Kubuntu, but no place to click to install it) today things seem to have quit working.

Hope this helps!

John Zero (johnzero) said : #5

I'm having the same problems, too!
I was running Edgy, have upgraded to Feisty (beta).

[ 123.432329] usb 2-1.2: new high speed USB device using ehci_hcd and address 4
2
[ 123.504433] usb 2-1.2: device descriptor read/64, error -71
[ 123.680386] usb 2-1.2: device descriptor read/64, error -71
[ 123.856341] usb 2-1.2: new high speed USB device using ehci_hcd and address 4
3
[ 123.928320] usb 2-1.2: device descriptor read/64, error -71
[ 124.104399] usb 2-1.2: device descriptor read/64, error -71
[ 124.280352] usb 2-1.2: new high speed USB device using ehci_hcd and address 4
4
[ 124.688085] usb 2-1.2: device not accepting address 44, error -71
[ 124.760352] usb 2-1.2: new high speed USB device using ehci_hcd and address 4
5
[ 125.168421] usb 2-1.2: device not accepting address 45, error -71
[ 125.240348] usb 2-1.3: new low speed USB device using ehci_hcd and address 46
[ 125.312328] usb 2-1.3: device descriptor read/64, error -32
[ 125.488533] usb 2-1.3: device descriptor read/64, error -32
[ 125.664362] usb 2-1.3: new low speed USB device using ehci_hcd and address 47
[ 125.736343] usb 2-1.3: device descriptor read/64, error -32
[ 125.912296] usb 2-1.3: device descriptor read/64, error -32
[ 126.088251] usb 2-1.3: new low speed USB device using ehci_hcd and address 48
[ 126.496022] usb 2-1.3: device not accepting address 48, error -32
[ 126.568254] usb 2-1.3: new low speed USB device using ehci_hcd and address 49
[ 126.976005] usb 2-1.3: device not accepting address 49, error -32
[ 127.048246] usb 2-1.4: new full speed USB device using ehci_hcd and address 5
0
[ 127.120226] usb 2-1.4: device descriptor read/64, error -32
[ 127.296306] usb 2-1.4: device descriptor read/64, error -32

John Zero (johnzero) said : #6

I've found this on other forums:
modprobe -r ehci_hcd

This actually helped! (But it might not be a real good solution)

raman aka morph (ramannanda9) said : #7

ya the problem is that ehci_hcd loads before ohci_hcd or maybe the vice versa .
and only solution to this is to use >>"modprobe -r ehci_hcd "<< and the device will be mounted .
the problem is due to parallel running of these modules maybe this will help?

gsoerjono (gatut-soerjono) said : #8

Thank you very much...
I have srtuggled all day long I have proceeded with # modprobe -r ehci_hcd and it works perfectly.

my question is whether i need always -r ehci_hcd?

Thanks .

Whilst >>"modprobe -r ehci_hcd "<< will unblock the usb ports, it removes the the high speed (480Mbs) USB2.0 controller, so all tranfers are reduced to USB1.0/1.1. This will make the transfer of data from large mass storage devices very slow indeed.

BTW, the same effect can be achieved by disabling the onboard USB2.0 controller in the BIOS.

What we require is a kernel fix for this problem, which only occurs on certain motherboards. I have two laptops and VIA EPIA-CN1300 based system which do not suffer this problem, but my Gigabyte MA-78GPM-DS2H, AMD Phenom 9950 based system locks up every time a USB mass storage device is a accessed.

Paco Riviere (pacoriviere) said : #10

Same problem with Hardy 8.04 - Kernel, motherboard and USB hub details follow:

~$ uname -a
Linux fujix 2.6.24-23-generic #1 SMP Wed Apr 1 21:47:28 UTC 2009 i686 GNU/Linux
~$ hwinfo | grep Mother
  pci.subsys_product = 'GA-7VM400M/7VT600 Motherboard'
  Model: "Giga-byte GA-7VM400M/7VT600 Motherboard"
  SubDevice: pci 0xe000 "GA-7VM400M/7VT600 Motherboard"
~$ lsusb | grep 'Bus 003'
Bus 003 Device 004: ID 058f:9254 Alcor Micro Corp. Hub
Bus 003 Device 001: ID 0000:0000
~$ dmesg | grep failed
[ 20.539336] hub 3-2:1.0: hub_port_status failed (err = -62)
[ 20.542328] hub 3-2:1.0: hub_port_status failed (err = -62)
[ 20.545320] hub 3-2:1.0: hub_port_status failed (err = -62)
[ 20.548315] hub 3-2:1.0: hub_port_status failed (err = -62)
[ 22.815726] PM: Resume from disk failed.

Same/similar problem with Karmic 9.10 - Kernel, motherboard and USB hub details follow:
~$ uname -a
Linux farkstar 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux
 ~$ hwinfo|grep pci.subsys_product
  pci.subsys_product_id = 65329 (0xff31)
  pci.subsys_product_id = 65329 (0xff31)
  pci.subsys_product_id = 28820 (0x7094)
  pci.subsys_product_id = 65329 (0xff31)
  pci.subsys_product_id = 0 (0x0)
  pci.subsys_product_id = 65329 (0xff31)
  pci.subsys_product_id = 65329 (0xff31)
  pci.subsys_product_id = 65329 (0xff31)
  pci.subsys_product_id = 65329 (0xff31)
  pci.subsys_product_id = 65329 (0xff31)
  pci.subsys_product_id = 65329 (0xff31)
  pci.subsys_product_id = 65329 (0xff31)
  pci.subsys_product_id = 0 (0x0)
  pci.subsys_product_id = 65329 (0xff31)
~$ dmesg |grep USB
<snip>
[ 3.512053] usb 3-4: new low speed USB device using ohci_hcd and address 4
[ 4.268073] usb 3-4: new low speed USB device using ohci_hcd and address 5
[ 5.012054] usb 3-4: new low speed USB device using ohci_hcd and address 6
[ 5.596062] usb 3-4: new low speed USB device using ohci_hcd and address 7
[ 6.004103] hub 3-0:1.0: unable to enumerate USB device on port 4
~$ dmesg |grep usb
[ 3.226104] usbcore: registered new interface driver usbhid
[ 3.226108] usbhid: v2.6:USB HID core driver
[ 3.512053] usb 3-4: new low speed USB device using ohci_hcd and address 4
[ 3.696023] usb 3-4: device descriptor read/64, error -62
[ 4.000057] usb 3-4: device descriptor read/64, error -62
[ 4.268073] usb 3-4: new low speed USB device using ohci_hcd and address 5
[ 4.448051] usb 3-4: device descriptor read/64, error -62
[ 4.732039] usb 3-4: device descriptor read/64, error -62
[ 5.012054] usb 3-4: new low speed USB device using ohci_hcd and address 6
[ 5.420693] usb 3-4: device not accepting address 6, error -62
[ 5.596062] usb 3-4: new low speed USB device using ohci_hcd and address 7
[ 6.004044] usb 3-4: device not accepting address 7, error -62

kenjiru (kenjiru) said : #12

I have the same problem:
root@kenjiru:/home/radu# dmesg | grep error
[ 100.064026] usb 2-1: device descriptor read/64, error -62
[ 100.348022] usb 2-1: device descriptor read/64, error -62
[ 100.804055] usb 2-1: device descriptor read/64, error -62
[ 101.085426] usb 2-1: device descriptor read/64, error -62
[ 101.784167] usb 2-1: device not accepting address 4, error -62
[ 102.395689] usb 2-1: device not accepting address 5, error -62

Tony T (tonytovar) said : #13

After all these years I assume the original poster has moved on! But i just recently started having a similar issue on a desktop running Ubuntu 9.10. One week my add-on card reader worked, the next it didn't. In the Log Viewer I saw the error message,
 > device descriptor read/64, error -62

I thought there might have been a kernel upgrade in the interim but when I tried booting from all the old kernels on my system, none worked. Still, I really thought this was a software regression. Since I was on an 'old' version of Ubuntu I decided to upgrade to 10.04, but this didn't work either.

Finally, from Googling the error message I found an old post that mentioned the hardware. I didn't think my card reader could have spontaneously stopped working (and it's only a couple months old, besides) but I decided to try an experiment. It was an internal unit with an internal-type USB connector to the motherboard. I simply moved it from one port to another and it started working again! Not sure if it just needed to be disconnected/reconnected, i.e., the same original port would have worked.

Actually, this might indicate that the port used by the card reader cannot be initialized first? That by disconnecting then reconnecting it, I might have forced the system to re-recognize it?

Tony T (tonytovar) said : #14

Oh, and I forgot to add a troubleshooting tip:

Boot from a LiveCD and see if your USB works? That will tell you if the original kernel works, and maybe also if a 'fresh' config works.

Almufadado (almufadado) said : #15

This affect this motherboard too
GA-TRC410MN-RH
This comes with a packard bell imedia ???? (not even the right model is given to the consumer !!!)

Dec 3 21:24:31 ??? kernel: [ 1.728099] usb 2-2: device descriptor read/64, error -62
Dec 3 21:24:31 ??? kernel: [ 1.732714] ohci1394 0000:02:06.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22

Report from sysinfo
MOTHERBOARD
 Host bridge
  ATI Technologies Inc Radeon Xpress 200 Host Bridge (rev 01)
  Subsystem: ATI Technologies Inc Radeon Xpress 200 Host Bridge
 PCI bridge(s)
  ATI Technologies Inc RS480 PCI-X Root Port
  ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev 80) (prog-if 01)
  ATI Technologies Inc RS480 PCI-X Root Port
  ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev 80) (prog-if 01)
 USB controller(s)
  ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) (prog-if 10)
  ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) (prog-if 10)
  ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) (prog-if 10)
  ATI Technologies Inc IXP SB400 USB Host Controller (rev 80) (prog-if 10)
 ISA bridge
  ATI Technologies Inc IXP SB400 PCI-ISA Bridge (rev 80)
  Subsystem: Packard Bell B.V. Device e017
 IDE interface
  ATI Technologies Inc IXP SB400 IDE Controller (rev 80) (prog-if 82 [Master PriP])
  Subsystem: Packard Bell B.V. Device e017

lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/4p, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/4p, 12M

 lsusb -s 1:1 -v

Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 9 Hub
  bDeviceSubClass 0 Unused
  bDeviceProtocol 0 Full speed (or root) hub
  bMaxPacketSize0 64
  idVendor 0x1d6b Linux Foundation
  idProduct 0x0001 1.1 root hub
  bcdDevice 2.06
  iManufacturer 3
  iProduct 2
  iSerial 1
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 25
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xe0
      Self Powered
      Remote Wakeup
    MaxPower 0mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 1
      bInterfaceClass 9 Hub
      bInterfaceSubClass 0 Unused
      bInterfaceProtocol 0 Full speed (or root) hub
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0002 1x 2 bytes
        bInterval 255
can't get hub descriptor: Operation not permitted
cannot read device status, Operation not permitted (1)

when I connect a usb pen :
Dec 3 22:14:15 ???? kernel: [ 2999.240028] usb 1-1: device descriptor read/64, error -62
Dec 3 22:14:16 ???? kernel: [ 2999.524782] usb 1-1: device descriptor read/64, error -62
Dec 3 22:14:16 ???? kernel: [ 2999.804037] usb 1-1: new full speed USB device using ohci_hcd and address 11
Dec 3 22:14:16 ???? kernel: [ 2999.984035] usb 1-1: device descriptor read/64, error -62
Dec 3 22:14:16 ???? kernel: [ 3000.268036] usb 1-1: device descriptor read/64, error -62
Dec 3 22:14:17 ???? kernel: [ 3000.549032] usb 1-1: new full speed USB device using ohci_hcd and address 12
Dec 3 22:14:17 ???? kernel: [ 3000.956032] usb 1-1: device not accepting address 12, error -62
Dec 3 22:14:17 ???? kernel: [ 3001.133033] usb 1-1: new full speed USB device using ohci_hcd and address 13
Dec 3 22:14:18 ???? kernel: [ 3001.541022] usb 1-1: device not accepting address 13, error -62
Dec 3 22:14:18 ???? kernel: [ 3001.541081] hub 1-0:1.0: unable to enumerate USB device on port 1

This is a strange, tricky, non-supported by a non-supportive manufacturer.
So crazy that it come with win xp home, which can't be installed because it crashes the windows activation process. It will only accept windows 7 or Ubuntu ... so Ubuntu it is !

But now (after 30 tries to get the any system running) am faced with this error !!! I was thanking the lousy, bad-mannered, non-supportive Packard Bell to make me ... force me to install Ubuntu but now I can't copy the user files because I haven't got the USB running !!!

I have been searching for solutions but it seems this ati chipset is not very supported ... at least this chip.

Almufadado (almufadado) said : #16

Well if it any consolation ...

I tried windows 7 on this usb problem and they found the solution ... well they found a "sweep under the carpet" solution !

Amd/ATI, as usual, don't give any support ! But I found they have more Linux drivers on their new joint site !

In my case this is either
- This is probably a bios setting in this low cost (low quality/low consumer support) systems. In this type of systems, including this packard bell, they tend to limit the consumer choices to a minimum

- The ports are burnt (already had 2 cases when people over use the 5v thingy!)

My solution will by a new standard PCI USB hub, or a new motherboard ! kinda fire and forget :) !

One thing come out right from this troubles of mine : Ubuntu is becoming a awesome system ... Installation, graphics, sound and internet alright ! Even games could play a fps game in the low-end system ! : )

Can you help with this problem?

Provide an answer of your own, or ask Slevin57 for more information if necessary.

To post a message you must log in.