From: Jerry Cooperstein <coop@axian.com>
To: linux-kernel@vger.kernel.org
Subject: Thinkpad Keyboard nuttiness since 2.5.60 with power management
Date: Mon, 24 Feb 2003 15:06:40 -0800 [thread overview]
Message-ID: <20030224230640.GA1225@p3.attbi.com> (raw)
Since 2.5.60 the keyboard on my Thinkpad 600X randomly
autorepeats each stroke multiple times, only when
power management is enabled (either APM or ACPI) and
only when powered up with no AC power. With AC power
everything is fine, and pulling the plug out has
no effects.
Everything was fine in 2.5.59, and I can't find anything
in the 2.5.59->2.5.60 patch that could have caused this.
Anyone else see this -- or maybe I have a hardware problem
the patch is making visible?
Thanks
======================================================================
Jerry Cooperstein, Senior Consultant, <coop@axian.com>
Axian, Inc., Software Consulting and Training
4800 SW Griffith Dr., Ste. 202, Beaverton, OR 97005 USA
http://www.axian.com/
======================================================================
next reply other threads:[~2003-02-24 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 23:06 Jerry Cooperstein [this message]
2003-02-25 19:21 ` Thinkpad Keyboard nuttiness since 2.5.60 with power management daveman
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=20030224230640.GA1225@p3.attbi.com \
--to=coop@axian.com \
--cc=linux-kernel@vger.kernel.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