Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755179AbXFDNoU (ORCPT ); Mon, 4 Jun 2007 09:44:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752269AbXFDNoM (ORCPT ); Mon, 4 Jun 2007 09:44:12 -0400 Received: from mail.suse.de ([195.135.220.2]:47282 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751044AbXFDNoK (ORCPT ); Mon, 4 Jun 2007 09:44:10 -0400 From: Andi Kleen To: Jiri Kosina Subject: Re: 2.6.22-rc[23]: blinking capslock led, stuck keys? Date: Mon, 4 Jun 2007 15:43:48 +0200 User-Agent: KMail/1.9.1 Cc: Pavel Machek , kernel list References: <20070604112426.GA2707@elf.ucw.cz> <20070604130903.GC1971@elf.ucw.cz> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200706041543.49071.ak@suse.de> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 967 Lines: 28 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/