Hello, I have a Salicru UPS in a Debian Wheezy connected with a USB HUB: # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ... Bus 001 Device 003: ID 1a40:0201 Terminus Technology Inc. FE 2.1 7-port Hub Bus 001 Device 005: ID 0665:5161 Cypress Semiconductor USB to Serial The problem is that I have some failed messages: # dmesg ... [90941.136274] usb 1-3.7: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [91382.412323] usb 1-3.7: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [92037.704329] usb 1-3.7: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [92250.832357] usb 1-3.7: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [92931.800283] usb 1-3.7: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 I can see the status: # upsc salicru battery.charge: 100 battery.voltage: 13.40 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.type: ups driver.name: blazer_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.6.4 driver.version.internal: 0.08 input.current.nominal: 2.0 input.frequency: 50.1 input.frequency.nominal: 50 input.voltage: 225.4 input.voltage.fault: 225.4 input.voltage.nominal: 230 output.voltage: 225.4 ups.beeper.status: enabled ups.delay.shutdown: 30 ups.delay.start: 180 ups.load: 8 ups.productid: 5161 ups.status: OL ups.type: offline / line interactive ups.vendorid: 0665 Are the messages a problem? Or could I ignore? Thanks for your help. Regards. -- Josu Lazkano
On Mar 7, 2014, at 4:12 PM, Josu Lazkano <josu.lazkano at gmail.com> wrote:> Are the messages a problem? Or could I ignore?Since they aren't happening on each poll interval, they are not a big problem. The driver should recognize -110 as a timeout, and retry the query.
2014-03-08 14:26 GMT+01:00 Charles Lepple <clepple at gmail.com>:> On Mar 7, 2014, at 4:12 PM, Josu Lazkano <josu.lazkano at gmail.com> wrote: > >> Are the messages a problem? Or could I ignore? > > Since they aren't happening on each poll interval, they are not a big problem. The driver should recognize -110 as a timeout, and retry the query.Thanks for the answer Charles, This is the times that it fails: # tail -f /var/log/syslog | grep blazer Mar 8 14:33:48 server kernel: [152463.672358] usb 1-3.7: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 Mar 8 14:36:55 server kernel: [152650.816372] usb 1-3.7: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 Mar 8 14:45:03 server kernel: [153138.876267] usb 1-3.7: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 Mar 8 14:52:27 server kernel: [153582.796345] usb 1-3.7: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 Which is the frequency of the poll? Regards. -- Josu Lazkano