From owner-freebsd-usb@FreeBSD.ORG Wed Jun 6 16:53:39 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F0D7106564A for ; Wed, 6 Jun 2012 16:53:39 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.c2i.net [212.247.154.162]) by mx1.freebsd.org (Postfix) with ESMTP id 90B748FC14 for ; Wed, 6 Jun 2012 16:53:38 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.212.201] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe06.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 282076016; Wed, 06 Jun 2012 18:48:30 +0200 From: Hans Petter Selasky To: Mark Felder Date: Wed, 6 Jun 2012 18:47:52 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.0-STABLE; KDE/4.7.4; amd64; ; ) References: <201206061821.04306.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="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201206061847.52544.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:53:39 -0000 On Wednesday 06 June 2012 18:37:15 Mark Felder wrote: > On Wed, 06 Jun 2012 11:21:04 -0500, Hans Petter Selasky > > wrote: > > Attachments look OK. > > Are any other USB devices being used at the time this failure happens? > > No, the only things plugged in via USB are the keyboard, the mouse, and a > cable for the USB keyboard's built-in hub. No other devices are present. Then I see no reason for a software fault. You could dump all threads when this happen and see if some threads are stuck in xxx_drain() functions. It is very unlikely though. --HPS