From owner-freebsd-usb@FreeBSD.ORG Wed May 25 07:34:30 2011 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 4527F106566B for ; Wed, 25 May 2011 07:34:30 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.c2i.net [212.247.154.130]) by mx1.freebsd.org (Postfix) with ESMTP id C61B78FC15 for ; Wed, 25 May 2011 07:34:29 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.1 cv=upTJuTb3ngPPUUVVSPoyO7jwIWz3rzPtkQxI490l6Ks= c=1 sm=1 a=SvYTsOw2Z4kA:10 a=WQU8e4WWZSUA:10 a=8nJEP1OIZ-IA:10 a=CL8lFSKtTFcA:10 a=i9M/sDlu2rpZ9XS819oYzg==:17 a=ymuYxwlvqn1zWDPLLngA:9 a=wPNLvfGTeEIA:10 a=i9M/sDlu2rpZ9XS819oYzg==:117 Received: from [188.126.198.129] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe05.swip.net (CommuniGate Pro SMTP 5.2.19) with ESMTPA id 129782038; Wed, 25 May 2011 09:34:26 +0200 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Wed, 25 May 2011 09:33:13 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.2-STABLE; KDE/4.4.5; amd64; ; ) References: <91D613ED-CA0F-41BF-AD53-2FD42529DCF8@gsoft.com.au> In-Reply-To: <91D613ED-CA0F-41BF-AD53-2FD42529DCF8@gsoft.com.au> X-Face: *nPdTl_}RuAI6^PVpA02T?$%Xa^>@hE0uyUIoiha$pC:9TVgl.Oq, NwSZ4V"|LR.+tj}g5 %V,x^qOs~mnU3]Gn; cQLv&.N>TrxmSFf+p6(30a/{)KUU!s}w\IhQBj}[g}bj0I3^glmC( :AuzV9:.hESm-x4h240C`9=w MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201105250933.13255.hselasky@c2i.net> Cc: Subject: Re: USB driver locking 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, 25 May 2011 07:34:30 -0000 On Tuesday 24 May 2011 23:48:30 Daniel O'Connor wrote: > I find that my application has rare problems where it does not get a reply > from the micro to a control bus packet, or perhaps the micro doesn't > receive it (I need to add a sequence number or similar to my protocol to > try and detect it I think). There was a data toggle issue fixed with the EHCI recently, which triggers depending on hardware timing. Are you running the latest 8-stable or 9- current. There is also a new utility called usbdump, which can be used to figure out what is going on. --HPS