Jump to content
We're Hiring! Full Stack Developer ×

Can not connect UPS, USB error -71.


Naminator

Recommended Posts

Good day everyone.

I have been having some odd problems with USB, I passed through some USB busses directly to a couple of VMs and naturally I left alone the device that handles
the boot USB.
The UNRAID USB is connected to a PCI usb card I used to passthrough devices individually without problem like Keyboards, Mice, the UPS, but suddenly it 
stopped doing that.
Currently it cannot communicate to any of them, but I can connect a flash memory and it will work, I can connect my cellphone and it will charge it and 
also a serial converter will work.
The device has an internal connector for power, it is connected and working.
Any ideas?

Edit:I also noticed my post looks strange, it is my first post in this forum, sorry XD

The part of the Syslog where I get the errors:

Jun  8 01:18:18 Tower kernel: usb 2-1: new low-speed USB device number 2 using xhci_hcd
Jun  8 01:18:18 Tower kernel: usb 1-1: new high-speed USB device number 2 using ehci-pci
Jun  8 01:18:18 Tower kernel: usb 2-1: device descriptor read/64, error -71
Jun  8 01:18:18 Tower kernel: hub 1-1:1.0: USB hub found
Jun  8 01:18:18 Tower kernel: hub 1-1:1.0: 6 ports detected
Jun  8 01:18:18 Tower kernel: xhci_hcd 0000:04:00.0: WARN urb submitted to disabled ep
Jun  8 01:18:18 Tower kernel: xhci_hcd 0000:04:00.0: WARN urb submitted to disabled ep
Jun  8 01:18:18 Tower kernel: xhci_hcd 0000:04:00.0: WARN urb submitted to disabled ep
Jun  8 01:18:18 Tower kernel: usb 2-1: device descriptor read/64, error -2
Jun  8 01:18:18 Tower kernel: usb 2-1: new low-speed USB device number 3 using xhci_hcd
Jun  8 01:18:18 Tower kernel: tsc: Refined TSC clocksource calibration: 3298.088 MHz
Jun  8 01:18:18 Tower kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2f8a3e6e441, max_idle_ns: 440795328433 ns
Jun  8 01:18:18 Tower kernel: usb 2-1: device descriptor read/64, error -71
Jun  8 01:18:18 Tower kernel: xhci_hcd 0000:04:00.0: WARN urb submitted to disabled ep
Jun  8 01:18:18 Tower kernel: xhci_hcd 0000:04:00.0: WARN urb submitted to disabled ep
Jun  8 01:18:18 Tower kernel: xhci_hcd 0000:04:00.0: WARN urb submitted to disabled ep
Jun  8 01:18:18 Tower kernel: usb 2-1: device descriptor read/64, error -2
Jun  8 01:18:18 Tower kernel: usb 2-1: new low-speed USB device number 4 using xhci_hcd
Jun  8 01:18:18 Tower kernel: usb 2-1: Device not responding to setup address.
Jun  8 01:18:18 Tower kernel: usb 2-1: Device not responding to setup address.
Jun  8 01:18:18 Tower kernel: usb 2-1: device not accepting address 4, error -71
Jun  8 01:18:18 Tower kernel: usb 2-1: new low-speed USB device number 5 using xhci_hcd
Jun  8 01:18:18 Tower kernel: usb 2-1: Device not responding to setup address.
Jun  8 01:18:18 Tower kernel: clocksource: Switched to clocksource tsc
Jun  8 01:18:18 Tower kernel: usb 2-1: Device not responding to setup address.
Jun  8 01:18:18 Tower kernel: usb 2-1: device not accepting address 5, error -71
Jun  8 01:18:18 Tower kernel: usb usb2-port1: unable to enumerate USB device
Jun  8 01:18:18 Tower kernel: usb 2-2: new high-speed USB device number 6 using xhci_hcd
Jun  8 01:18:18 Tower kernel: usb-storage 2-2:1.0: USB Mass Storage device detected
Jun  8 01:18:18 Tower kernel: scsi host0: usb-storage 2-2:1.0
Link to comment
  • 7 months later...

I have yet to verify exactly what caused it but I had this same error recently and here's what fixed it: switching the device to a new USB port (preferably on a different USB controller).

 

In my case I had a keyboard and mouse which would light up but not work on the GUI login screen (in addition to the UPS). I suspect either the ports on the motherboard are dying/fried since before switching ports my UPS would also randomly disconnect or, the controller being used isn't initialized early enough (UNRAID or BIOS issue?) for it to get picked up correctly and attach the device.

Link to comment

I have yet to verify exactly what caused it but I had this same error recently and here's what fixed it: switching the device to a new USB port (preferably on a different USB controller).

 

In my case I had a keyboard and mouse which would light up but not work on the GUI login screen (in addition to the UPS). I suspect either the ports on the motherboard are dying/fried since before switching ports my UPS would also randomly disconnect or, the controller being used isn't initialized early enough (UNRAID or BIOS issue?) for it to get picked up correctly and attach the device.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...