From: Pavel Machek <pavel@ucw.cz>
To: "Björn Steinbrink" <B.Steinbrink@gmx.de>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Andi Kleen" <ak@suse.de>, "Jiri Kosina" <jikos@jikos.cz>,
"kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: thinkpad testers wanted (was Re: 2.6.22-rc[23]: blinking capslock led, stuck keys?)
Date: Mon, 4 Jun 2007 17:10:25 +0200 [thread overview]
Message-ID: <20070604151025.GD2059@elf.ucw.cz> (raw)
In-Reply-To: <20070604150613.GC3363@atjola.homenet>
Hi!
> > > >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~
Ok, I did not want to focus on "numpad" keys. Even normal keys
misbehave for me, like being lost or duplicated. Strange.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-06-04 15:10 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 11:24 2.6.22-rc[23]: blinking capslock led, stuck keys? Pavel Machek
2007-06-04 12:08 ` Éric Piel
2007-06-04 12:35 ` Jiri Kosina
2007-06-04 13:09 ` Pavel Machek
2007-06-04 13:12 ` Jiri Kosina
2007-06-04 13:36 ` Pavel Machek
2007-06-04 13:38 ` Jiri Kosina
2007-06-04 13:43 ` Andi Kleen
2007-06-04 13:54 ` Pavel Machek
2007-06-04 14:02 ` Dmitry Torokhov
2007-06-04 14:13 ` thinkpad testers wanted (was Re: 2.6.22-rc[23]: blinking capslock led, stuck keys?) Pavel Machek
2007-06-04 15:06 ` Björn Steinbrink
2007-06-04 15:10 ` Pavel Machek [this message]
2007-06-04 16:20 ` Björn Steinbrink
2007-06-04 15:11 ` Johannes Stezenbach
2007-06-04 15:18 ` Dmitry Torokhov
2007-06-04 20:55 ` Pavel Machek
2007-06-04 16:40 ` Michael Tokarev
2007-06-04 16:34 ` 2.6.22-rc[23]: blinking capslock led, stuck keys? Henrique de Moraes Holschuh
2007-06-04 17:46 ` Dmitry Torokhov
2007-06-04 20:57 ` Pavel Machek
2007-06-12 5:42 ` Dmitry Torokhov
2007-06-12 23:35 ` Indan Zupancic
2007-06-13 8:18 ` Pavel Machek
2007-06-13 14:09 ` Indan Zupancic
2007-06-15 5:41 ` Dmitry Torokhov
2007-06-16 2:04 ` Indan Zupancic
2007-06-16 3:34 ` Dmitry Torokhov
2007-06-16 11:54 ` Indan Zupancic
2007-06-16 15:58 ` Dmitry Torokhov
2007-06-04 18:04 ` Andi Kleen
2007-06-04 15:10 ` Indan Zupancic
2007-06-04 15:13 ` Pavel Machek
2007-06-04 12:35 ` Indan Zupancic
2007-06-04 12:38 ` Jiri Kosina
2007-06-04 14:43 ` Indan Zupancic
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=20070604151025.GD2059@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=B.Steinbrink@gmx.de \
--cc=ak@suse.de \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@jikos.cz \
--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