Arnaud Quette
2006-Feb-27 08:14 UTC
[Nut-upsdev] Re: Bug#354429: nut spams consoles and system logs with USB UPS
tags 354429 + upstream thank 2006/2/26, suicune@eml.cc <suicune@eml.cc>:> Package: nut > Version: 2.0.1-3 > > > This is the spam message: > drivers/usb/input/hid-core.c: ctrl urb status -32 received > > I never once saw this message until after I installed and configured > nut. > > Spam begins during boot and continues infinitely until reboot or nut is > stopped. > > Spam appears on all text mode consoles (not xterms) about once a second, > making > the consoles unusable. The spam also appears in several system logs. > `dmesg` is > unusable because the spam message is the only thing that appears by the > time I > can type the command. > > Running `/etc/rc2.d/S20nut stop` halts the spam and sets all back to > normal. > > 2.6.8-2-686 #1 Tue Aug 16 13:22:48 UTC 2005 i686 GNU/Linux > lrwxrwxrwx 1 root root 13 2005-10-19 12:13 /lib/libc.so.6 -> > libc-2.3.5.so > > Hardware > Compaq Deskpro EP 6400 > Pentium3 Katmai 450MHz > UPS is connected to motherboard USB port (Intel 82371AB/EB/MB PIIX4 USB) > UPS is Belkin F6H550-USB > ...I suspect something like claiming not working as once newhidups is started, Linux hid layer shouldn't be used anymore! A good test would be (if you have no USB/HID keyboard or mouse) to force the removal of the hid module and see if the messages still appears. Peter: any thought on this? Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/
Peter Selinger
2006-Feb-27 09:08 UTC
[Nut-upsdev] Re: Bug#354429: nut spams consoles and system logs with USB UPS
Arnaud Quette wrote:> > tags 354429 + upstream > thank > > 2006/2/26, suicune@eml.cc <suicune@eml.cc>: > > Package: nut > > Version: 2.0.1-3 > > > > > > This is the spam message: > > drivers/usb/input/hid-core.c: ctrl urb status -32 received > > ... > > I suspect something like claiming not working as once newhidups is > started, Linux hid layer shouldn't be used anymore! > A good test would be (if you have no USB/HID keyboard or mouse) to > force the removal of the hid module and see if the messages still > appears. > > Peter: any thought on this?No, I have not observed this problem. However, I have seen the following: usb 2-1: usbfs: process 13959 (newhidups) did not claim interface 0 before use usb 2-1: usbfs: interface 0 claimed while 'get_descriptor' sets config #1 usb 2-1: usbfs: process 13959 (newhidups) did not claim interface 0 before use usb 2-1: get_descriptor timed out on ep0in usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd get_descriptor rqt 128 rq 6 len 2048 ret -110 I don't know if it's related or not. By the way, "lsusb -v" generates the same type of message: usb 4-1: usbfs: process 13993 (lsusb) did not claim interface 1 before use usb 2-2: usbfs: process 13993 (lsusb) did not claim interface 0 before use -- Peter