From: David Laight > From: renevant@xxxxxxxxxxxx. > But there are also further issues I'm about to look at. > Short 'ping' requests work, but a 'netperf' tcp rr test with 8k blocks > (which probably generates sg transmits) fails generating some > 'TRB DMA ptr not part of current TD' errors. > I think I've seem that when a 'TRB error' is reported (when I was using the > wrong type of NOP). I'm about to investigate what is being errored here. In this case they happen when receive buffers cross 64k boundaries and so are split into two TRBS. The controller is generating one event for the 'short transfer' and a second for the last TRB - by which time the TD and URB have already been cleared up. While the trace isn't ideal, I don't think this is responsible for the whole thing locking up - which it does under some load patterns. I'm not sure how the Intel 'panther point' handles these split rx buffers when they contain a LINK TRB. The splits are definitely not aligned to any reasonably boundary. David -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
