Hi all, after a change of UPS (to Atlantis Host Power 851) I began to use the new driver blazer_usb and compared to old one (blazer used with serial connection) I noted more CPU use and errors in dmesg: [...] [256712.584370] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [256789.640795] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [257771.412836] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [258932.684998] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [258981.720738] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [259180.876451] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [259211.897105] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [259232.909134] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [394342.020322] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [...] This is the configuration of the driver in ups.conf: [ups] driver = blazer_usb subdriver = cypress vendorid = 0665 productid = 5161 port = auto desc = "AtlantisLand Host Power 851+" Obviously the usb ports work good, I think is a bug in the driver or something like.. Bye at all Fabio C.
On Nov 25, 2013, at 4:56 PM, Fabio Cecamore wrote:> Hi all, > after a change of UPS (to Atlantis Host Power 851) I began to use the new driver blazer_usb and compared to old one (blazer used with serial connection) I noted more CPU use and errors in dmesg: > > [...] > [256712.584370] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110"ret -110" is a timeout, I believe.> Obviously the usb ports work good, I think is a bug in the driver or something like..Could be a cable problem, too. What version of NUT? We increased the timeout in 2.7.1. Also, devices that talk to blazer_usb are basically serial UPSes with a USB-to-serial converter. The increased CPU usage is not surprising, since the host now has to poll the USB-to-serial converter (rather than the UART interrupting the CPU when data is ready). Do you have any profiling data to show how much more CPU time is being used? -- Charles Lepple clepple at gmail
Hi Charles>> Obviously the usb ports work good, I think is a bug in the driver or something like.. > Could be a cable problem, too.I'll try to change the USB cable but is hard to be fault, it's new..> What version of NUT? We increased the timeout in 2.7.1.Network UPS Tools - Megatec/Q1 protocol USB driver 0.09 (2.6.5)> > Also, devices that talk to blazer_usb are basically serial UPSes with a USB-to-serial converter. The increased CPU usage is not surprising, since the host now has to poll the USB-to-serial converter (rather than the UART interrupting the CPU when data is ready). Do you have any profiling data to show how much more CPU time is being used?I don't have any profiling data, I just noticed that blazer_usb is ever first in 'top' list, with older blazer driver it was at the end of the 'top' list, now it uses always 0,3% to 1,7% of CPU with poolinterval at 2 seconds. My CPU is not so powerful but anyway it is a good diference and so I noted it.. Bye -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20131126/7460de4b/attachment.html>
Fabio Cecamore
2013-Dec-06 19:05 UTC
[Nut-upsuser] AtlantisLand don't want to wake up after the whiteout
Hi all, I've problem with the management of my AtlantisLand UPS, the UPS don't want to wake up after the whiteout and I don't have any idea why.. This is the ups.conf: [ups] driver = blazer_usb subdriver = cypress vendorid = 0665 productid = 5161 port = auto desc = "AtlantisLand Host Power 851+" pollinterval = 10 offdelay = 60 this is the upsc result: battery.charge: 100 battery.voltage: 13.50 battery.voltage.high: 13.00 battery.voltage.low: 10.40 battery.voltage.nominal: 12.0 device.type: ups driver.name: blazer_usb driver.parameter.offdelay: 60 driver.parameter.pollinterval: 10 driver.parameter.port: auto driver.parameter.productid: 5161 driver.parameter.subdriver: cypress driver.parameter.vendorid: 0665 driver.version: 2.6.5 driver.version.internal: 0.09 input.current.nominal: 3.0 input.frequency: 50.0 input.frequency.nominal: 50 input.voltage: 232.8 input.voltage.fault: 232.8 input.voltage.nominal: 220 output.voltage: 232.8 ups.beeper.status: enabled ups.delay.shutdown: 60 ups.delay.start: 180 ups.load: 8 ups.productid: 5161 ups.status: OL ups.type: offline / line interactive ups.vendorid: 0665 I had the same problem with the old UPS (serial), never wake up.. So I think is my bad configuration. Thanks all.. Bye Fabio
hyouko at gmail.com
2013-Dec-09 15:04 UTC
[Nut-upsuser] AtlantisLand don't want to wake up after the whiteout
2013/12/6 Fabio Cecamore <ceca_89 at hotmail.com>:> Hi all,Hi> I've problem with the management of my AtlantisLand UPS, the UPS don't want > to wake up after the whiteout and I don't have any idea why..Some (very old) units are known to have problems with small values for ondelay (hence the default 3 minutes value): https://github.com/networkupstools/nut/blob/master/drivers/blazer.c#L443 Have you tried increasing the standard ondelay?