2011/8/14 Chris Vine <chris@xxxxxxxxxxxxxxxxxxxxx>: > On Sun, 14 Aug 2011 13:11:12 +0200 > Rafał Miłecki <zajec5@xxxxxxxxx> wrote: >> 2011/8/14 Rafał Miłecki <zajec5@xxxxxxxxx>: >> > 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 >> >> I meant "to 8": >> #define B43_RXRING_SLOTS 8 > > It is not an improvement. Different errors occur earlier (approx 100MB > of download), upon which the wireless disassociates from the network. > dmesg produces the output at the end of this post (with MAC addresses > munged). I didn't expect improvement, I tried to make it worse :P I though our problems may be coming from not-fast-enough reading RX ring. So you just made that ring even smaller to allow faster/easier errors. What do you mean by different errors? The only one I can see is "b43-phy0 ERROR: PHY transmission error". Do you mean that or something else? Did you post all the log you wanted to? Maybe missed beginning? -- 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
