From: Vojtech Pavlik <vojtech@suse.cz>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Andries Brouwer <aebr@win.tue.nl>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: Another keyboard woes with 2.6.0...
Date: Fri, 19 Sep 2003 13:38:24 +0200 [thread overview]
Message-ID: <20030919113824.GB784@ucw.cz> (raw)
In-Reply-To: <20030913214047.GF8973@vana.vc.cvut.cz>
On Sat, Sep 13, 2003 at 11:40:47PM +0200, Petr Vandrovec wrote:
> On Sat, Sep 13, 2003 at 08:52:44PM +0200, Andries Brouwer wrote:
> > On Fri, Sep 12, 2003 at 08:33:24PM +0200, Petr Vandrovec wrote:
> >
> > > Andries is already gathering info for this one. This problem (missed
> > > key release) happens to me on all systems I have (Athlon + via, P3 + i440BX,
> > > P4 + 845...), most often when I do alt+right-arrow for walking through
> > > consoles (and for Andries: hitting key stops this, otherwise it
> > > endlessly switches all VTs around, and while kernel thinks that key
> > > is down, keyboard actually does not generate any IRQs, so keyboard knows
> > > that all keys are released).
> >
> > OK. It seems to me the two main hypotheses are: (i) problem with timers,
> > (ii) problem with keyboard.
> >
> > In other words: could you (and/or anybody else who can reproduce this
> > at will) change the #undef DEBUG in i8042.c to #define DEBUG, recreate
> > the problem, and post or mail the resulting file with keystrokes?
> >
> > [of course: cut away parts corresponding to login sequences etc.]
> >
> > This will probably allow us to decide whether the missing key release
> > was never sent by the keyboard, or was lost by the kernel.
>
> Unfortunately I'm at home, while box is at work, so I could only reboot it,
> and confirm that it happened again. Unfortunately I cannot go to the box
> and hit any key to get some more data. But I'll enable this on my workstation,
> and if I'll get some "unexpected keycode" or "keyboard reconnect" errors again,
> I'll have more data in the hand.
>
> >From log it looks like that switch likes 0x41 a lot: it reports ID 0x41AB,
> it reports current scan set 0x41, and when we enable it, it returns spurious
> 0x41... And the last 0x41 is one which confuses everything.
I've just sent a patch to Linus that should fix this. Please try ...
(either get the patch from LKML or wait for next Linus's release).
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2003-09-19 11:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 18:33 Petr Vandrovec
2003-09-13 18:52 ` Andries Brouwer
2003-09-13 21:40 ` Petr Vandrovec
2003-09-14 10:13 ` Andries Brouwer
2003-09-14 10:34 ` Andries Brouwer
2003-09-14 19:52 ` Petr Vandrovec
2003-09-14 22:10 ` Andries Brouwer
2003-09-19 11:38 ` Vojtech Pavlik [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 16:50 Petr Vandrovec
2003-09-12 17:45 ` Zwane Mwaikambo
2003-09-16 21:23 ` Andries Brouwer
2003-09-16 22:45 ` Jamie Lokier
2003-09-16 22:49 ` Zwane Mwaikambo
2003-09-16 23:12 ` Zwane Mwaikambo
2003-09-16 23:18 ` Zwane Mwaikambo
2003-09-17 0:01 ` Andries Brouwer
2003-10-06 22:08 ` Petr Vandrovec
2003-10-14 18:16 ` Petr Vandrovec
2003-10-14 21:27 ` Andries Brouwer
2003-09-13 19:06 ` Pekka Pietikainen
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=20030919113824.GB784@ucw.cz \
--to=vojtech@suse.cz \
--cc=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
--cc=zwane@linuxpower.ca \
/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
all inboxes | Powered by JetHome®