From: "Michael Büsch" <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: b43-dev <b43-dev@lists.infradead.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: b43 error under heavy load
Date: Mon, 22 Nov 2010 19:53:02 +0100 [thread overview]
Message-ID: <1290451982.20888.2.camel@maggie> (raw)
In-Reply-To: <4CEAB969.20702@lwfinger.net> (sfid-20101122_194209_226222_FFFFFFFFA98AFC1F)
On Mon, 2010-11-22 at 12:41 -0600, Larry Finger wrote:
> Under heavy load with multiple streams, I'm getting errors from my BCM4312
> (14e4:4315) device as follows:
>
> b43-phy0 debug: TX-status contains invalid cookie: 0x0D4D
> 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 continues).
>
> Clearly that cookie is garbage as it has a slot number of 0. Any suggestions on
> diagnostic information that I could dump to help debug this?
I think that probably is a firmware or hardware bug. The affected
kernel code was not changed in years, as far as I know.
--
Greetings Michael.
next prev parent reply other threads:[~2010-11-22 18:53 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 [this message]
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
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=1290451982.20888.2.camel@maggie \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
/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).