From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761257Ab0J0QJB (ORCPT ); Wed, 27 Oct 2010 12:09:01 -0400 Received: from mail-yw0-f46.google.com ([209.85.213.46]:50474 "EHLO mail-yw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760843Ab0J0QI7 (ORCPT ); Wed, 27 Oct 2010 12:08:59 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:references:mime-version :content-type:content-disposition:content-transfer-encoding :in-reply-to:user-agent; b=AK2cqYq2S4OQp6jJzOlGBPiKod6IAsXy1rJIGPS2nOPXdc+EEFDkVHJaFEsAXOdq5P oPbvgmM0bvSSWnNqUk0nY9q01LiMKV7KUSxTBe8tx9Aaiwdg2LjtiAfVzkzoOyYfIUtT EHIBousTFkI0f7emWGdAYXfOqDeHQ/ezkhyu0= Date: Wed, 27 Oct 2010 09:08:42 -0700 From: Dmitry Torokhov To: Samuel Thibault , Tom Vier , "594089@bugs.debian.org" <594089@bugs.debian.org>, "linux-input@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Jiri Kosina Subject: Re: Bug#594089: keyboard-configuration: caps lock keycode problem Message-ID: <20101027160842.GB8745@core.coreip.homeip.net> References: <20101025045003.GA1438@core.coreip.homeip.net> <4CC58816.3090301@triadsys.com> <20101025180320.GA4725@const.famille.thibault.fr> <4CC6E9D8.8010201@triadsys.com> <20101026161820.GE13097@core.coreip.homeip.net> <4CC7426C.8040502@triadsys.com> <20101027091029.GB28895@core.coreip.homeip.net> <20101027120513.GT4725@const.famille.thibault.fr> <99F91536-4413-430C-9932-7CEF6AB656DB@gmail.com> <20101027152242.GO4725@const.famille.thibault.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20101027152242.GO4725@const.famille.thibault.fr> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 27, 2010 at 05:22:42PM +0200, Samuel Thibault wrote: > Dmitry Torokhov, le Wed 27 Oct 2010 08:06:26 -0700, a écrit : > > On Oct 27, 2010, at 5:05 AM, Samuel Thibault wrote: > > > > > > Dmitry Torokhov, le Wed 27 Oct 2010 02:10:29 -0700, a écrit : > > > > Also, based on evtest data I only see presses/releases for one key > > (Caps Lock, Right Shift, etc.) I do not see the presses for the additional > > keys in the evtest stream so I am baffled as to where the additional > > scancode is coming from... Do you have some funky keymap loaded? > > Anything interesting in dumpkeys? > > > > > > Err, since the duplicates appear in scancodes already, is the content of > > dumpkeys really involved? > > > > Evtest data does not show any additional events, so the additional scancodes > > must be coming from the legacy keyboard driver. > > Sure, but dumpkeys shows the table from scancodes to keycodes, not from > input events to scancodes. I am just wondering if some of the translation is leaking even though the keyboard is in raw mode... OK, scratch that... Are there any other input devices? Anything connected via uinput and listening? What does /proc/bus/input/devices show? Maybe if Tom could compile and load evbug module it would show us where the additional events are coming form, becaus ethey surely are not generated by the keyboard itself (otherwise we'd have seen them in evtest output for that device). -- Dmitry