* 2.6.38.3 w/nut: libusb_get_string: error sending control message: Broken pipe
@ 2011-04-21 17:34 Justin Piszcz
0 siblings, 0 replies; only message in thread
From: Justin Piszcz @ 2011-04-21 17:34 UTC (permalink / raw)
To: linux-kernel, linux-usb, nut-upsuser
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.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-04-21 17:34 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-04-21 17:34 2.6.38.3 w/nut: libusb_get_string: error sending control message: Broken pipe Justin Piszcz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®