You are not logged in.
Pages: 1
On boot, I am confronted with errors such as:
usb 1-5: device descriptor read/64, error -71
usb 1-5: Device not responding to setup address
and finally
usb usb1-port5: unable to enumerate USB device.
A full log from dmesg can be found here.
All usb peripherals (mouse, keyboard, wifi dongle) work without issue. Further, the error appears on boot even when nothing is plugged into the USB drives.
I assume this error is harmless, since everything is working properly. Nonetheless, is there any way to fix it?
If not, could I at least suppress it, since it clutters the login screen where I enter my password for the luks-encrypted drive? I tried booting with the kernel parameters "quiet loglevel=3 rd.systemd.show_status=false" as suggested in the wiki, but this did not change the appearance of the error messages. Neither did loglevel=0. Perhaps I am doing something wrong here?
(My parameters previously were "loglevel=3 quiet." The error comes before the root drive is decrypted, so I think it is systemd giving the error messages.)
Thank you for your time, and please let me know if I should provide any more information. I am on a fully updated installation.
Last edited by rowhammer (2020-03-19 07:27:18)
Offline
So, what's on that port?
lsusb -tv
Offline
That command gives the following, which I am not sure how to interpret.
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
ID 1532:001c Razer USA, Ltd RZ01-0036 Optical Gaming Mouse [Abyssus]
|__ Port 2: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M
ID 04d9:a0f8 Holtek Semiconductor, Inc.
|__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
ID 04d9:a0f8 Holtek Semiconductor, Inc.
|__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 12M
ID 04d9:a0f8 Holtek Semiconductor, Inc.
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 2: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8188eu, 480M
ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter
Additionally, lsusb gives:
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 04d9:a0f8 Holtek Semiconductor, Inc. USB Gaming Keyboard
Bus 005 Device 002: ID 1532:001c Razer USA, Ltd RZ01-0036 Optical Gaming Mouse [Abyssus]
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Offline
[ 2.483764] usb 1-5: new full-speed USB device number 4 using xhci_hcd
[ 2.613769] usb 1-5: device descriptor read/64, error -71
…
[ 2.850479] usb 1-5: device descriptor read/64, error -71
[ 2.957140] usb usb1-port5: attempt power cycle
There seems to be something on that port, but apparently it cannot be powered up (error -71 is power related)
Since the other device on the bus is the wifi chip, maybe bluetooth? Or a microphone? (This is an internal bus, USB is not! a jack)
Is the device supposed to have bluetooth (it's not the complete dmesg…)?
If so: rfkill?
Is there maybe some HW switch?
Offline
I'm using an Asrock 570M motherboard. The manual is here (.pdf download). I do not see an internal microphone or bluetooth chip.
However, on page 5, USB_5 is listed as "AMD LED Fan USB Header." I have this attached to my CPU fan, and can control the LEDs for it in the BIOS, but maybe the kernel is complaining because it isn't capable of communicating with it?
If you believe this is the case, I have no desire to control the LEDs from Arch. Is there a way to quiet this error on boot so it does not pollute my login screen (for the encrypted drive)?
The dmesg I posted is complete. Thanks so much for your time.
Last edited by rowhammer (2020-03-18 21:15:16)
Offline
You could try to disconnect the fan LED (afaics the fan itself is entirely powered and controlled by the normal 4-pin connector) and see whether the message disappears to be sure that this is the cause.
If you're conviced this is the device and you just want to shut it down, you probably need to pass "uhci-hcd.ignore_oc=1"
Notice:
uhci-hcd.ignore_oc=
[USB] Ignore overcurrent events (default N).
Some badly-designed motherboards generate lots of
bogus events, for ports that aren't wired to
anything. Set this parameter to avoid log spamming.
Note that genuine overcurrent events won't be
reported either.
You can also try http://www.irongeek.com/i.php?page=secu … using_UDEV but I assume
cat /sys/bus/usb/devices/1-5/authorized
will tell you that no such file or device exists?
Offline
Yes, I get the error "No such file or directory" when running that command.
You're definitely right that it's an internal port. I tested the external USB ports next to where the wifi dongle is plugged in, and those work fine.
If we examine the manual, we see the following. The external front USB ports (where the wifi dongle is) plug into item 10. The fan LEDs plug into item 9. The physical proximity makes me think they're on the same bus. This gives some evidence for the theory it's the fan lights.
I am not really inclined to open my case and start unplugging things to confirm, since I am in a high-static environment right now, and it was enough of a headache to get everything together in the first place. I'm going to go with this guess and just mute the errors. Does this sound reasonable?
https://i.imgur.com/ZozdvEv.png
moderator edit -- replaced oversized image with link.
Pasting pictures and code
Last edited by 2ManyDogs (2020-03-18 22:45:36)
Offline
Note that genuine overcurrent events won't be reported either.
Does the connector physically prevent you from eg. flipping the connection (ie. does it ensure that Pin1 is connected to Lane1)?
I'd always rule a HW misconfig out first, but that oc. requires the opportunity to do so.
To silence the boot (but keep the error logged, if that's your major concern)
https://wiki.archlinux.org/index.php/Silent_boot#sysctl
You'll likely have to pass this to the kernel command line (in grub) and lower the loglevel to 2 ("loglevel=2" might works just as well), because "3" is "error", "2" is "critical"
Offline
Thank you, seth. I silenced the errors and am happy now. I will mark the thread as solved.
Cross-referencing the motherboard manual and the lsusb output, the fan is the only possibility. You must be right about me having it plugged in wrong. I will fix it next time I open the case, but I'm happy to let things sit for now.
Last edited by rowhammer (2020-03-19 07:36:12)
Offline
Seth, you were 100% right. I flipped the LED header and Arch sees it now. Thank you!
Offline
Pages: 1