linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: Keyboard oddness.
Date: Thu, 25 Sep 2003 20:27:57 -0500	[thread overview]
Message-ID: <200309252027.57512.rob@landley.net> (raw)
In-Reply-To: <20030923000647.A1128@pclin040.win.tue.nl>

On Monday 22 September 2003 17:06, Andries Brouwer wrote:

> > Any clues?  (This happens to me at least once an hour...)
>
> Some people have been reporting missing key releases (maybe also you),
> but these are all missing key presses. It is easiest to blame the
> keyboard, even though I could imagine ways to blame the kernel.
>
> What about 2.4? Do you have to go back once an hour and add a symbol
> that was not transmitted correctly? Does 2.4 work perfectly for you?
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Okay, a little fresh data:

I just had the keyboard key sticking problem occur, 2.6.0-test5-mm4.

Sep 25 20:06:25 localhost dhclient: DHCPREQUEST on eth0 to 128.83.185.55 port 
67
Sep 25 20:06:25 localhost dhclient: DHCPACK from 128.83.185.55
Sep 25 20:06:25 localhost dhclient: bound to 128.62.240.239 -- renewal in 1608 
seconds.
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
Sep 25 20:22:42 localhost su(pam_unix)[2047]: session opened for user root by 
landley(uid=500)

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.

Checking the log, I saw the above message.  This is the first time since the 
last reboot the problem has occurred, and the first such message since the 
last reboot.  The message IS occurring when I have the key sticking problem, 
as shown by the timestamps.

You're talking about missed keypresses, but the end-user symptom I'm seeing is 
definitely a missed key release, and it's associated with the above log 
message.

Rob

  parent reply	other threads:[~2003-09-26  1:31 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 [this message]
2003-09-26  8:15         ` Andries Brouwer
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=200309252027.57512.rob@landley.net \
    --to=rob@landley.net \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --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).