Justin Piszcz
2011-Apr-21 17:34 UTC
[Nut-upsuser] 2.6.38.3 w/nut: libusb_get_string: error sending control message: Broken pipe
Hello, Dist: Debian Testing Kernel: 2.6.38.3 Software: nut 2.6.0-1 I believe this is a chipset bug, are there any plans for a workaround? The messages have changed over the kernel versions for this problem, but the problem itself still exists: Apr 21 09:17:25 p34 usbhid-ups[3737]: libusb_get_string: error sending control message: Broken pipe Apr 21 09:44:20 p34 usbhid-ups[3737]: libusb_get_string: error sending control message: Broken pipe Error from 2009 (still a problem) http://lists.alioth.debian.org/pipermail/nut-upsuser/2009-October/005530.html This occurred on my last Intel motherboard (Intel 965WH) and current motherboard, Intel DP55KG. Is there something that can be 'fixed' or an workaround implemented, or should I just send these messages to /dev/null? As the nut software does work OK, I keep getting these errors in the logs. Thanks, Justin.
Reasonably Related Threads
- 2.6.31.4: Any other suggestions regarding a UPS/USB (APC1500VA) on (Intel P55KG) stale issue?
- USB/UPS connectivity issue on Intel DP55KG Motherboard
- nut-2.2.0+linux kernel usb/hiddev bug
- nut 2.0.5-3+b1 reports low battery, previous versions do not
- libusb_get_string: invalid argument