From: Andries Brouwer <aebr@win.tue.nl>
To: Rob Landley <rob@landley.net>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: Keyboard oddness.
Date: Fri, 26 Sep 2003 10:15:42 +0200 [thread overview]
Message-ID: <20030926081542.GA21857@win.tue.nl> (raw)
In-Reply-To: <200309252027.57512.rob@landley.net>
On Thu, Sep 25, 2003 at 08:27:57PM -0500, Rob Landley wrote:
> Okay, a little fresh data:
> Sep 25 20:22:22 localhost kernel: atkbd.c: Unknown key (set 2, scancode 0xd1,
> on isa0060/serio0) pressed.
> Sep 25 20:22:22 localhost kernel: i8042 history: d1 e0 51 e0 d1 e0 51 e0 d1 e0
> 51 e0 d1 e0 51 d1
e0 51 is PageDown press
e0 d1 is PageDown release
You see here (apart from the first byte, which probably is the second half
of a PageDown release): PageDown press, release, press, release, press, release,
press, broken release.
A byte e0 was lost, and the release was not seen as a PageDown release.
> The page down key is the one that stuck. I pressed another key (possibly
> either cursor up or page up) to unstick it, and then the next time I pressed
> page down it didn't register, but the time after that it did.
> You're talking about missed keypresses, but the end-user symptom I'm seeing
> is definitely a missed key release
Yes - here a release was garbled.
Many people have reported missing key releases, and, as a consequence of that,
stuck keys. Your reports feel a bit different: the e0 is sometimes lost from
a key press, sometimes from a key release.
next prev parent reply other threads:[~2003-09-26 8:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 20:33 Keyboard oddness Rob Landley
2003-09-20 22:18 ` Andries Brouwer
2003-09-21 18:51 ` Rob Landley
2003-09-21 10:04 ` Vojtech Pavlik
2003-09-21 20:20 ` Rob Landley
2003-09-22 20:06 ` Rob Landley
2003-09-22 22:06 ` Andries Brouwer
2003-09-23 0:23 ` Rob Landley
2003-09-23 10:51 ` Greg Louis
2003-09-25 23:59 ` Rob Landley
2003-09-26 1:27 ` Rob Landley
2003-09-26 8:15 ` Andries Brouwer [this message]
2003-09-26 8:43 ` Rob Landley
2003-09-26 8:46 ` Vojtech Pavlik
2003-09-26 9:43 Nicolas Mailhot
2003-09-26 10:24 ` Vojtech Pavlik
2003-09-26 10:41 ` Nicolas Mailhot
2003-09-26 10:51 ` Vojtech Pavlik
2003-09-26 12:48 ` jw schultz
2003-09-26 13:08 ` Nicolas Mailhot
2003-09-26 13:41 ` Vojtech Pavlik
2003-09-26 14:12 ` Nicolas Mailhot
2003-09-26 14:17 ` Vojtech Pavlik
2003-09-26 14:21 ` Nicolas Mailhot
2003-09-26 14:26 ` Vojtech Pavlik
2003-09-26 14:50 ` Nicolas Mailhot
2003-09-26 15:06 ` Vojtech Pavlik
2003-09-26 15:21 ` Nicolas Mailhot
2003-09-26 15:24 ` Vojtech Pavlik
2003-09-26 13:56 ` Helge Hafting
2003-09-26 14:01 ` Mike Dresser
2003-09-28 10:58 ` Helge Hafting
2003-10-02 12:40 ` Pavel Machek
2003-10-01 10:09 ` Pavel Machek
2003-10-01 13:06 ` Nicolas Mailhot
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=20030926081542.GA21857@win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=vojtech@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).