From owner-freebsd-usb@FreeBSD.ORG Thu Jul 31 16:09:19 2014 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E5FB5E3; Thu, 31 Jul 2014 16:09:19 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1F3412449; Thu, 31 Jul 2014 16:09:18 +0000 (UTC) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 965D01FE027; Thu, 31 Jul 2014 18:09:09 +0200 (CEST) Message-ID: <53DA6A41.7000209@selasky.org> Date: Thu, 31 Jul 2014 18:09:37 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: sbruno@freebsd.org, freebsd-usb Subject: Re: Random issues with xhci References: <1406822044.1364.1.camel@bruno> In-Reply-To: <1406822044.1364.1.camel@bruno> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2014 16:09:19 -0000 On 07/31/14 17:54, Sean Bruno wrote: > xhci0@pci0:2:0:0: class=0x0c0330 card=0x84881043 chip=0x10421b21 > rev=0x00 hdr=0x00 > vendor = 'ASMedia Technology Inc.' > device = 'ASM1042 SuperSpeed USB Host Controller' > class = serial bus > subclass = USB > > > I can't quite ping down a specific test case with this usb controller. > I see that, sometimes, connecting devices to it or rebooting with > devices connected to it will fail with a constant device timeout > message. > > Any ideas on some better test cases with various bits of USB gear? > Hi, Does this happen with recent -current and -stable branches? --HPS