From owner-freebsd-current@FreeBSD.ORG Thu Jun 29 11:09:19 2006 Return-Path: X-Original-To: freebsd-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 6690716A407 for ; Thu, 29 Jun 2006 11:09:19 +0000 (UTC) (envelope-from Lena@lena.kiev.ua) Received: from mx.uatele.com (mx.uatele.com [62.80.178.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id B38AC43D55 for ; Thu, 29 Jun 2006 11:09:18 +0000 (GMT) (envelope-from Lena@lena.kiev.ua) Received: from bedside.lena.kiev.ua (c.229.174.a516.dyn.adsl.cyfra.net [62.80.174.229]) by mx.uatele.com (8.13.6/8.13.6) with ESMTP id k5TB9Fvb023507; Thu, 29 Jun 2006 14:09:15 +0300 Received: from bedside.lena.kiev.ua (localhost.lena.kiev.ua [127.0.0.1]) by bedside.lena.kiev.ua (8.13.7/8.13.7) with ESMTP id k5TB9FvK001432; Thu, 29 Jun 2006 14:09:15 +0300 (EEST) (envelope-from Lena@lena.kiev.ua) Received: (from lena@localhost) by bedside.lena.kiev.ua (8.13.7/8.13.7/Submit) id k5TB9E1A001431; Thu, 29 Jun 2006 14:09:14 +0300 (EEST) (envelope-from Lena@lena.kiev.ua) Date: Thu, 29 Jun 2006 14:09:14 +0300 From: Lena@lena.kiev.ua To: freebsd-current@freebsd.org Message-ID: <20060629110914.GA534@lena.kiev> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44615A46.6020009@FreeBSD.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.87, clamav-milter version 0.87 on mx.uatele.com X-Virus-Status: Clean X-Mailman-Approved-At: Thu, 29 Jun 2006 12:25:47 +0000 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: Thu, 29 Jun 2006 11:09:19 -0000 On Tue, May 09, 2006 at 05:01:30PM -0700, Pascal Hofstee wrote: > 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. Emil Mikulic wrote: > 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. > > Normally, if I'm hitting letter keys, I never see any irq1: atkbd0 > interrupts. If I bounce on the Caps Lock, I can get it as high as > 72/sec. > > Running top(1), I can get system time up to about 50% by pounding away > at Caps Lock. Normal typing doesn't affect the system time much, it > fluctuates between 0% and 1%. > > This is with 7-CURRENT, GENERIC, on x86, from yesterday. And it's on a > Dell GX280 with a USB keyboard. I've seen similar issues on a Dell > Poweredge SC430, again with a USB keyboard. > If I add hint.atkbd.0.disabled="1" to /boot/loader.conf, > I no longer see this problem. Maksim Yevmenkin wrote on May 10, 2006: > 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. FreeBSD 6.1-RELEASE-p2, Abit BE6-II motherboard made in 2000 or 2001, PS/2 keyboard, no USB keyboard. In console the Caps Lock key works, but the Caps Lock LED doesn't lit up at all. In X the LED works OK. Adding hint.kbdmux.0.disabled="1" to /boot/device.hints made the Caps Lock LED to work in console again. Lena