USB: device descriptor read/64, error -110

george55 · 2019-04-13 06:08:20

I have a micro-sd port on my laptop that I use to add capacity to my relatively small hard drive. However, when I boot the machine I am regularly unable to mount the card because of the following error:

[ +11.847354] usb 1-4: device descriptor read/64, error -110
[  +0.270006] usb 1-4: new full-speed USB device number 5 using xhci_hcd
[ +15.249836] usb 1-4: device descriptor read/64, error -110
[ +15.360160] usb 1-4: device descriptor read/64, error -110
[  +0.120063] usb usb1-port4: attempt power cycle
[  +0.709905] usb 1-4: new full-speed USB device number 6 using xhci_hcd
[  +5.019956] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  +0.220194] usb 1-4: Device not responding to setup address.
[  +0.219849] usb 1-4: device not accepting address 6, error -71
[  +0.150036] usb 1-4: new full-speed USB device number 7 using xhci_hcd
[Apr13 12:53] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[  +0.220235] usb 1-4: Device not responding to setup address.
[  +0.219866] usb 1-4: device not accepting address 7, error -71
[  +0.000101] usb usb1-port4: unable to enumerate USB device

I generally try removing the card, putting it back in, etc. for a while and suddenly it will start working:

[  +0.349903] usb 1-7: new high-speed USB device number 8 using xhci_hcd
[  +0.185507] usb 1-7: New USB device found, idVendor=05e3, idProduct=0727, bcdDevice= 2.08
[  +0.000006] usb 1-7: New USB device strings: Mfr=3, Product=4, SerialNumber=2
[  +0.000004] usb 1-7: Product: USB Storage
[  +0.000004] usb 1-7: Manufacturer: Generic
[  +0.000004] usb 1-7: SerialNumber: 000000000208

I am not sure, however, if this is a problem with my machine itself, or with the sd card. Sometimes when I have taken out the card, the errors continue to be added to dmesg, which gives me the idea it's a problem with the port itself, not the card. Any idea what could be causing this error?

seth · 2019-04-13 06:59:01

https://stackoverflow.com/questions/136 … -error-110

There's a good chance that the reader has an implicit switch and is only activated by pushing in a card (it's probably a push-eject one?)

george55 · 2019-04-13 07:34:27

Thanks. It could be, but there are a couple indicators this is not the case:

1) The issue is erratic; I have this problem sometimes at boot, sometimes I don't (say 5-10% of the time)
2) It is a push-eject system, but sometimes I will have to eject and put it back in once for it to start working, sometimes 5+ times, and sometimes it just starts working again after waiting 10-30 seconds
3) It does not seem to reactivate upon pushing the card back in. Even if I do, it takes another 2-30 seconds for it to start working with no indication in dmesg that pushing it back in made any change
4) In response to the linked thread: other devices using too much power would be odd, because it generally happens at boot with no other devices attached. Sometimes there is a mouse attached, but often there is no other device whatsoever drawing power

Any ideas what would match these symptoms?

seth · 2019-04-13 07:42:02

There's probably much more on the USB ("it's a bus, not a plug"), check lsusb and "lsusb -t"
Things that are often wired via USB and could suck some power (next to anything spinning, but that'd be rather external) are wifi/BT - you could try to deactivate those in the BIOS (is possible)

george55 · 2019-04-13 07:57:11

Thanks. I've checked it out:

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 05e3:0727 Genesys Logic, Inc. microSD Reader/Writer
Bus 001 Device 003: ID 0bda:5685 Realtek Semiconductor Corp. 
Bus 001 Device 002: ID 1d57:fa20 Xenta 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  $ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
    |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 3: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 3: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 7: Dev 8, If 0, Class=Mass Storage, Driver=usb-storage, 480M

I'm not sure... I've tried looking things up but it seems that the hub and Xenta are all related to the ports themselves. Do they draw power??

And if this is the case, wouldn't this be a poorly designed laptop (if its internal devices draw too much power to make the micro-sd port malfunction). It's certainly possible, but I would be quite sad to find out the laptop was built like that. It's a Dell Chromebook BTW, which also means I can't access a traditional bios to turn anything off...

seth · 2019-04-13 08:11:27

"0bda:5685 Realtek Semiconductor Corp." is a webcam, "1d57:fa20 Xenta " *seems* to be bluetooth.

Does the reader work reliably for "normal" use cases (ie. when you boot empty and slot a card somewhen after the DE started like you wanted to copy some photos from it)?

george55 · 2019-04-13 08:32:51

I have a small HD so there are some files on my SD card that I need to fully boot my system (some config files for i3). So I never fully boot without the drive being mounted.

Ah I see with the webcam/bluetooth. I'd be happy to somehow turn them off during boot but don't have a regular bios so this is difficult with the ChromeOS setup I have I'm afraid.

seth · 2019-04-13 12:03:04

You should try. Another possibility is that it simply takes a while for the reader to initialize and accessing it before messes that up.

Do you have a static fstab entry for the card (forcing the system to wait for it shoing up)?
What if you resort to "noauto,x-systemd.automount" to only mount it on accessing the path?

Arch Linux

#1 2019-04-13 06:08:20

USB: device descriptor read/64, error -110

#2 2019-04-13 06:59:01

Re: USB: device descriptor read/64, error -110

#3 2019-04-13 07:34:27

Re: USB: device descriptor read/64, error -110

#4 2019-04-13 07:42:02

Re: USB: device descriptor read/64, error -110

#5 2019-04-13 07:57:11

Re: USB: device descriptor read/64, error -110

#6 2019-04-13 08:11:27

Re: USB: device descriptor read/64, error -110

#7 2019-04-13 08:32:51

Re: USB: device descriptor read/64, error -110

#8 2019-04-13 12:03:04

Re: USB: device descriptor read/64, error -110

Board footer