On Fri, Mar 17, 2000 at 11:04:55PM +0000, Alex Holden wrote:
> Hi, I just got an ezusb devel board so decided to try the usbstress
> package on it. It seems that quite a few of the tests fail...
>
> I'm using: linux-2.3.99-pre1, usbstress-0.3 (slightly hacked to download
> to the vid/pid of the board I have), an AN2123 board (ActiveWire), USB via
> an Intel 82371AB PIIX4 in an IBM Thinkpad 770, devel board plugged
> directly into root hub port.
>
> First I tried the usb-uhci.o driver:
>
> Control Echo test fails after some random number of transactions
> (typically between about 10 and 5000) with a message similar to:
> control_msg(0xc0, 0xe0, 48) failed with -1, errno Broken pipe (32)
> sequence 682
This seems to be a bug in the stress test itself. The error returned
is a STALL (no real error), but usbstress treats this as an error.
I've looked at it with the USB analyzer and except the STALL from the
Anchor there are no problems. IMHO a retry after the STALL would solve
the problem.
> Bulk Echo test appears to work okay.
>
> Asynchronous Bulk Echo test typically lists one or two errors at the
> beginning and appears to work fine after that. The errors look like:
> Receive error: status 0 actlen 608 rxseq 0x00f7ef05 expected seq
> 0x00000000
Smells like an initialization problem in the Anchor, but has nothing to do
with usb-uhci.
> Isochronous echo appears to fail totally. It gives a continual stream of
> messages similar to:
> Receive error: frame 15 status 0 actlen 288 rxseq 0x0228563f expected seq
> 0x0000092f
The isochronous test never worked for me.
--
Bye
Georg Acher, [EMAIL PROTECTED]
http://www.in.tum.de/~acher/
"Oh no, not again !" The bowl of petunias
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
