From: Rob Landley <rob@landley.net>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Keyboard oddness.
Date: Sun, 21 Sep 2003 14:51:39 -0400 [thread overview]
Message-ID: <200309211451.39180.rob@landley.net> (raw)
In-Reply-To: <20030921001838.A3619@pclin040.win.tue.nl>
On Saturday 20 September 2003 18:18, Andries Brouwer wrote:
> On Sat, Sep 20, 2003 at 04:33:22PM -0400, Rob Landley wrote:
> > I've mentioned my keyboard repeat problems before. I grepped through the
> > logs and found a whole bunch of these type messages:
> >
> > Aug 17 05:28:48 atkbd.c: Unknown key (set 2, scancode 0x1d0,
> > on isa0060/serio0) pressed.
> > Aug 19 09:06:51 atkbd.c: Unknown key (set 2, scancode 0x8e,
> > on isa0060/serio0) pressed.
>
> ...
>
> These are key releases for keys i8042.c didnt know were down.
> If otherwise your keyboard functions well, this is harmless.
It doesn't. It's missing key release events left and right. About twice an
hour a key well get "stuck". X is okay once you press a second key, but if a
VT gets a key stuck, it doesn't come back.
> > Sep 2 13:37:52 atkbd.c: Unknown key (set 0, scancode 0xfc,
> > on isa0060/serio1) pressed.
> > Sep 2 13:37:52 atkbd.c: Unknown key (set 0, scancode 0xfc,
> > on isa0060/serio1) pressed.
>
> I suppose these are error codes from your mouse.
> If so, it is a bug that they ever went to atkbd.c.
The mouse sometimes sticks as well, just like the keyboard. (Click and the
button is held down for no reason.)
I suspect the bug is actually in the new input core...
> Andries
Rob
next prev parent reply other threads:[~2003-09-21 18:54 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 [this message]
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
2003-09-26 8:43 ` Rob Landley
2003-09-26 8:46 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
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=200309211451.39180.rob@landley.net \
--to=rob@landley.net \
--cc=aebr@win.tue.nl \
--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