From owner-freebsd-usb@FreeBSD.ORG Fri Apr 11 06:06:04 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 84C11199 for ; Fri, 11 Apr 2014 06:06:04 +0000 (UTC) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::2]) (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 487C1184D for ; Fri, 11 Apr 2014 06:06:04 +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 2AA111FE027; Fri, 11 Apr 2014 08:06:01 +0200 (CEST) Message-ID: <5347867B.2040001@selasky.org> Date: Fri, 11 Apr 2014 08:06:51 +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: Erich Dollansky , Daniel O'Connor Subject: Re: USB 3 devices not reliably connecting at 5Gbps References: <20140411130729.489d3513@X220.alogt.com> In-Reply-To: <20140411130729.489d3513@X220.alogt.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-usb@freebsd.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2014 06:06:04 -0000 On 04/11/14 07:07, Erich Dollansky wrote: > It is either the error handling of FreeBSD or the quality of the > electrical signal. Hi, The port speed is decided by the hardware after port reset. Setting "sysctl hw.usb.uhub.debug=15" should reveal some more information about the port reset sequence. Please also ensure you are running 9/10-stable when testing, hence there are some minor fixes for XHCI every now and then. Try to collect some more logs from UHUB driver first. Compare bad and good case. --HPS