From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Vine Date: Wed, 1 Jun 2011 19:09:29 +0100 Subject: b43 error under heavy load In-Reply-To: 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: <20110601190929.244c57ed@boulder.homenet> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= Cc: Larry Finger , wireless , Michael =?ISO-8859-1?B?QvxzY2g=?= , b43-dev On Wed, 1 Jun 2011 20:03:56 +0200 Rafa? Mi?ecki wrote: > 2011/6/1 Chris Vine : > > The one which failed caused the cessation of > > wireless traffic, and was accompanied by the debug log reports of > > out of order TX status earlier referred to, and with only one > > single report > > As I said, I don't really suspect any relation between full TX ring > and out of order problems anymore. > > But it won't hurt to ask just in case: > Did you see relation between this single "Stopped TX ring 1" and > massive out of order messages? Did out of order messages starter right > after "Stopped TX ring 1" one? The "Stopped TX ring 1" message was near the end (but not at the end) of the out of order messages. It was definitely not at the beginning of the out of order messages. Chris