From owner-freebsd-usb@FreeBSD.ORG Tue Mar 19 07:08:10 2013 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 88D04129 for ; Tue, 19 Mar 2013 07:08:10 +0000 (UTC) (envelope-from hps@bitfrost.no) Received: from mta.bitpro.no (mta.bitpro.no [92.42.64.202]) by mx1.freebsd.org (Postfix) with ESMTP id 2CF0D81C for ; Tue, 19 Mar 2013 07:08:09 +0000 (UTC) Received: from mail.bitfrost.no (mail.bitfrost.no [46.29.221.36]) by mta.bitpro.no (Postfix) with ESMTP id DD3BD7A120; Tue, 19 Mar 2013 08:08:07 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at bitfrost.no Received: from laptop015.hselasky.homeunix.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: hanspetter) by mail.bitfrost.no (Postfix) with ESMTPSA id 1490920CD2; Tue, 19 Mar 2013 08:08:05 +0100 (CET) Message-ID: <51480F20.6060601@bitfrost.no> Date: Tue, 19 Mar 2013 08:09:20 +0100 From: Hans Petter Selasky Organization: Bitfrost A/S MIME-Version: 1.0 To: "Ronald F. Guilmette" Subject: Re: Help please... More problems with USB 3.0 (kernel freezes) References: <2278.1363646352@server1.tristatelogic.com> In-Reply-To: <2278.1363646352@server1.tristatelogic.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.14 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Mar 2013 07:08:10 -0000 Hi, On 03/18/13 23:39, Ronald F. Guilmette wrote: > 1) What is the best way to debug this? I have seen HPS suggest to others > with USB problems that they either (a) use the usbdump(8) command to get > more info about the problems or else (b) compile and install a new kernel > in which the option USB_DEBUG has been defined. Which should I do, and > how may I interpret the results in either case? I see two kind of hangs: 1) IRQ is spinning 2) DMA is going wild in the memory In sys/dev/usb/controller/xhci.c there are debug prints, DPRINTF() and DPRINTFN(). You probably want to have a print in the interrupt routine. Just search for "interrupt". Debug level is controlled via sysctl hw.usb.xhci.debug=X > > 2) What are the command timeouts set to in the XHCI driver and how can I > increase them? (Perhaps my card is just barely meeting the published > USB standard timing specs, and just need a tiny bit more time?) The XHCI is an active USB controller. That means many high-level USB commands must be fed into it using separate commands. These have nothing to do with what is transferred to the USB device. > > 3) What exactly is "hw.usb.no_cs_fail" ? This just instructs the system to not re-enumerate the device on repeated clear stall failures. > > 4) What exactly is "hw.usb.u3g.debug" ? That's debugging for u3g driver module. > > 5) What exactly is "diveration" ? Where did you find this? --HPS