[Nut-upsdev] usbhid-ups: no reconnect on error EPIPE
Arjen de Korte
nut+devel at de-korte.org
Mon Jan 4 21:00:34 UTC 2010
In response to my previous message, an excerpt from the syslog showing
what happens:
Jan 4 21:40:11 mail usbhid-ups[5145]: libusb_get_report: error
sending control message: Broken pipe
Jan 4 21:40:15 mail kernel: usb 1-2.1: usbfs: USBDEVFS_CONTROL failed
cmd usbhid-ups rqt 128 rq 6 len 255 ret -110
Jan 4 21:40:16 mail kernel: usb 1-2.1: usbfs: USBDEVFS_CONTROL failed
cmd usbhid-ups rqt 128 rq 6 len 255 ret -110
Jan 4 21:40:16 mail upsd[5149]: Data for UPS [ellipse] is stale -
check driver
Jan 4 21:40:19 mail upsd[5149]: UPS [ellipse] data is no longer stale
The above happens fairly frequently, up to several times per hour. It
looks like the UPS is somehow too busy to handle the USB communication
and even fails to respond to the first two requests for the report
descriptor. After that, it is business as usual again.
Best regards, Arjen
--
Please keep list traffic on the list
More information about the Nut-upsdev
mailing list