From owner-freebsd-current@FreeBSD.ORG Sat Sep 5 16:47:38 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88EF2106566C for ; Sat, 5 Sep 2009 16:47:38 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 9D5028FC13 for ; Sat, 5 Sep 2009 16:47:37 +0000 (UTC) Received: (qmail invoked by alias); 05 Sep 2009 16:47:35 -0000 Received: from 85-127-83-116.dynamic.xdsl-line.inode.at (EHLO taxman.pepperland) [85.127.83.116] by mail.gmx.net (mp062) with SMTP; 05 Sep 2009 18:47:35 +0200 X-Authenticated: #16703784 X-Provags-ID: V01U2FsdGVkX19HN0YicvVHo0uViwkm6hMOepsB4SQV0sMtHaPvqQ iJC8/vKE0qMCKj From: Stefan Ehmann To: Hans Petter Selasky Date: Sat, 5 Sep 2009 18:47:32 +0200 User-Agent: KMail/1.12.1 (FreeBSD/8.0-BETA4; KDE/4.3.1; i386; ; ) References: <200909051632.55580.shoesoft@gmx.net> <200909051802.37902.hselasky@c2i.net> In-Reply-To: <200909051802.37902.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200909051847.32946.shoesoft@gmx.net> X-Y-GMX-Trusted: 0 X-FuHaFi: 0.53 Cc: freebsd-current@freebsd.org Subject: Re: ukbd: short freeze when activating LEDs 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: Sat, 05 Sep 2009 16:47:38 -0000 On Saturday 05 September 2009 18:02:37 you wrote: > On Saturday 05 September 2009 16:32:55 Stefan Ehmann wrote: > > Whenever I press capslock/numlock, the system shortly (< 0.5 ms) freezes. > > How did you measure this? The mouse is not responding and sound also stops during that period. It's probably much shorter, more likely 0.1-0.2ms. > Are you able to figure out why it is hanging? > > Has this got anything to do with BIOS or microcode running on the CPU? No idea. top shows > 95% interrupt if I'm on the console, in xorg the cpu goes to system. Interestingly, the number of interrupts displayed by systat is very moderate (if I just move the mouse, it's much higher) > USB keyboard LEDs are set asynchronously. It should not block like you > explain. The keyboard works fine on my notebook. I think the problem is the USB controller on my PC, not the keyboard driver. dmesg reports it as uhci0: port 0xb400-0xb41f at device 16.0 on pci0 uhci0: [ITHREAD] uhci0: LegSup = 0x003a usbus0: on uhci0 Historically, I've always had lots of trouble with USB on this particular PC. With the old USB code, I've got lots of issues. scanner didn't work at all, sometimes even problems with basic things like umass. With new USB things are much better, but not always perfect. If there's no easy way to debug, it's probably not worth the hassle. The PC is nearing the end of its life-time anyway. -- Thanks, Stefan