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: Sun, 14 Aug 2011 13:10:39 +0200 [thread overview]
Message-ID: <CACna6rxH8_9pc+vZizLyAkNCLK7-CmK6GZP-E2FKUfwR9uD8Xg@mail.gmail.com> (raw)
In-Reply-To: <20110601184931.499557c6@boulder.homenet>
Hey Chris,
2011/6/1 Chris Vine <chris@cvine.freeserve.co.uk>:
> 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?
next prev parent reply other threads:[~2011-08-14 11:10 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
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 [this message]
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=CACna6rxH8_9pc+vZizLyAkNCLK7-CmK6GZP-E2FKUfwR9uD8Xg@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).