On 5/25/11 12:54 AM, Daniel O'Connor wrote:
On 25/05/2011, at 9:51, Hans Petter Selasky wrote:
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?
I'll try and cook something up to run it when the problem happens.
hans and Daniel,
I suggest you put some KTR points into the driver and trace some
crucial information using that.
it is capable of keeping up with very fast stuff with small disturbance.
Just the basic info.. you get 5 x 64 bit arguments. (or is it 6?)
which is enough space for quite a bit of stuff to be logged.
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
_______________________________________________
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
_______________________________________________
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
