From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Re:Re: Linux 2.6.0-test4
Date: Tue, 2 Sep 2003 10:07:33 +0200 [thread overview]
Message-ID: <20030902080733.GA14380@charite.de> (raw)
In-Reply-To: <20030831120605.08D6.CHRIS@heathens.co.nz>
* Chris Heath <chris@heathens.co.nz>:
> > Aug 27 18:53:41 hummus2 kernel: atkbd.c: Unknown key (set 2, scancode 0x9d, on isa0060/serio0) pressed.
> > Aug 27 19:15:14 hummus2 kernel: atkbd.c: Unknown key (set 2, scancode 0xb9, on isa0060/serio0) pressed.
> > Aug 27 19:42:50 hummus2 kernel: atkbd.c: Unknown key (set 2, scancode 0x9d, on isa0060/serio0) pressed.
> > Aug 28 10:14:14 hummus2 kernel: atkbd.c: Unknown key (set 2, scancode 0x9d, on isa0060/serio0) pressed.
> >
> > Basically, CTRL was stuck. Even when I switched to X11.
>
> Well, this completely baffles me. I thought X11 maintains its own
> keydown array.
>
> Anyway, I've included a patch that should hopefully give us better
> debugging information. When you get an unknown key error, it will also
> dump the last 16 bytes that were sent from the keyboard. Be careful
> with this one. If you post any errors to the list, make sure it doesn't
> contain any sensitive passwords. :-)
I got some more events, and today I even was able to reproduc the
"CTRL-is-stuck" problem.
I was able to get the key unstuck by switching back and forth between
dirrerent FB consoles and by pushing and releaseing CTRL in them...
Sep 2 09:10:01 hummus2 kernel: atkbd.c: Unknown key (set 2, scancode 0x9c, on isa0060/serio0) pressed.
Sep 2 09:10:01 hummus2 kernel: i8042 history: e0 d0 1c 9c 2e ae 10 90 e0 50 e0 d0 e0 d0 1c 9c
Sep 2 09:10:06 hummus2 kernel: atkbd.c: Unknown key (set 2, scancode 0xa0, on isa0060/serio0) pressed.
Sep 2 09:10:06 hummus2 kernel: i8042 history: 1c 9c 1c 9c e0 50 e0 d0 e0 50 e0 d0 e0 d0 20 a0
Sep 2 09:14:54 hummus2 kernel: input: AT Set 2 keyboard on isa0060/serio0
Sep 2 09:25:44 hummus2 kernel: atkbd.c: Unknown key (set 2, scancode 0x9d, on isa0060/serio0) pressed.
Sep 2 09:25:44 hummus2 kernel: i8042 history: e0 50 e0 d0 e0 50 e0 d0 e0 d0 1d 2d ad 1f 9f 9d
Sep 2 09:30:34 hummus2 kernel: atkbd.c: Unknown key (set 2, scancode 0xb9, on isa0060/serio0) pressed.
Sep 2 09:30:34 hummus2 kernel: i8042 history: e0 48 e0 c8 39 b9 e0 38 56 d6 e0 b8 e0 b8 39 b9
Sep 2 09:35:51 hummus2 kernel: atkbd.c: Unknown key (set 2, scancode 0xb9, on isa0060/serio0) pressed.
Sep 2 09:35:51 hummus2 kernel: i8042 history: a0 20 a0 9d e0 4d e0 cd e0 4d e0 cd e0 cd 39 b9
--
Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de
Charite Campus Mitte Tel. +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze - Fax. +49 (0)30-450 570-916
AIM: ralfpostfix
next prev parent reply other threads:[~2003-09-02 8:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-31 16:22 Re:Re: Linux 2.6.0-test4 Chris Heath
2003-09-01 16:01 ` Ralf Hildebrandt
2003-09-02 0:16 ` [PATCH] keyboard - was: " Andries Brouwer
2003-09-02 5:39 ` Ralf Hildebrandt
2003-09-02 8:07 ` Ralf Hildebrandt [this message]
2003-09-02 10:47 ` Andries Brouwer
2003-09-02 11:18 ` Ralf Hildebrandt
2003-09-02 12:32 ` Ralf Hildebrandt
2003-09-02 21:41 ` Andries Brouwer
2003-09-03 7:45 ` Ralf Hildebrandt
2003-09-03 13:25 ` Ralf Hildebrandt
-- strict thread matches above, loose matches on Subject: below --
2003-08-30 14:13 Chris Heath
2003-08-30 14:59 ` Ralf Hildebrandt
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=20030902080733.GA14380@charite.de \
--to=ralf.hildebrandt@charite.de \
--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