From owner-freebsd-usb@FreeBSD.ORG Wed Jun 6 16:21:43 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D13DF1065680 for ; Wed, 6 Jun 2012 16:21:43 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe09.c2i.net [212.247.155.2]) by mx1.freebsd.org (Postfix) with ESMTP id 5F6218FC20 for ; Wed, 6 Jun 2012 16:21:43 +0000 (UTC) X-T2-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED Received: from [176.74.212.201] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe09.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 108755874; Wed, 06 Jun 2012 18:21:41 +0200 From: Hans Petter Selasky To: Mark Felder Date: Wed, 6 Jun 2012 18:21:04 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.0-STABLE; KDE/4.7.4; amd64; ; ) References: <201206061758.32133.hselasky@c2i.net> In-Reply-To: X-Face: 'mmZ:T{)),Oru^0c+/}w'`gU1$ubmG?lp!=R4Wy\ELYo2)@'UZ24N@d2+AyewRX}mAm; Yp |U[@, _z/([?1bCfM{_"B<.J>mICJCHAzzGHI{y7{%JVz%R~yJHIji`y>Y}k1C4TfysrsUI -%GU9V5]iUZF&nRn9mJ'?&>O MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201206061821.04306.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org Subject: Re: usb power output issues X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2012 16:21:43 -0000 On Wednesday 06 June 2012 18:05:56 Mark Felder wrote: > On Wed, 06 Jun 2012 10:58:32 -0500, Hans Petter Selasky > > wrote: > > Hi, > > > > Can you try pressing CTRL+ALT+F1, then CTRL+ALT+F9. Sometimes I see > > something > > similar, and switching back and forth between the console helps. > > The keyboard goes *completely* dead, so even switching VTs like that isn't > possible. > > I worked around the issue by plugging in a powered USB hub. So currently > if I plug in my keyboard directly, it won't work. > > > You can try to get dmesg, and also run: > > > > usbconfig dump_device_desc dump_curr_config_desc > > > > If your device times out on the command above, something is wrong in > > USB. Else > > it is a problem in the interaction with X11. > > It doesn't appear to time out when I collect that info, and it can't be an > X11 issue because I can kill X11 completely and the problem persists. > > > FYI: CAPS-LOCK-LED and NUM-LOCK-LED are software controlled by the USB > > stack. > > I suspected as much. > > > See attached. Attachments look OK. Are any other USB devices being used at the time this failure happens? --HPS