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 for Android: free password hash cracker in your pocket

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

Message-Id: <200706041543.49071.ak@suse.de>
Date:	Mon, 4 Jun 2007 15:43:48 +0200
From:	Andi Kleen <ak@...e.de>
To:	Jiri Kosina <jikos@...os.cz>
Cc:	Pavel Machek <pavel@....cz>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.22-rc[23]: blinking capslock led, stuck keys?

On Monday 04 June 2007 15:12, Jiri Kosina wrote:

> 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.

 Anyways; it is normally only intended for special
case kdump or other debugging kernels which tend to not get 
much interaction; you shouldn't really set it anywhere else.

I've been also considering to make it always dependent on
a command line option, but that is not done yet.

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