Date: Tue, 19 Mar 2013 08:09:20 +0100 From: Hans Petter Selasky <hps@bitfrost.no> To: "Ronald F. Guilmette" <rfg@tristatelogic.com> Cc: freebsd-usb@freebsd.org Subject: Re: Help please... More problems with USB 3.0 (kernel freezes) Message-ID: <51480F20.6060601@bitfrost.no> In-Reply-To: <2278.1363646352@server1.tristatelogic.com> References: <2278.1363646352@server1.tristatelogic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51480F20.6060601>