[Nut-upsuser] USBDEVFS_CONTROL failed cmd usbhid-ups

[Thomas Gutzler]

Arjen de Korte wrote:
> Citeren Thomas Gutzler <thomas.gutzler at gmail.com>:
> 
>> In summary:
>> - no EMI (port re-connect) for the 'old' ups
>> - 68 and 76 USBDEVFS_CONTROL errors for the 'old' ups over the first and
>> second period
>> - 323 and 314 USBDEVFS_CONTROL errors for the 'new' ups over the first
>> and second period
> 
> The 'old' UPS might not be using interrupt reports and therefor, we
> don't see collisions. Could you run it in debug mode (one minute will be
> enough) to check if this is indeed the case?

The logfile is attached; one with each version.

>> Is there anything else I can do for you?
> 
> You could try adding the 'pollonly' flag, but I'm afraid this isn't
> going to help. I don't think we (the NUT developers) can do anything
> about it.

Not sure there, but I have added pollonly = 1 to ups.conf and restarted
the driver. See what it does next week.

Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: usbhid-ups_2.4.1-DDD_old.log.gz
Type: application/x-gzip
Size: 3285 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20091204/591785c8/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: usbhid-ups_2.4.1-2142-DDD_old.log.gz
Type: application/x-gzip
Size: 7361 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20091204/591785c8/attachment-0003.bin>