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: <Pine.LNX.4.64.0706041511010.29896@twin.jikos.cz>
Date:	Mon, 4 Jun 2007 15:12:57 +0200 (CEST)
From:	Jiri Kosina <jikos@...os.cz>
To:	Pavel Machek <pavel@....cz>
cc:	kernel list <linux-kernel@...r.kernel.org>, Andi Kleen <ak@...e.de>
Subject: Re: 2.6.22-rc[23]: blinking capslock led, stuck keys?

On Mon, 4 Jun 2007, Pavel Machek wrote:

> CONFIG_BLINK=y
> OOps. WTF is that?
> 
> config BLINK
> 	tristate "Keyboard blink driver"
> 	help
> 	  Driver that when loaded will blink the keyboard LEDs
> continuously.
> 	  This is useful for debugging and for kernels that cannot
> necessarily
> 	  output something to the screen like kexec kernels to give
> the user
> 	  a visual indication that the kernel is doing something.
> ..does it need "default n"? Why does it make keys stuck sometimes?

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.

-- 
Jiri Kosina
-
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/