From owner-freebsd-current@FreeBSD.ORG Wed May 10 17:24:40 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A577516A4BF; Wed, 10 May 2006 17:24:40 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEA5F43D53; Wed, 10 May 2006 17:24:38 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id F19D23BE6F; Wed, 10 May 2006 12:24:37 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14532-01-33; Wed, 10 May 2006 12:24:37 -0500 (CDT) Received: from [10.254.186.111] (sntc04ep01.savvis.net [64.14.1.106]) by mailgate1b.savvis.net (Postfix) with ESMTP id 2B5E43BE6D; Wed, 10 May 2006 12:24:37 -0500 (CDT) Message-ID: <446221D4.1050305@savvis.net> Date: Wed, 10 May 2006 10:24:36 -0700 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marcus Alves Grando References: <1147219290.1410.6.camel@synergy.odyssey.homeunix.org> <20060510020336.GA25800@cs.rmit.edu.au> <44615A46.6020009@FreeBSD.org> In-Reply-To: <44615A46.6020009@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at savvis.net Cc: emax@FreeBSD.org, current@freebsd.org, Emil Mikulic , Pascal Hofstee Subject: Re: kbdmux oddity ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 May 2006 17:24:42 -0000 Marcus Alves Grando wrote: > Emil Mikulic wrote: > >>On Tue, May 09, 2006 at 05:01:30PM -0700, Pascal Hofstee wrote: >> >>>I recently decided to add kbdmux support to my default kernel config >>>since i noticed at times that upon kernel panics and similar events my >>>USB keyboard goes dead. >>> >>>Today i got to actually installing a kbdmux enabled kernel and came to >>>the conclusion that even though keys like Capslock, Numlock and >>>Scrolllock perform the functions they're supposed to do, the keyboard >>>leds seem to arbitrarily decide wether or not they want to toggle >>>on/off. >>> >>>on console i noticed that usually after hitting e.g. caps lock a few >>>times the leds decdide to "work with me again" and toggle on/off >>>accordingly .. until i hit any actual textual input .. at which point >>>the previous eratic behavior has resurfaced. >>> >>>Similar problems exist in X as well ... though seem to be even more >>>eratic there. >>> >>>Removing kbdmux from my kernel seems to restore normality again. >>> >>>Am i the only one seeing these problems ? >> >>I'm seeing a similar (but different?) problem - I get an interrupt storm >>every time I hit Caps Lock or Num Lock, or flip VTs in text mode. If >>XMMS is running, the music skips. > > I already get this too and already report to kbdmux maintainer. i can not reproduce it here with dell latitude d610 laptop. i think, that this maybe particular usb keyboard/bios fault. kbdmux(4) really does not do anything except switching slave keyboards into "raw" mode and pass all scancodes to the upper layers. it seems like kbdmux(4) exposes all the little problems with low level keyboard drivers. again, i'm looking into this, but i do not have much time right now. thanks max