Nut upsuser - Jul 2005 - NUT 2.x causes uhci-usb error messages in syslog.

Hello,



  For a while I have been running NUT 2.0.0 just fine with my APC Back-UPS RS
800 using the usbhid interface.



  I decided to upgrade to 2.0.2, and all went well (upsc and upsd/upsmon seem
happy to talk to the UPS), but I am getting a ton of these messages in my
syslog:



Jul  6 17:12:45 yggdrasil kernel: usb-uhci.c: interrupt, status 3, frame# 780

Jul  6 17:12:50 yggdrasil kernel: usb-uhci.c: interrupt, status 3, frame# 1687

Jul  6 17:12:55 yggdrasil kernel: usb-uhci.c: interrupt, status 3, frame# 556

Jul  6 17:13:01 yggdrasil kernel: usb-uhci.c: interrupt, status 3, frame# 646



(frame #s are random)



I decided to try and downgrade to 2.0.1, but it had the same problem.



I used the original 2.0.0 source and it's not giving me those error messages
anymore.



Kernel is 2.4.27

modules loaded: hid, usb-uhci, usbcore

UPS: APC Back-UPS RS 800



(If my email seems odd, it's because I'm using sneakemail to prevent
spammers from mailing me as it seems everyone's email addresses are publicly
viewable in the archives.)



Any help would be appreciated! Thanks very much!



Tom

Hi Arnaud,



  I attempted to switch to the newhidups driver. I changed the driver to
'newhidups' and the port to 'auto' in the ups.conf file.



  I also removed the HIDDEV support in the kernel. The UPS driver won't load
at all, and won't give me any kind of useful messages (even if I invoke
newhidups manually with the -D parameter.)



  Is there anything else I should try? I thought the newhidups driver only
handled a certain kind of UPS?



 Thanks,

   Tom

Hi Arnaud,

I did as you suggested, but got the following back:

Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2)

debug level is '5'
Opening new device (0000/0000)
Opening new device (043D/007A)
Opening new device (413C/5105)
Opening new device (413C/5106)
Opening new device (051D/0002)
Found 0x51d
failed to claim USB device, trying 2 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
failed to claim USB device, trying 1 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
failed to claim USB device, trying 0 more time(s)...
detaching kernel driver from USB device...
failed to detach kernel driver from USB device...
trying again to claim USB device...
- Unable to fetch manufacturer string
- Unable to fetch product string
- Unable to fetch serial number string
Unable to get HID descriptor (error sending control message: Operation not 
permitted)
found 0 (-1)
No USB/HID UPS found

Thanks,
Tom

On 7/20/05, arnaud.quette-at-mgeups.com
<http://arnaud.quette-at-mgeups.com>|NUT Mailing list|<
...> wrote:
> 
> 
> 
> Hi
> 
> > Hello again, Arnaud -
> 
> I reply directly to this one.
> 
> BTW, please subscribe to nut mailing lists and post publically.
> There are other people in your situation...
> 
> > Just a little addendum.. I edited ups.conf to set port = auto, and I 
> removed hiddev support
> > in the kernel. (All that is left is the following: CONFIG_USB_HID=m, 
> CONFIG_USB_HIDINPUT=y
> > CONFIG_USB_HIDDEV=n)
> >
> > Both with and without the 'hid' module loaded, the driver does
not load,
> and it doesn't give any kind of useful
> > debugging output (even if I add -D to the newhidups command-line)
> 
> hid will have no effect on newhidups as we now unbind it
> from the device at runtime.
> 
> I more suspect an hotplug issue. Depending on the way you've installed
> nut, you might miss the libhid.usermap and libhidups files (from nut 
> source,
> scripts/hotplug directory) to be put in /etc/hotplug/usb.
> 
> you can validate this by doing "export USB_DEBUG=3"
> and then launch newhidups in debug mode (-DDDDD)
> 
> Arnaud
> ---
> Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
> OpenSource Developer - http://arnaud.quette.free.fr/
> Debian Developer - http://people.debian.org/~aquette/
> ... and much more ...
> 
> 
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20050720/530fd0c6/attachment.htm

Hi Tom,
> For a while I have been running NUT 2.0.0 just fine with my APC Back-UPS RS
800 using the usbhid interface.
>
> I decided to upgrade to 2.0.2, and all went well (upsc and upsd/upsmon seem
happy to talk to the UPS),
> but I am getting a ton of these messages in my syslog:
>
> Jul  6 17:12:45 yggdrasil kernel: usb-uhci.c: interrupt, status 3, frame#
780
> ...
> (frame #s are random)
this should be due to the call of "HIDIOCINITREPORT" before getting
each report (== data).
This was needed for some APC models, but seems to cause problems
to others... Does your driver continue to update data?

Anyway, your best bet is to try newhidups, as this one will soon replace
the old linux only hidups.

But there are point missing (not sure, as it seems the shutoff (== ups
poweroff) is not supported for APC in hidups), that are under investigation
by APC users... If you want to join, you're welcome.

Arnaud

> I did as you suggested, but got the following back:
>
> Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2)
> ...
> Opening new device (051D/0002)
> Found 0x51d
> failed to claim USB device, trying 2 more time(s)...
> detaching kernel driver from USB device...
> failed to detach kernel driver from USB device...
> ...
this is a hotplug problem

- Copy the files libhidups and libhid.usermap (from nut/scripts/hotplug)
to /etc/hotplug/usb. libhidups might be adapted to the nut user of your
system (ie "nut" on RH)
- Change the perms on /etc/hotplug/usb/libhidups to 755 (ie using chmod +x ...)
- unplug / replug your USB cord
- relaunch newhidups in debug mode

it should now work...

Arnaud

[forwarded for info]
> Tom Murphy wrote:
> I fixed it! I forgot to chmod 755 the libupshid file, now it loads
everything.
> Thanks so much!
>
> Tom
> ...