From: "Rafał Miłecki" <zajec5@gmail.com>
To: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: "Larry Finger" <Larry.Finger@lwfinger.net>,
wireless <linux-wireless@vger.kernel.org>,
"Michael Büsch" <mb@bu3sch.de>,
b43-dev <b43-dev@lists.infradead.org>
Subject: b43 error under heavy load
Date: Wed, 1 Jun 2011 20:03:56 +0200 [thread overview]
Message-ID: <BANLkTi=Cm1o8HVqugC6JNooP8h+HpJ=aRQ@mail.gmail.com> (raw)
In-Reply-To: <20110601184931.499557c6@boulder.homenet>
2011/6/1 Chris Vine <chris@cvine.freeserve.co.uk>:
> 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?
next prev parent reply other threads:[~2011-06-01 18:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 18:41 b43 error under heavy load Larry Finger
2010-11-22 18:53 ` Michael Büsch
2010-11-22 19:12 ` Larry Finger
2011-05-10 5:08 ` Rafał Miłecki
2011-05-10 18:34 ` Larry Finger
2011-05-10 21:19 ` Rafał Miłecki
2011-06-01 9:23 ` Rafał Miłecki
2011-06-01 9:24 ` Rafał Miłecki
2011-06-01 10:48 ` Chris Vine
2011-06-01 10:56 ` Rafał Miłecki
2011-06-01 12:08 ` Chris Vine
2011-06-01 12:25 ` Rafał Miłecki
2011-06-01 15:01 ` Chris Vine
2011-06-01 15:42 ` Rafał Miłecki
2011-06-01 17:49 ` Chris Vine
2011-06-01 18:03 ` Rafał Miłecki [this message]
2011-06-01 18:09 ` Chris Vine
2011-06-01 18:10 ` Rafał Miłecki
2011-07-26 9:28 ` Chris Vine
2011-08-14 11:10 ` Rafał Miłecki
2011-08-14 11:11 ` Rafał Miłecki
2011-08-14 20:46 ` Chris Vine
2011-08-14 20:54 ` Rafał Miłecki
2011-08-14 21:19 ` Chris Vine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=Cm1o8HVqugC6JNooP8h+HpJ=aRQ@mail.gmail.com' \
--to=zajec5@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=chris@cvine.freeserve.co.uk \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).