From: Vojtech Pavlik <vojtech@suse.cz>
To: Dmitri Katchalov <dmitrik@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org, Andries Brouwer <aebr@win.tue.nl>
Subject: Re: 2.6.0-test5 atkbd.c: Unknown key (100% reproduceable)
Date: Sat, 20 Sep 2003 13:38:03 +0200 [thread overview]
Message-ID: <20030920113803.GA8779@ucw.cz> (raw)
In-Reply-To: <003c01c37b8f$9e09fba0$0a01a8c0@internal.dimasoftware.com>
On Mon, Sep 15, 2003 at 11:45:25PM +1000, Dmitri Katchalov wrote:
> > On Sun, Sep 14, 2003 at 06:12:49PM +1000, Dmitri Katchalov wrote:
> > > Quoting Andries Brouwer <aebr@win.tue.nl>:
> >
> > > > On Sat, Sep 13, 2003 at 06:51:14PM +1000, Dmitri Katchalov wrote:
> > > >
> > > > > I'm consistently getting this error:
> > > > >
> > > > > atkbd.c: Unknown key (set 2, scancode 0xab, on isa0060/serio0)
> pressed.
> > > > > This happens whenever I type 'f' in "<F7>usbdevfs".
> >
> > It seems most likely that this keyboard is broken.
> > Instead of 0xa1 (f release) you get 0xab (\ release).
> > By some coincidence 0xab is f release in untranslated scancode set 2.
> > (But you are in translated scancode set 2, otherwise the other letters
> > would also have produced different codes.)
> >
> > Could you try to run "showkey -s" on the console under 2.4.*?
> > Hit and release the f a few times. Type <F7>usbdevfs.
> >
> > Just a broken key is something I have seen lots of times.
> > Since for most operating systems make codes are important
> > while break codes (other than those for Shift, Ctrl, Alt)
> > are not, a key with broken release code is usually harmless.
> >
> > This case seems interesting because, if I understand you correctly,
> > the f in itself is not always broken, but this error occurs after
> > a particular sequence of keystrokes.
>
> I've just run showkey. This is WEIRD! I've never seen anything
> like it (almost)! It is definitely a bug in my keyboard.
> Whenever 'f' occurs in the stream exactly 12 scancodes
> after <F7> it reports wrong release code. It even has a "queue"
> so that multiple instances of the bug can be pipelined :)
Interesting. Can you check if it goes away with a different keyboard?
How about when you disable ACPI?
> Interestingly the bug has no ill effects on 2.4.18 at all. It just works.
> In 2.6.0-test5 I'm getting a message right across the screen followed
> by zillions of 'f's.
>
> Andries, thanks for your time and for the hints you gave me. I'll put a
> workaround in my kernel. I don't think it will be useful to anyone else
> though:)
Next available 2.6 should have that worked around.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
prev parent reply other threads:[~2003-09-20 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 8:51 2.6.0-test5 atkbd.c: Unknown key (100% reproduceable) Dmitri Katchalov
2003-09-13 20:07 ` Andries Brouwer
2003-09-14 8:12 ` Dmitri Katchalov
2003-09-14 16:51 ` Andries Brouwer
2003-09-15 13:45 ` Dmitri Katchalov
2003-09-20 11:38 ` Vojtech Pavlik [this message]
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=20030920113803.GA8779@ucw.cz \
--to=vojtech@suse.cz \
--cc=aebr@win.tue.nl \
--cc=dmitrik@users.sourceforge.net \
--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