usb 2-6: device descriptor read/64, error -110

danielbmarques · 2016-06-21 10:02:13

Hello,

I just finished installing Arch following the Beginners' guide and I think it went relatively well.
Then I restarted the computer and before I had the time to type "root" at the login field this showed up:

[    12.379593] usb 2-6: device descriptor read/64, error -110

And that's how it goes every time I boot.

After that I can type the username and login and it all seems to work ok.
I've been googling this for a long time and I found many posts with similar errors, but they're usually related to some usb device that doesn't work… in my case there are no usb devices connected at all (it's a laptop).

If I do connect a flash drive it shows up at /dev as it should, though.

I didn't even start using Arch yet. As I said, I just finished installing, so I don't know if this has any other consequences… but for now it's just really annoying.

Any ideas?

Thanks in advance,
Daniel

R00KIE · 2016-06-21 13:21:11

Are you sure you don't have any usb devices connected? Laptop have all kinds of "built-in" peripherals, such as webcams, cards readers, fingerprint readers, etc. Any of them can be connected to the usb bus.

If everything works then that message is just annoying, but I suppose it might be caused by a peripheral that takes a bit longer to initialize.

ewaller · 2016-06-21 14:55:16

To expand on what R00KIE said, that is a message that was posted to the console by the kernel. Log in should still work (press return and you will get a new log in prompt)

Edit: Then do a lsusb and see what the offending device is at that bus address

Last edited by ewaller (2016-06-21 14:55:52)

danielbmarques · 2016-06-21 20:05:51

Thank you for the answers.

ewaller, is the bus address that number in brackets that shows up before the error message? How do I know what's at that address?
Here's the result of lsusb:

Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 002 Device 005: ID 0cf3:e005 Atheros Communications, Inc.
Bus 002 Device 002: ID 0bda:5684 Realtek Semiconductor Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I have no idea what any of this means except for the "Card Reader Controller", which I assume is the SD card reader.

R00KIE, I guess I do have usb devices connected then, like the card reader. But I still don't know what's causing this problem or how to fix it.

Last edited by danielbmarques (2016-06-21 20:06:42)

ewaller · 2016-06-21 20:26:30

The two 16 bit hex numbers after 'ID' are the VID and PID (Vendor identification, product identification) for the devices. 0cf3:e005 is your Bluetooth. 0bda:5684 is your camera. 0bda:0129 is (indeed) your card reader.

Nothing is living at bus 2 address 6. Take a look at your journal for the last boot (journalcrl -b) and look around time t=12.85 seconds and find that message, Then, see what happened just before and just after.

Edit: I did not answer your question. Yes 2-6 is bus 2, device 6. Note that the device numbers are assigned arbitrarily when a device attaches and enumerates.

Last edited by ewaller (2016-06-21 20:27:56)

danielbmarques · 2016-06-21 21:13:24

Here's journalctl -b.

(Sorry about using a picture, I'm talking to you from a different computer and I didn't know which lines were relevant to copy by hand.)

I don't know if it has anything to do with anything, but there are other lines that are highlighted with contents that don't sound so good, like:

ACPI: NMI not connected to LINT1!

pmd_set_hug: Cannot satisfy [mem … ] with a huge-page mapping due to MTRR override.

 APCI Warning: SystemIO range [lots of numbers] conflicts with OpRegion [more numbers]

i915 0000:00:02.0: can't derive routing for PCI INT A

i915 0000:00:02.0: PCI INT A: not connected

ACPI Exception: AE_NOT_FOUND, Evaluating _DOD (20160108/video-1241)

r8169 0000:07:00.0: can't disable ASPM; OS doesn't have ASPM control

uvcvideo 1-5:1.0: Entity type for entity [4 different things] was not initialized!

could not read from '/sys/module/pcc_cpufreq/initstate': No such device

Should I worry about any of this stuff?
I'm sorry if I'm asking obvious or silly questions, this is the first time I ever use linux. I don't expect to fix every little problem, but since it's a fresh install and I followed the guide by the letter I'm just hoping everything is ok before I start ruining things.

PS: It says "usb 1-6" now because I restarted the computer in the meanwhile. This post suggested cutting the power for a while, so I removed the battery and the power cord for a few minutes and tried again, but it's still the same. Another post suggested turning off autosuspend, it didn't work either.

Last edited by danielbmarques (2016-06-22 19:43:43)

R00KIE · 2016-06-22 10:44:08

Please don't post large images, use an image hosting service and post the link to the images [1]. I'm giving you the opportunity to move the image to an image hosting service of your choice, but if you don't move it one of the moderators will move it, possibly to a service you might not like.

Regarding your actual problem, like I've said before, that may be caused by a usb device that takes longer to initialize and doesn't answer the first enumeration request, therefore there might be nothing you can do about it short of not using it if possible.

I suspect you may have to use 'lsusb -t' and go by bus-port instead of bus-device, at least on my machine what 'lsusb' says doesn't match to what can be found in '/sys/bus/usb/devices/'

[1] https://wiki.archlinux.org/index.php/Co … s_and_code

danielbmarques · 2016-06-22 20:10:28

Sorry for that, it's fixed now.

Well, then should I just ignore that and keep looking at that error every time I boot?
(It's an honest question, I'll take yes as an answer, haha).

I had some other problems trying to set up Gnome and I think I'll do another fresh install of Arch, but in the meanwhile I gave Ubuntu a try and I get the same error (actually I get many more, but this is still one of them).

So now I tried `lsusb -t` in Ubuntu and here's what it says:

/:    Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
      Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
      |__ Port 5: Dev 2, If 2, Class=Video, Driver=ucvideo, 480M
      |__ Port 5: Dev 2, If 2, Class=Video, Driver=ucvideo, 480M
      |__ Port 6: Dev 2, If 5, Class=Wireless, Driver=btusb, 12M
      |__ Port 6: Dev 2, If 5, Class=Wireless, Driver=btusb, 12M
      |__ Port 8: Dev 2, If 3, Class=Vendor Specific Class, Driver=rtsx_usb, 480M
/:    Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
      |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M

So does that mean `usb 2-6` is `Class=Wireless, Driver=btusb`? And the "bt" in "btusb" means "bluetooth", I guess?
You said "there might be nothing you can do about it short of not using it if possible"… I don't use bluetooth very often, so how would I go about "not using it"? I mean, except for physically disconnecting it from somewhere inside the laptop. Can I have it not connect automatically at boot and just start it if I need it sometime?

Edit: this didn't happen in Arch, but now with Ubuntu if I do `journalctl -p 3 -xb` I also get many errors related to bluetooth:

kernel: usb 206: device descriptor read/64, error -110
bluetoothd[820]: Failed to obtain handles for "Service Changed" characteristic
bluetoothd[820]: Not enough free handles to register service
bluetoothd[820]: Error adding Link Loss service
bluetoothd[820]: Not enough free handles to register service
bluetoothd[820]: Not enough free handles to register service
bluetoothd[820]: Not enough free handles to register service
(…)
bluetoothd[820]: Sap driver initialization failed

Using Arch I only got that first line.

Last edited by danielbmarques (2016-06-22 20:18:51)

R00KIE · 2016-06-22 21:00:10

I recommend you stick with Arch, which is the only distro we support here[1]. Output you get from another distro using a different kernel and different software versions has zero usefulness.

danielbmarques wrote:

Well, then should I just ignore that and keep looking at that error every time I boot?
(It's an honest question, I'll take yes as an answer, haha).

As far as I know there is nothing you can do, so the answer is yes. What you could try is including the (bluetooth?) driver in the initramfs in the hope the message shows up sooner and goes away once the login prompt comes around.

[1] https://wiki.archlinux.org/index.php/Co … .2Aonly.2A

danielbmarques · 2016-06-22 21:04:50

Yes, I'll go back to Arch, but since the error is the same I thought this could still be useful.
Anyway, thank you for your help, I'll look into the initramfs thing.

mis · 2016-06-22 21:09:52

If you don't care about the systemd boot messages you could give this a try https://wiki.archlinux.org/index.php/Silent_boot

danielbmarques · 2016-06-22 21:14:08

@mis Interesting, I'll see if I can get into the habit of checking the journal regularly and consider doing this. Thanks!

damian01w · 2016-06-22 22:14:30

Same error here with archlinux up-to-date. I'm using a Dell Inspiron 3443 laptop. Everything seems to be working fine ... but this error is very annoying.

Last edited by damian01w (2016-06-22 22:17:05)

danielbmarques · 2016-06-22 22:47:37

Yep, mine is a Dell Inspiron too.

Arch Linux

#1 2016-06-21 10:02:13

usb 2-6: device descriptor read/64, error -110

#2 2016-06-21 13:21:11

Re: usb 2-6: device descriptor read/64, error -110

#3 2016-06-21 14:55:16

Re: usb 2-6: device descriptor read/64, error -110

#4 2016-06-21 20:05:51

Re: usb 2-6: device descriptor read/64, error -110

#5 2016-06-21 20:26:30

Re: usb 2-6: device descriptor read/64, error -110

#6 2016-06-21 21:13:24

Re: usb 2-6: device descriptor read/64, error -110

#7 2016-06-22 10:44:08

Re: usb 2-6: device descriptor read/64, error -110

#8 2016-06-22 20:10:28

Re: usb 2-6: device descriptor read/64, error -110

#9 2016-06-22 21:00:10

Re: usb 2-6: device descriptor read/64, error -110

#10 2016-06-22 21:04:50

Re: usb 2-6: device descriptor read/64, error -110

#11 2016-06-22 21:09:52

Re: usb 2-6: device descriptor read/64, error -110

#12 2016-06-22 21:14:08

Re: usb 2-6: device descriptor read/64, error -110

#13 2016-06-22 22:14:30

Re: usb 2-6: device descriptor read/64, error -110

#14 2016-06-22 22:47:37

Re: usb 2-6: device descriptor read/64, error -110

Board footer