Hey Chris, 2011/6/1 Chris Vine <chris@xxxxxxxxxxxxxxxxxxxxx>: > Summary: Traffic sent up from the broadcom wireless device generates > copious reports of "Stopped TX ring 1" but always carries on with its > job and stays up, although its traffic is slower than on received > packets. Received traffic on the other hand reports no errors until > the spate of "Out of order TX status report on DMA ring 1" errors > occurs, which seems to happen at random (albeit accompanied on my > failed transfer by a single "Stopped TX ring 1" log entry), and when it > does happen brings the wireless link to a halt. Wireless traffic can be > restarted simply by reassociating with the AP. So it seems heavy load of RX can cause problems with TX. I just though of one another reason, could you test one more thing for me? Edit drivers/net/wireless/b43/dma.h and change define from value 64 to in the line: #define B43_RXRING_SLOTS 64 Can you get "Out of order TX" much more easily after such a change? -- Rafał -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html