Return-path: Received: from mail-qw0-f46.google.com ([209.85.216.46]:39555 "EHLO mail-qw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752763Ab1FASD5 convert rfc822-to-8bit (ORCPT ); Wed, 1 Jun 2011 14:03:57 -0400 Received: by qwk3 with SMTP id 3so29856qwk.19 for ; Wed, 01 Jun 2011 11:03:56 -0700 (PDT) MIME-Version: 1.0 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> Date: Wed, 1 Jun 2011 20:03:56 +0200 Message-ID: (sfid-20110601_200400_849677_B3B60A01) Subject: Re: b43 error under heavy load From: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= To: Chris Vine Cc: Larry Finger , wireless , =?UTF-8?Q?Michael_B=C3=BCsch?= , b43-dev Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: 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? -- RafaƂ