linux-kernel - Re: 2.6.22-rc[23]: blinking capslock led, stuck keys?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d120d5000706040702q3b5251e8oc5e9f3c198f060bd@mail.gmail.com>
Date:	Mon, 4 Jun 2007 10:02:33 -0400
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"Pavel Machek" <pavel@....cz>
Cc:	"Andi Kleen" <ak@...e.de>, "Jiri Kosina" <jikos@...os.cz>,
	"kernel list" <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.22-rc[23]: blinking capslock led, stuck keys?

On 6/4/07, Pavel Machek <pavel@....cz> wrote:
> Hi!
>
> > > Are you sure that it's this dummy blink driver that makes the kernel
> > > stuck? I can't see how it could be causing any hogs - see commit f038f9.
> > >
> > > 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.

-- 
Dmitry
-
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/