Usb 1-6: device descriptor read/64, error -110

Operating Systems & Open Source Linux
1

Has anybody seen this error before?

My hardware specs:

CPU: AMD Ryzen 9 5950X
Motherboard: Asus ROG STRIX X570-E GAMING WIFI II
RAM: 4x Crucial 32GB DDR4-3200 unbuffered, non-ECC RAM (128 GB total)
CPU HSF: Noctua NH-D15 with 2x Noctua NF-A14 industrial PPC 3000 PWM (ilo of the stock fans)
Video card: EVGA GeForce GTX 660
NIC: Mellanox ConnectX-4 100 Gbps Infiniband
Hard drive: 1x HGST 1 TB SATA 3 Gbps 7200 rpm HDD
PSU: Corsair CX750M
OS: CentOS 7.7.1908 (kernel-ml-5.14.15-1.el7.elrepo.x86_64)

I don’t even have a keyboard nor a mouse (USB nor otherwise) plugged into the system. I’m running it headless and controlling the system entirely remotely over SSH.

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

Shows up when the system is booting, and it will list it a bunch of times before proceeding to boot into the OS.

Once booted, the Infiniband network will be down, but if I unplug and replug the DAC, then said Infiniband network will come up.

If I roll back to kernel 5.4.196-el7.elrepo.x86_64, then this error message goes away.

Any ideas?

Thanks.

2

This means you have some peripheral on the mobo that is connected via the USB (integrated) but they system either cannot initialize it correctly or has mis-identified the device (modprobe) and is not getting the expected response after loading the driver.

I don’t know about your specific hardware (I am still on PoorDozer on the 990FX chipset), but a lot of the times, the sound solution is actually an integrated USB sound card.

If you were to do an lsusb -v, lsmod -v, and lspci -v, you might be able to see what device may be causing the issue. But if your system boots and you are not having adverse effects, then you can probably ignore it.

3

Thanks. I’ll probably try that, and see if it comes up with anything.

The weird thing is that it is having (apparently) and adverse reaction with my Infiniband card because that’s the device that I would need to unplug and re-plug the DAC.

I’ll see what I can find out.

Thank you.

4

So I updated the kernel again back to 5.14.15 and here’s the output from dmesg of the errors when the system is booting up:

# dmesg | grep usb
[    0.768900] usbcore: registered new interface driver usbfs
[    0.768903] usbcore: registered new interface driver hub
[    0.768907] usbcore: registered new device driver usb
[    0.824102] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.14
[    0.824103] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.824104] usb usb1: Product: xHCI Host Controller
[    0.824105] usb usb1: Manufacturer: Linux 5.14.15-1.el7.elrepo.x86_64 xhci-hcd
[    0.824106] usb usb1: SerialNumber: 0000:06:00.1
[    0.824360] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    0.824367] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.14
[    0.824368] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.824368] usb usb2: Product: xHCI Host Controller
[    0.824369] usb usb2: Manufacturer: Linux 5.14.15-1.el7.elrepo.x86_64 xhci-hcd
[    0.824369] usb usb2: SerialNumber: 0000:06:00.1
[    0.825102] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.14
[    0.825102] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.825103] usb usb3: Product: xHCI Host Controller
[    0.825104] usb usb3: Manufacturer: Linux 5.14.15-1.el7.elrepo.x86_64 xhci-hcd
[    0.825104] usb usb3: SerialNumber: 0000:06:00.3
[    0.825362] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    0.825369] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.14
[    0.825370] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.825370] usb usb4: Product: xHCI Host Controller
[    0.825371] usb usb4: Manufacturer: Linux 5.14.15-1.el7.elrepo.x86_64 xhci-hcd
[    0.825371] usb usb4: SerialNumber: 0000:06:00.3
[    0.825509] usb: port power management may be unreliable
[    0.825963] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.14
[    0.825964] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.825964] usb usb5: Product: xHCI Host Controller
[    0.825965] usb usb5: Manufacturer: Linux 5.14.15-1.el7.elrepo.x86_64 xhci-hcd
[    0.825965] usb usb5: SerialNumber: 0000:0c:00.3
[    0.826093] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    0.826100] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.14
[    0.826100] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.826101] usb usb6: Product: xHCI Host Controller
[    0.826101] usb usb6: Manufacturer: Linux 5.14.15-1.el7.elrepo.x86_64 xhci-hcd
[    0.826102] usb usb6: SerialNumber: 0000:0c:00.3
[    0.826200] usbcore: registered new interface driver usbserial_generic
[    0.826202] usbserial: USB Serial support registered for generic
[    0.826610] usbcore: registered new interface driver usbhid
[    0.826610] usbhid: USB HID core driver
[    1.063604] usb 1-5: new high-speed USB device number 2 using xhci_hcd
[    1.063610] usb 3-4: new full-speed USB device number 2 using xhci_hcd
[    1.192863] usb 1-5: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=60.52
[    1.192866] usb 1-5: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    1.192867] usb 1-5: Product: USB2.0 Hub
[    1.204129] usb 3-4: config 1 has an invalid interface number: 2 but max is 1
[    1.204131] usb 3-4: config 1 has no interface number 1
[    1.216130] usb 3-4: New USB device found, idVendor=0b05, idProduct=18f3, bcdDevice= 1.00
[    1.216133] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.216134] usb 3-4: Product: AURA LED Controller
[    1.216135] usb 3-4: Manufacturer: AsusTek Computer Inc.
[    1.216135] usb 3-4: SerialNumber: 9876543210
[    1.234211] hid-generic 0003:0B05:18F3.0001: hiddev96,hidraw0: USB HID v1.11 Device [AsusTek Computer Inc. AURA LED Controller]
 on usb-0000:06:00.3-4/input2
[    1.347628] usb 3-5: new low-speed USB device number 3 using xhci_hcd
[    1.421634] usb 1-6: new high-speed USB device number 3 using xhci_hcd
[    1.488194] usb 3-5: New USB device found, idVendor=0461, idProduct=4d51, bcdDevice= 7.17
[    1.488196] usb 3-5: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[    1.488197] usb 3-5: Product: DELL Laser Mouse
[    1.512261] input: DELL Laser Mouse as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:06:00.3/usb3/3-5/3-5:1.0
/0003:0461:4D51.0002/input/input2
[    1.512309] hid-generic 0003:0461:4D51.0002: input,hidraw1: USB HID v1.11 Mouse [DELL Laser Mouse] on usb-0000:06:00.3-5/input0

[    1.622863] usb 3-6: new low-speed USB device number 4 using xhci_hcd
[    1.767212] usb 3-6: New USB device found, idVendor=413c, idProduct=2113, bcdDevice= 1.08
[    1.767214] usb 3-6: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[    1.767215] usb 3-6: Product: Dell KB216 Wired Keyboard
[    1.856319] input: Dell KB216 Wired Keyboard as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:06:00.3/usb3/3-
6/3-6:1.0/0003:413C:2113.0003/input/input3
[    1.907932] hid-generic 0003:413C:2113.0003: input,hidraw2: USB HID v1.11 Keyboard [Dell KB216 Wired Keyboard] on usb-0000:06:0
0.3-6/input0
[    1.915339] input: Dell KB216 Wired Keyboard System Control as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:
06:00.3/usb3/3-6/3-6:1.1/0003:413C:2113.0004/input/input4
[    1.966931] input: Dell KB216 Wired Keyboard Consumer Control as /devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/000
0:06:00.3/usb3/3-6/3-6:1.1/0003:413C:2113.0004/input/input5
[    1.966967] hid-generic 0003:413C:2113.0004: input,hidraw3: USB HID v1.11 Device [Dell KB216 Wired Keyboard] on usb-0000:06:00.
3-6/input1
[    6.813453] usb 1-6: device descriptor read/64, error -110
[   22.685285] usb 1-6: device descriptor read/64, error -110
[   22.900981] usb 1-6: new high-speed USB device number 4 using xhci_hcd
[   28.317016] usb 1-6: device descriptor read/64, error -110
[   44.189276] usb 1-6: device descriptor read/64, error -110
[   44.291191] usb usb1-port6: attempt power cycle
[   44.671154] usb 1-6: new high-speed USB device number 5 using xhci_hcd
[   55.547150] usb 1-6: device not accepting address 5, error -62
[   55.660978] usb 1-6: new high-speed USB device number 6 using xhci_hcd
[   66.811143] usb 1-6: device not accepting address 6, error -62
[   66.811281] usb usb1-port6: unable to enumerate USB device
[  141.749861] usb 1-6: new high-speed USB device number 7 using xhci_hcd
[  147.101265] usb 1-6: device descriptor read/64, error -110
[  162.973307] usb 1-6: device descriptor read/64, error -110
[  163.189216] usb 1-6: new high-speed USB device number 8 using xhci_hcd
[  168.605280] usb 1-6: device descriptor read/64, error -110
[  176.818287] usb 3-6: USB disconnect, device number 4
[  177.423427] usb 3-5: USB disconnect, device number 3
[  184.477369] usb 1-6: device descriptor read/64, error -110
[  184.579048] usb usb1-port6: attempt power cycle
[  184.959216] usb 1-6: new high-speed USB device number 9 using xhci_hcd
[  195.835148] usb 1-6: device not accepting address 9, error -62
[  195.949189] usb 1-6: new high-speed USB device number 10 using xhci_hcd
[  207.099179] usb 1-6: device not accepting address 10, error -62
[  207.099233] usb usb1-port6: unable to enumerate USB device
[  207.223193] usb 1-6: new high-speed USB device number 11 using xhci_hcd
[  212.637266] usb 1-6: device descriptor read/64, error -110
[  228.509404] usb 1-6: device descriptor read/64, error -110
[  228.725174] usb 1-6: new high-speed USB device number 12 using xhci_hcd
[  234.141237] usb 1-6: device descriptor read/64, error -110
[  250.013299] usb 1-6: device descriptor read/64, error -110
[  250.115092] usb usb1-port6: attempt power cycle
[  250.495207] usb 1-6: new high-speed USB device number 13 using xhci_hcd
[  261.371271] usb 1-6: device not accepting address 13, error -62
[  261.485167] usb 1-6: new high-speed USB device number 14 using xhci_hcd
[  272.634859] usb 1-6: device not accepting address 14, error -62
[  272.634895] usb usb1-port6: unable to enumerate USB device
[  296.220851] usb 1-6: new high-speed USB device number 15 using xhci_hcd
[  301.724903] usb 1-6: device descriptor read/64, error -110
[  317.597338] usb 1-6: device descriptor read/64, error -110
[  317.813200] usb 1-6: new high-speed USB device number 16 using xhci_hcd
[  323.229274] usb 1-6: device descriptor read/64, error -110
[  339.101232] usb 1-6: device descriptor read/64, error -110
[  339.202955] usb usb1-port6: attempt power cycle
[  339.583166] usb 1-6: new high-speed USB device number 17 using xhci_hcd
[  350.459242] usb 1-6: device not accepting address 17, error -62
[  350.573201] usb 1-6: new high-speed USB device number 18 using xhci_hcd
[  361.723171] usb 1-6: device not accepting address 18, error -62
[  361.723225] usb usb1-port6: unable to enumerate USB device
[  361.847200] usb 1-6: new high-speed USB device number 19 using xhci_hcd
[  367.260893] usb 1-6: device descriptor read/64, error -110
[  383.133262] usb 1-6: device descriptor read/64, error -110
[  383.349277] usb 1-6: new high-speed USB device number 20 using xhci_hcd
[  388.765298] usb 1-6: device descriptor read/64, error -110
[  404.637869] usb 1-6: device descriptor read/64, error -110
[  404.746887] usb usb1-port6: attempt power cycle
[  405.135850] usb 1-6: new high-speed USB device number 21 using xhci_hcd
[  415.994846] usb 1-6: device not accepting address 21, error -62
[  416.108848] usb 1-6: new high-speed USB device number 22 using xhci_hcd
[  427.259842] usb 1-6: device not accepting address 22, error -62
[  427.259885] usb usb1-port6: unable to enumerate USB device

And here is the output of lsusb -v:
lsusb.txt (20.4 KB)

I’m not really sure how to interpret the outputs because I don’t know what “usb 1-6” corresponds to in the lsusb output.

Your help is greatly appreciated.

(Oddly enough, I just upgraded the kernel to 5.14.15 again and it DOESN’T appear to be causing an issue with my Mellanox ConnectX-4 Infiniband NIC anymore. Or at least for now/for the moment.)

Go figures!!!

5

You may have found a kernel regression. IT may be worth while to issue a bug report to your kernel maintainer.

This usually corresponds to Bus 1, port 6

Also it looks like you are running a RHEL kernel. It could be possible that the drivers/kernel modules may not be compiled in the kernel or the firmware is missing.

6

Thank you.

I appreciate your insights.

I don’t really know much about this stuff because previously, I was using a 4-node Xeon blade server, so I didn’t run into issues like this on that platform.

Thank you.

Interestingly enough, when I look at my lsusb.txt file, it doesn’t show nor have a bus 1, device 6 USB device.

So…I’m not really sure what to make of that.

Not sure.

It’s entirely possible.

(I’m running CentOS 7.7.1908 with an updated kernel from the elrepo repository, so it’s probably a RHEL derivative.)

I am, maybe, perhaps a little bit surprised because I would’ve thought that with the X570 platform being almost 2 years old by now, that this kind of stuff would’ve been ironed out by now.

Granted, even if the USB 3.0 ports didn’t work (I’m using a much older Antect full tower case, so it only has USB 2.0 ports in the front where if I need console access, I would plug a keyboard and a mouse into), if I need something, as long as my GbE NIC is up and working, then I can usually pull whatever it is I need, off the network.

The only time that I really need the USB 3.0 ports is when I am installing the OS, and even then, I have to jumpstart the system using another system so that I can install the base OS, and then update the kernel before moving the hard drive over to either of my 5950X systems.

Thank you.

7

People make fun of Debian because the stable branch has old software, but CentOS chuckles at Debian Stable and says, “Hold my Beer”.
This is probably the issue. The newer stuff may not have been truly upgraded to work with everything. hence why the older kernel probably works.

If the device cannot be enumerated, which it states that it can’t, then that means that it may not show up in lsusb.
With that said, if you can identify other devices on bus 1, you may be able to figure out which port it actually is and see if it is occupied by something or if it is an internal motherboard port.

8

The 5.4.196 and the 5.14.15 kernels both come from the same elrepo repository.

I’m not really sure.

I just figured that it was easier for me to just download it as a YUM/RPM package and install it with that, than to compile and install it myself (because if something goes wrong, then I am going to be spending more time trying to "de-"compile it) and I just really need my system to be deployed as a production system rather than trying to sort out basic, sysadmin/operational issues with it.

That’s going to take some time, and if I am going to be perfectly blunt and honest – as long as my Infiniband is back up and running now and it can survive reboots, I am not overly concerned about the operation (or lack thereof (yet)) of the USB error message.

I was just hoping that on the off chance, it’s either a known issue (when I googled it, a lot of the question that people were asking about and their respective responses were about or in relation to a device being plugged in). But that isn’t what’s happening in my case because even without the Dell USB mouse and keyboard plugged in, I get that error regardless.

It extends the boot time by about a minute or so whilst the system is trying to probe/sort that out on boot up/start up, but once it’s in the OS, it doesn’t really seem to bother it that much, if at all.

The more annoying thing when I first started to experience it was that it was taking down my IB ports with it. But now it’s working.

shrug who knows!

(The only difference was that I rolled back to the 5.4.196 kernel, rebooted the system, and then installed the 5.14.15 (from the same, source RPM file), and rebooted it again, and now it works.)

Linux can be super frustrating like this sometimes where I don’t really know WHY it works now, but I’m also not really going to be complaining that it is at least, working now.

9

This sounds like the INITRD/INITRAMFS did not build properly during the system upgrade process and that when you installed through RPM, it did.

I am biased and if I go rpm based systems, I choose SuSe due to zypper and what not. Otherwise, I am an Debian and ArchLinux type of person.

If you are not using DNF for your upgrades, then I recommend doing that. I don’t know what CentOS’s default is. DNF is a lot more intelligent of a package manager than using rpm or what ever the default RHEL system is.

Overall, if it is working now, I do a system inventory (export the list of installed packages) and copy your critical config files.

10

Both installs were done via yum/rpm.

To me, I haven’t really found much of an observable difference between RHEL’s YUM vs. SuSE’s zypper.

I used to use SuSE, but that was before that I found that their mgag200 had a memory leak in it on my blade micro cluster, so ever since then, that’s when I switched over to CentOS and CentOS has been working well for me since then (at least until I started to deploy a new generation of hardware (e.g. 5950X).)

I’m not really sure that I understand what are the real differences between yum vs. dnf.

Yeah…well…I was hoping that when Asus sent me the replacement motherboard that it would have been the same model as my other system, so that I can effectively, just clone the hard drive.

But being that this was a different motherboard model, I ended up deciding to install the OS from scratch just to make sure that there wouldn’t be any such oddities like this.

And it’s a good thing that I did install it from scratch because otherwise, these issues may have potentially been masked and/or cloning the hard drive from my other system may not have booted and I would’ve needed to re-install CentOS from scratch anyways.

Thanks.

1 Like