From: Josh Boyer <jwboyer@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: USB device PM oddity in 3.5
Date: Thu, 24 May 2012 16:36:56 -0400 [thread overview]
Message-ID: <20120524203655.GK1143@zod.bos.redhat.com> (raw)
I'm testing Linus' tree as the merge window happens, and I've hit an
issue with what I believe is USB device power management (or something)
that is causing my mouse and keyboard to become unresponsive. After a
very short time of non-use, either device will cut out. I can move the
mouse around but it doesn't relay to the screen and I noticed this is
because the laser is turned off. If I click a button on it, it will
turn back on and function again until a small period of non-use. The
keyboard exhibits similar behavior, "ignoring" the first few key strokes
until it wakes back up.
I found this thread:
http://thread.gmane.org/gmane.linux.usb.general/64292
and
http://marc.info/?t=133552726500001&r=1&w=2
which have similar symptoms, but the kernels I'm using have the
subsequent patches applied. I'm doing a git bisect at the moment, with
72c04af as the starting good commit and 61011677 as the first bad. I'll
let you know what comes of this, but I thought I'd mail about it now in
case anyone has any ideas.
josh
next reply other threads:[~2012-05-24 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 20:36 Josh Boyer [this message]
2012-05-24 20:48 ` USB device PM oddity in 3.5 Alan Stern
2012-05-25 11:39 ` Josh Boyer
2012-05-25 11:41 ` Matthew Garrett
2012-05-25 11:45 ` Josh Boyer
2012-05-25 11:50 ` Josh Boyer
2012-05-25 11:56 ` Matthew Garrett
2012-05-25 13:00 ` Lan Tianyu
2012-05-25 13:08 ` Matthew Garrett
2012-05-25 14:27 ` Josh Boyer
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=20120524203655.GK1143@zod.bos.redhat.com \
--to=jwboyer@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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