From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265732AbTL3VsW (ORCPT ); Tue, 30 Dec 2003 16:48:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265803AbTL3VsW (ORCPT ); Tue, 30 Dec 2003 16:48:22 -0500 Received: from mailhost.tue.nl ([131.155.2.7]:16650 "EHLO mailhost.tue.nl") by vger.kernel.org with ESMTP id S265732AbTL3VsU (ORCPT ); Tue, 30 Dec 2003 16:48:20 -0500 Date: Tue, 30 Dec 2003 17:37:42 +0100 From: Andries Brouwer To: Meelis Roos Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.0+BK keyboard problems Message-ID: <20031230163742.GB17107@win.tue.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 30, 2003 at 12:04:31PM +0200, Meelis Roos wrote: > Additionally, when X starts, these two messages appear in dmesg: > atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). > atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0). That is a kernel debugging message bug. You got an ACK from the keyboard, 0xfa, and that is not unknown, and not the release of a key with scancode 0x7a.