From owner-freebsd-current@FreeBSD.ORG Wed May 10 03:13:19 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 34FB516A410; Wed, 10 May 2006 03:13:19 +0000 (UTC) (envelope-from mnag@FreeBSD.org) Received: from corp.grupos.com.br (corp.grupos.com.br [200.193.29.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BA5643D45; Wed, 10 May 2006 03:13:18 +0000 (GMT) (envelope-from mnag@FreeBSD.org) Received: from corp.grupos.com.br (corp.grupos.com.br [192.168.10.2]) by corp.grupos.com.br (Postfix) with ESMTP id D8E1C5C37; Wed, 10 May 2006 00:13:16 -0300 (BRT) Received: from [192.168.0.120] (unknown [201.31.23.238]) (Authenticated sender: marcus@corp.grupos.com.br) by corp.grupos.com.br (Postfix) with ESMTP id 69A955C27; Wed, 10 May 2006 00:13:14 -0300 (BRT) Message-ID: <44615A46.6020009@FreeBSD.org> Date: Wed, 10 May 2006 00:13:10 -0300 From: Marcus Alves Grando Organization: FreeBSD.org User-Agent: Thunderbird 1.5 (X11/20060114) MIME-Version: 1.0 To: Emil Mikulic References: <1147219290.1410.6.camel@synergy.odyssey.homeunix.org> <20060510020336.GA25800@cs.rmit.edu.au> In-Reply-To: <20060510020336.GA25800@cs.rmit.edu.au> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Filtered: By ProxSMTP using Clamav and Bogofilter Cc: emax@FreeBSD.org, current@freebsd.org, 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 03:13:19 -0000 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. Regards -- Marcus Alves Grando marcus(at)corp.grupos.com.br | Grupos Internet S/A mnag(at)FreeBSD.org | FreeBSD.org