[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070604150613.GC3363@atjola.homenet>
Date: Mon, 4 Jun 2007 17:06:13 +0200
From: Björn Steinbrink <B.Steinbrink@....de>
To: Pavel Machek <pavel@....cz>
Cc: Dmitry Torokhov <dmitry.torokhov@...il.com>,
Andi Kleen <ak@...e.de>, Jiri Kosina <jikos@...os.cz>,
kernel list <linux-kernel@...r.kernel.org>
Subject: Re: thinkpad testers wanted (was Re: 2.6.22-rc[23]: blinking capslock led, stuck keys?)
On 2007.06.04 16:13:45 +0200, Pavel Machek wrote:
> Hi!
>
> > >> > Anyway, added Andi to CC.
> > >>
> > >> Hmm, in theory it could be triggering bugs in some buggy keyboard
> > >> controller. But then a
> > >>
> > >> while true ; do setleds +caps +numlock ; sleep 1 ; setleds -caps
> > >-numlock ;
> > >> sleep 1 ; done
> > >>
> > >> should trigger it too.
> > >
> > >...and it does.
> > >
> > >pavel@amd:~$ while true; do setleds +num; setleds -num; done
> > >Hm,m so thiis iis a teest of fkeyboarad behaviour under lloadd.
> > >
> > >pavel@amd:~$
> > >
> > >...but I'm not quite sure it is a buggy keyboard. It happens _way_ too
> > >often. Launch the line above and try to do some typing...
> >
> > This used to work fine on my box last time I tried it (the switch
> > itself is offloaded to a keventd and shoud not get in the way) but
> > then they push all kind of ACPI/SMM crap together with KBC so who
> > knows... I should try it again when I get home.
>
> Hmm, this needs to be ran from console (not X). Can someone with
> thinkpad try this?
The version that doesn't sleep totally messes up keyboard input on my
T43. Some keypresses are totally ignored and the keys that are part of
the "numpad" sometimes generate crap, e.g. holding down "j"
results in j, 1 or ^[[4~
Björn
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists