Re: [Nut-upsuser] libusb_get_interrupt: error reading from interrupt endpoint /dev/ugen0.1

2011-03-24 Thread John Bayly

On 24/03/2011 13:01, Charles Lepple wrote:

How do things work if you add the pollonly option to the
configuration file?

I've just tried this, and the USB debug messages stopped on restart.
Really appreciate the help.



Be sure that the measured values shown in upsc are updating as well.
With the pollonly flag, they should be explicitly requested via
control messages, and you should see error messages if those control
messages fail, but that's making a lot of assumptions about the USB
stack.
Thanks for pointing that out. Just did some timing and found that with 
and without the pollonly flag set, the ups.load value was changing 
when applying and removing additional load. I did however notice that 
the time taken to register the load change could be between 0 and 20 
seconds, thought this could be down to the UPS itself, and not the drivers.

I've seen no errors being reported, so I'll cross my fingers!

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] libusb_get_interrupt: error reading from interrupt endpoint /dev/ugen0.1

2011-03-24 Thread Arjen de Korte

Citeren John Bayly freebsd.po...@tipstrade.net:

Thanks for pointing that out. Just did some timing and found that  
with and without the pollonly flag set, the ups.load value was  
changing when applying and removing additional load. I did however  
notice that the time taken to register the load change could be  
between 0 and 20 seconds, thought this could be down to the UPS  
itself, and not the drivers.

I've seen no errors being reported, so I'll cross my fingers!


Note that only a handful variables (mostly related to critical  
ups.status flags) will be polled every 'pollinterval' (default: 2)  
seconds (for the mge-hid subdriver) and the remainder of the variables  
only once every 'pollfreq' (default: 30) seconds. See 'man 5 ups.conf'  
and 'man 8 usbhid-ups' respectively. So with the 'pollonly' flag set,  
the OL/OB/LB and *.timer variables will be updated every 2 seconds and  
the remainder every 30 seconds.


Best regards, Arjen
--
Please keep list traffic on the list (off-list replies will be rejected)


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


[Nut-upsuser] libusb_get_interrupt: error reading from interrupt endpoint /dev/ugen0.1

2011-03-23 Thread John Bayly
Using an Eaton Evolution S 3000 (usbhid-ups) 2.6.0 on FreeBSD 7.3. After 
checking the debug log for an unrelated reason I saw that it was being 
swamped by the following message:


Mar 23 15:50:57 rack usbhid-ups[65419]: libusb_get_interrupt: error 
reading from interrupt endpoint /dev/ugen0.1: Resource temporarily 
unavailable


The UPS is ugen0 on /dev/usb1

# ll /dev/usb1
crw-rw  1 root  uucp0,  37 Mar 22 18:50 /dev/usb1

# ll /dev/ugen*
crw-rw  1 uucp  wheel0, 113 Mar 22 18:49 /dev/ugen0
crw-rw  1 uucp  wheel0, 130 Mar 22 18:49 /dev/ugen0.1

As far as I can see, everything *appears* to be working properly. Any 
suggestions?


Thanks,
John

___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] libusb_get_interrupt: error reading from interrupt endpoint /dev/ugen0.1

2011-03-23 Thread Charles Lepple

On Mar 23, 2011, at 12:09 PM, John Bayly wrote:

Using an Eaton Evolution S 3000 (usbhid-ups) 2.6.0 on FreeBSD 7.3.  
After checking the debug log for an unrelated reason I saw that it  
was being swamped by the following message:


The USB stack in FreeBSD prior to 8.0 did not lend itself to being  
precisely controlled from userspace by libusb. It sounds like you are  
seeing slightly different problems than I saw while trying to make  
tripplite_usb work under FreeBSD, but the common symptom was the  
interrupt endpoints. (FreeBSD prior to 8.0 seems to poll the endpoints  
more frequently than userspace code reads from them, and I often saw  
partial packets dropped when the buffer filled up.)


How do things work if you add the pollonly option to the  
configuration file?


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser