On Mon, Apr 19, 2010 at 07:08:37PM -0400, Charles Lepple wrote: > On Mon, Apr 19, 2010 at 4:22 PM, Kelvin Ku > <[email protected]> wrote: > > Hello, > > > > I have a TrippLite SU2200XLA UPS with a possibly unreliable USB interface > > running on NUT 2.4.3. This flooded syslog last night, beginning with the USB > > connection spontaneously reconnecting: > > > > Apr 18 22:00:42 kernel: hiddev96: USB HID v1.11 Device [Tripp Lite > > TRIPP LITE UPS ] on usb-0000:00:0f.2-2 > > Apr 18 22:00:44 usbhid-ups[486]: Got disconnected by another driver: Device > > or resource busy > > Apr 18 22:00:46 usbhid-ups[486]: Got disconnected by another driver: Device > > or resource busy > > Apr 18 22:00:48 usbhid-ups[486]: Got disconnected by another driver: Device > > or resource busy > > Rather than restarting the driver, you probably want to start by > figuring out what else is claiming the driver. You can only have one > program talking HID to a USB device* at a time. Do you have any other > power management software on your system which might try to grab this > device? > > * technically, one per interface, but most UPSes have one HID interface. > > -- > - Charles Lepple >
Sorry, I left this out of the paste: Apr 18 22:00:42 kernel: hub 1-0:1.0: port 2 disabled by hub (EMI?), re-enabling... Apr 18 22:00:42 kernel: usb 1-2: USB disconnect, address 5 Apr 18 22:00:42 kernel: usb 1-2: new low speed USB device using ohci_hcd and address 6 Apr 18 22:00:42 kernel: usb 1-2: configuration #1 chosen from 1 choice Apr 18 22:00:42 kernel: hiddev96: USB HID v1.11 Device [Tripp Lite TRIPP LITE UPS ] on usb-0000:00:0f.2-2 Does this indicate something is flaky with the USB connection? I don't think the device is actually being claimed by another driver: $ ps -ef | egrep 'usb|hid' root 119 2 0 Mar13 ? 00:00:00 [ksuspend_usbd] hero 13364 13004 0 20:06 pts/0 00:00:00 egrep usb|hid There's nothing else in syslog around the time that the device was disconnected. Just to be clear, I didn't physically reconnect the device at 22:00:42; it was connected long before that. Also, this specific unit does this on every host I connect it to, so it could be a bad USB interface on the UPS (or maybe a bad cable?), in which case I hope I can configure the software to work around it. - Kelvin _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
