From owner-freebsd-hardware@FreeBSD.ORG Wed Jan 19 15:04:38 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59B2A106566C; Wed, 19 Jan 2011 15:04:38 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.c2i.net [212.247.154.2]) by mx1.freebsd.org (Postfix) with ESMTP id 787808FC19; Wed, 19 Jan 2011 15:04:37 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=A4HDTGXxjEDC1UuJ6rl8GMp0zaXu4XgXPL1dbujgs48= c=1 sm=1 a=XTUqBGVsqOAA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=l_Y0fWRYadet1y9gK_0A:9 a=RwtVsJ-TxpBShPIPgmwA:7 a=RmbvT1dXn1wWusJJl8Vx2HMxa8oA:4 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 76974602; Wed, 19 Jan 2011 16:04:33 +0100 From: Hans Petter Selasky To: freebsd-hardware@freebsd.org Date: Wed, 19 Jan 2011 16:04:35 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.2-PRERELEASE; KDE/4.4.5; amd64; ; ) References: <4D3608BD.7010604@comcast.net> <4D36EB91.1050406@comcast.net> <4D36FA7D.1030503@comcast.net> In-Reply-To: <4D36FA7D.1030503@comcast.net> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201101191604.35867.hselasky@c2i.net> Cc: freebsd-stable , Steve Polyack , Jeremy Chadwick , User Questions Subject: Re: Keyboard repeat issues with Dell Optiplex 980s X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2011 15:04:38 -0000 On Wednesday 19 January 2011 15:51:41 Steve Polyack wrote: > On 01/19/11 08:48, Steve Polyack wrote: > > On 1/18/2011 5:56 PM, Jeremy Chadwick wrote: > >> On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: > >>> We've recently upgraded a few desktop workstations from Dell > >>> Optiplex 960s to Optiplex 980s. We were running FreeBSD > >>> 8.1-RELEASE. The migration was performed by simply swapping the > >>> drives into the new systems. Immediately after switching people > >>> over, they all began to report bizarre keyboard issues - things like > >>> infinite key repeats (letters, numbers, "enter") for keys they did > >>> not hold down. The key repeats continue indefinitely until another > >>> key is pressed. Occasionally, even mouse input will trigger similar > >>> infinite keyboard input repetition. In addition to the repeat > >>> issue, sometimes physical key-presses are not registered by FreeBSD, > >>> leading to typos and angry developers. > >>> > >>> We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these > >>> systems, and the issue persists. Because of the observed behavior, > >>> I'm thinking that this is due to new hardware in the 980s which > >>> isn't timing or handling interrupts correctly under the FreeBSD > >>> kernel. > >>> > >>> Looking at a 'pciconf -lvb' from each system, I noticed that the 980 > >>> has two USB controllers which probe under ehci(4), while the 960 > >>> (which does not exhibit this problem), enumerates six uhci(4) > >>> controllers and two ehci(4) controllers. To cut to the chase here, > >>> the 960 users' keyboards probe under a USB1.0 uhci(4), while the > >>> 980s only have ehci(4) devices to attach to. > >>> > >>> So, I guess what I'm asking is - has anyone else seen any keyboard > >>> repeat or other USB craziness with ehci(4) ports or otherwise Intel > >>> PCH controllers? Any fellow Optiplex 980 users? I'd be more than > >>> happy to provide pciconf or other output if requested. > >> > >> Try adding the following to /boot/loader.conf then reboot and see if > >> the "excessive repeat" behaviour changes: > >> > >> hint.kbdmux.0.disabled="1" > >> > >> It would also help if you would state exactly what brand/model of > >> keyboard is used. Yes, believe it or not, it matters. dmesg output > >> would be helpful in this case. > > > > The keyboard is also a Dell model - model KB1421, or listed as "Dell > > QuiteKey Keyboard" under dmesg. The same keyboard does not exhibit > > the strange behavior when used with the older model of tower (Optiplex > > 960). > > > > I'll reboot today with the loader.conf hint you provided. I'll let > > > > you guys know if it helps. Thanks! > > The problem still exists with the kbdmux.0.disabled hint. It definitely > took effect, as there is no longer a /dev/kbdmux0, and dmesg lists the > refusal to register the kbdmux module. Any other ideas? We've tried > playing with the hw.usb.ehci.lostinrbug and hw.usb.ehci.no_hs sysctls, > but they don't make a difference either. > > Looking at the ehci(4) man page, this sticks out at me: > BUGS > The driver is not finished and is quite buggy. > > There is currently no support for isochronous transfers. For FreeBSD 8+ this is not true. Probably the manpage has not been updated. Hence you are seeing a different number of UHCI controllers, this looks like an ACPI problem. USB keyboards usually require a UHCI to enumerate. The EHCI can only enumerate High Speed devices. --HPS