Date: Wed, 25 May 2011 09:51:53 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: "Daniel O'Connor" <doconnor@gsoft.com.au> Cc: freebsd-usb@freebsd.org Subject: Re: USB driver locking Message-ID: <201105250951.53498.hselasky@c2i.net> In-Reply-To: <99FAD844-DDC8-4C3D-8117-0887CB893728@gsoft.com.au> References: <91D613ED-CA0F-41BF-AD53-2FD42529DCF8@gsoft.com.au> <201105250933.13255.hselasky@c2i.net> <99FAD844-DDC8-4C3D-8117-0887CB893728@gsoft.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 25 May 2011 09:47:50 Daniel O'Connor wrote: > On 25/05/2011, at 9:33, Hans Petter Selasky wrote: > > 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- > > This one? > http://svnweb.freebsd.org/base?view=revision&revision=219845 Yes. > I have that as I am running 219926 > > > current. There is also a new utility called usbdump, which can be used to > > figure out what is going on. > > I am running 9-current (in production for my sins..) > > usbdump is useful but consumes too much CPU at my data rate :( You probably need an USB analyzer to figure out the real problem. Have you tried to start usbdump only once the problem happens? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201105250951.53498.hselasky>