From: Chris Vine <chris@cvine.freeserve.co.uk>
To: "Rafał Miłecki" <zajec5@gmail.com>
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 22:19:58 +0100 [thread overview]
Message-ID: <20110814221958.6e7a4264@boulder.homenet> (raw)
In-Reply-To: <CACna6ry4LxUAo-s2ViKHH8V1n5Nsc9-Oora3Dazz67jftfX9oA@mail.gmail.com>
On Sun, 14 Aug 2011 22:54:20 +0200
Rafa? Mi?ecki <zajec5@gmail.com> wrote:
> I didn't expect improvement, I tried to make it worse :P I though our
> problems may be coming from not-fast-enough reading RX ring. So you
> just made that ring even smaller to allow faster/easier errors.
>
> What do you mean by different errors? The only one I can see is
> "b43-phy0 ERROR: PHY transmission error". Do you mean that or
> something else? Did you post all the log you wanted to? Maybe missed
> beginning?
That's it.
On your question "what do you mean by different errors", I mean the
reported errors are different. Without that patch the reported error
is:
b43-phy0 debug: TX-status contains invalid cookie: 0x0DCE
b43-phy0 debug: Out of order TX status report on DMA ring 1. Expected 74, but got 76
b43-phy0 debug: Out of order TX status report on DMA ring 1. Expected 74, but got 78
... and so on.
Chris
prev parent reply other threads:[~2011-08-14 21:19 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
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 [this message]
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=20110814221958.6e7a4264@boulder.homenet \
--to=chris@cvine.freeserve.co.uk \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=zajec5@gmail.com \
/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).