Thread (6 messages) 6 messages, 4 authors, 2014-01-30

RE: Help testing for USB ethernet/xHCI regression

From: David Laight <hidden>
Date: 2014-01-30 10:03:30

From: Sarah Sharp
On Tue, Jan 28, 2014 at 11:30:51PM -0500, Mark Lord wrote:
quoted
On 14-01-28 03:30 PM, Sarah Sharp wrote:
..
quoted
Can you please pull this branch, which contains a 3.13 kernel with
David's patch reverted, and test whether your USB ethernet device works
or fails?
Fails.  dmesg log attached.
It's funny, because there's certainly data transferred over endpoint
0x82, even though there were link TRBs in the middle of transfers.  Did
the "untransferred" messages stop when the device stopped working, or
did they continue?
What I saw was that the USB transfers continued, but the ethernet
transmits stopped.
This rather changes the packets generated by TCP at both ends.
The effect can be seen in the timestamps (etc) in the USB trace.
There are still tx and rx packets, after a while they'll only
happen on ever-increasing timeouts.

That was the point where I wrote the NOP patch just to see if
it made a difference. I didn't really expect one!

I think that the LINK trb splits a 1k usb message in two.
This well and truly confuses the ethernet part of the ax88179_178a
hardware to the point where it doesn't even reset itself on the
next sub 1k message.

It might be that other targets (eg the smsx95xx) is more resilient
and only loses the single packet - which won't be immediately obvious.

	David
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help