From owner-freebsd-usb@FreeBSD.ORG Wed Jun 6 17:26:31 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 E7C771065670 for ; Wed, 6 Jun 2012 17:26:31 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id BC4E38FC16 for ; Wed, 6 Jun 2012 17:26:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Cc:Date:References:Subject:To:Content-Type; bh=rmCznnWlkXR8F6SYzUoht6H54vM5reoRiFzQOODISCs=; b=cAlx5VD0K2n0JfVPkJWjvGNpFqyQp7Rx1rLrLcqZVf36l/LiJAs7hTiYlj+4ms8M7pBdyyk/xxCQMDQsVooLtwarn+P5mUVh9uN9iR89QhfWNJiUUUfau0GY+sozR4hZ; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.77 (FreeBSD)) (envelope-from ) id 1ScK06-000816-Ch; Wed, 06 Jun 2012 12:26:31 -0500 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpa id 1339003584-26372-26371/5/44; Wed, 6 Jun 2012 17:26:24 +0000 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-usb@freebsd.org References: <201206061821.04306.hselasky@c2i.net> <201206061847.52544.hselasky@c2i.net> Date: Wed, 6 Jun 2012 12:26:24 -0500 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: <201206061847.52544.hselasky@c2i.net> User-Agent: Opera Mail/11.64 (FreeBSD) X-SA-Score: -1.5 Cc: 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 17:26:32 -0000 On Wed, 06 Jun 2012 11:47:52 -0500, Hans Petter Selasky wrote: > 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. I'll assume this is a hardware bug for now. Thanks for looking into it for me!