mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	nut-upsuser@lists.alioth.debian.org
Subject: 2.6.38.3 w/nut: libusb_get_string: error sending control message: Broken pipe
Date: Thu, 21 Apr 2011 13:34:51 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1104211247370.4005@p34.internal.lan> (raw)

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.





                 reply	other threads:[~2011-04-21 17:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.02.1104211247370.4005@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=nut-upsuser@lists.alioth.debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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®