From: Arjan van de Ven <arjan@infradead.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
nut-upsuser@lists.alioth.debian.org, bruce.w.allan@intel.com,
Alan Piszcz <ap@solarrain.com>
Subject: Re: 2.6.31.4: Intel P55 Chipset BUG [usbhid-raw/devices/broken?] [tested 3 different UPS']
Date: Sat, 31 Oct 2009 17:07:49 -0700 [thread overview]
Message-ID: <20091031170749.4c2470ff@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.00.0910311847530.5522@p34.internal.lan>
On Sat, 31 Oct 2009 19:43:38 -0400 (EDT)
Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> >> Problem appears to be the Intel P55KG / USB Chipset in the way
> >> that it handles usbhid-raw devices as CD/USB sticks/kbd/mouse/etc
> >> do not appear to be affected.
> >>
> >> So far all other USB devices work fine, with the exception of
> >> UPS', I have tested two APC 1500VA (one an RS the other an XS), in
> >> addition I also have a 'BELKIN 1200VA UPS with AVR' from a long
> >> time ago, the same problem occurs.
> >
> > ...
> >
> >> A bit frustrated, I popped in a PCI card with 4 external USBs, and
> >> now no more errors:
just as a wild guess;
does it go away if you disable CONFIG_USB_SUSPEND ?
also, google suggests that your bios may not have c-states enabled;
if so, enabling those in the bios might also be a good idea
--
Arjan van de Ven Intel Open Source Technology
CentreCONFIG_USB_SUSPEND For development, discussion and tips for power
savings,visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-11-01 0:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 14:58 2.6.31.4: Any other suggestions regarding a UPS/USB (APC1500VA) on (Intel P55KG) stale issue? Justin Piszcz
2009-10-31 11:59 ` 2.6.31.4: Intel P55 Chipset BUG [usbhid-raw/devices/broken?] [tested 3 different UPS'] Justin Piszcz
2009-10-31 15:18 ` Alan Stern
2009-10-31 23:43 ` Justin Piszcz
2009-11-01 0:07 ` Arjan van de Ven [this message]
2009-11-01 8:55 ` Justin Piszcz
2009-11-01 17:11 ` Alan Stern
2009-11-01 17:52 ` Matthew Dharm
2009-11-01 21:18 ` Justin Piszcz
2009-11-01 21:25 ` Justin Piszcz
2009-11-02 0:49 ` Matthew Dharm
2009-11-02 13:43 ` Henrique de Moraes Holschuh
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=20091031170749.4c2470ff@infradead.org \
--to=arjan@infradead.org \
--cc=ap@solarrain.com \
--cc=bruce.w.allan@intel.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nut-upsuser@lists.alioth.debian.org \
--cc=stern@rowland.harvard.edu \
/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®