From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= Date: Sun, 14 Aug 2011 13:10:39 +0200 Subject: b43 error under heavy load In-Reply-To: <20110601184931.499557c6@boulder.homenet> References: <4CEAB969.20702@lwfinger.net> <1290451982.20888.2.camel@maggie> <4CEAC095.7020706@lwfinger.net> <4DC9853A.1090508@lwfinger.net> <20110601114839.433ae42d@boulder.homenet> <20110601130842.077da1c3@boulder.homenet> <20110601160101.75e30b3d@boulder.homenet> <20110601184931.499557c6@boulder.homenet> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Chris Vine Cc: Larry Finger , wireless , =?UTF-8?Q?Michael_B=C3=BCsch?= , b43-dev Hey Chris, 2011/6/1 Chris Vine : > 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?