From: Pavel Machek <pavel@ucw.cz>
To: Indan Zupancic <indan@nul.nu>
Cc: Dmitry Torokhov <dtor@insightbb.com>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Andi Kleen <ak@suse.de>, Jiri Kosina <jikos@jikos.cz>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.22-rc[23]: blinking capslock led, stuck keys?
Date: Wed, 13 Jun 2007 10:18:25 +0200 [thread overview]
Message-ID: <20070613081825.GF13747@elf.ucw.cz> (raw)
In-Reply-To: <52481.81.207.0.53.1181691356.squirrel@secure.samage.net>
Hi!
> > For what it worth I finally tried that setleds loop on my laptop. I am
> > not getting any lost keypresses/releases. But then I don't have EC
> > (or at least it is not exported via ACPI). This is an old Dell notebook.
>
> Well, as I said before, I've the "stuck key"/repeated output too (as well
> as a warping PS/2 mouse), but no blinking led problem, so I believe the
> two things are totally unrelated.
Well, after turning off CONFIG_BLINK, my problems went away, and with
a fast-blink done from userspace, I can make them way worse. They
_are_ related here.
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-13 8:18 UTC|newest]
Thread overview: 37+ 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
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 [this message]
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
[not found] <8siVc-46n-17@gated-at.bofh.it>
[not found] ` <8sktY-6G7-13@gated-at.bofh.it>
[not found] ` <8skDC-6Su-5@gated-at.bofh.it>
[not found] ` <8sl6G-7uE-9@gated-at.bofh.it>
[not found] ` <8slgk-7Gl-3@gated-at.bofh.it>
[not found] ` <8slq0-89X-9@gated-at.bofh.it>
[not found] ` <8snLc-3ik-29@gated-at.bofh.it>
2007-06-06 11:26 ` Bodo Eggert
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=20070613081825.GF13747@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=ak@suse.de \
--cc=dtor@insightbb.com \
--cc=hmh@hmh.eng.br \
--cc=indan@nul.nu \
--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