From owner-freebsd-hackers@FreeBSD.ORG Sat May 24 20:16:34 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 267D31065672 for ; Sat, 24 May 2008 20:16:34 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 2D57F8FC19 for ; Sat, 24 May 2008 20:16:34 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id E7BAE1CC033; Sat, 24 May 2008 13:16:33 -0700 (PDT) Date: Sat, 24 May 2008 13:16:33 -0700 From: Jeremy Chadwick To: Fraser Tweedale Message-ID: <20080524201633.GA81364@eos.sc1.parodius.com> References: <48378DA0.8040506@frase.id.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48378DA0.8040506@frase.id.au> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-hackers@freebsd.org, m_evmenkin@yahoo.com Subject: Re: temporary freezes when pressing capslock / numlock X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 May 2008 20:16:34 -0000 On Sat, May 24, 2008 at 01:38:08PM +1000, Fraser Tweedale wrote: > Since upgrading to RELENG_7_0 I was experiencing momentary freezes (of > about .5 seconds) whenever the capslock or numlock buttons were pressed. Let me guess -- you're using a USB keyboard. > The issue occurs both in console and in X, and for both ULE and 4BSD. The > problem was reproducible with USB keyboards only (ukbd); atkbd seems fine. > It also occurs when numlockx is used to set numlock on or off without > keyboard interaction. I figured as much. I hadn't checked numlock/capslock myself, but vcons switching also has that problem. Yes, it's semi-documented; see section "USB" below: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues For what it's worth, the systems I've confirmed the problem on are Intel and nForce 4. Meaning, the issue is not specific to a single chipset. > Interestingly, if you add enough keyboards, the problem vanishes, which led > me to kbdmux. Sure enough, removing device kbdmux from the kernel makes > the problem go away (at the expensive of some functionality of course, but > this is my current workaround). An interesting find! I'll add this to the details in the above wiki. I've also CC'd kbdmux's maintainer. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |