Hello Peter, On 15/11/14(Sat) 15:29, Peter N. M. Hansteen wrote: > and I just noticed that the supplied dmesg did not in fact capture the NULL > xfer pointer messages, > but here's one that does, from a few minutes later running the same snapshot. > > The failure pattern isn't entirely consistent - the urtwn device will > maintain link for some minutes, > then timeout, sometimes with the NULL xfer pointer message, but not always. > Also, about 50% of the time > it's possible to get the link back just by rerunning netstart for urtwn0, at > other times detaching, > reattaching and re-running netstart urtwn0 is needed in order to get back on > line. Also, when the device > does work, its throughput is significantly worse than earlier (guesstimate > 10% of previous throughput > although pinging the gateway yields wildly fluctuating round trip times).
Various people reported a similar problem with an xHCI 1.0 controller and urtwn(4). I am unable to reproduce the problem with the various controllers I have at my disposition here. I'll try to get access to more hardware in order to track that down, unless somebody else find the issue before me.
