Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265343AbUAJThu (ORCPT ); Sat, 10 Jan 2004 14:37:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265213AbUAJTf0 (ORCPT ); Sat, 10 Jan 2004 14:35:26 -0500 Received: from twilight.ucw.cz ([81.30.235.3]:9127 "EHLO twilight.ucw.cz") by vger.kernel.org with ESMTP id S265338AbUAJTeF (ORCPT ); Sat, 10 Jan 2004 14:34:05 -0500 Date: Sat, 10 Jan 2004 20:34:04 +0100 From: Vojtech Pavlik To: linux-kernel@vger.kernel.org Subject: Re: [2.6.1] atkbd.c: Unknown key released Message-ID: <20040110193404.GB22654@ucw.cz> References: <20040110183116.GA8319@ss1000.ms.mff.cuni.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040110183116.GA8319@ss1000.ms.mff.cuni.cz> User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 973 Lines: 26 On Sat, Jan 10, 2004 at 07:31:16PM +0100, Rudo Thomas wrote: > Hello. > > This line shows up twice in dmesg when starting up X. > > atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). > > Tried with 2.6.1, 2.6.1-mm1. It does not happen in 2.6.0, IIRC. I don't seem to > be able to reproduce the message by pressing any combination on keyboard. > > Full dmesg output is atteched. This is a bug in X. It talks directly to the keyboard controller. And that's a rather nasty one. I got a couple reports of "My keyboard stops working in X", and this is exactly why. X can rather easily confuse the controller by talking to it in parallel with the kernel driver. -- Vojtech Pavlik SuSE Labs, SuSE CR - 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/