[Nut-upsuser] Eaton Nova AVR repeated USBDEVFS_CONTROL failed cmd usbhid-ups

Charles Lepple clepple at gmail.com
Fri Apr 4 02:51:47 UTC 2014


On Apr 3, 2014, at 3:40 PM, Adam Pribyl wrote:

> I have nut 2.6.4-2.3+deb7u1 on debian 7 32bit, with UPS Eaton Nova AVR 1250 connected via USB.

Which kernel version?

> It happens several times a day that I get a message about
> 
> Apr  3 16:41:49 kernel: [422581.049671] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110
> Apr  3 16:41:54 kernel: [422586.041057] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 3 ret -110

Error -110 is indeed a timeout, but it is not directly coupled to pollinterval.

NUT 2.7.1 increases most of the USB timeouts from 4000 to 5000 ms, but if this error is after the driver initialization has completed, then the increased timeout is not as likely to help.

> Apr  3 16:41:54 kernel: [422586.331313] hub 5-0:1.0: port 1 disabled by hub (EMI?), re-enabling...
> Apr  3 16:41:54 kernel: [422586.331377] usb 5-1: USB disconnect, device number 3
> Apr  3 16:41:54 kernel: [422586.515007] hub 5-0:1.0: unable to enumerate USB device on port 1

This problem is between your USB hardware and your kernel. (The previous error may be related.)

Without knowing your USB host controller, I'd say it might be a USB cable or port issue. Try another USB cable (preferably shorter), and also try a different port. If that doesn't fix it, you probably want to check with the linux-usb list to see if there is a known issue with your kernel version.

There really isn't much that NUT can do there, besides recover gracefully. The reconnection logic should be in usbhid-ups.

-- 
Charles Lepple
clepple at gmail



More information about the Nut-upsuser mailing list