From: "Rafał Miłecki" <zajec5@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
Juan Carlos Romero <juancarlos.romero@gmail.com>
Cc: "Michael Büsch" <mb@bu3sch.de>,
b43-dev <b43-dev@lists.infradead.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: b43 error under heavy load
Date: Tue, 10 May 2011 07:08:20 +0200 [thread overview]
Message-ID: <BANLkTimjRA5CsSDp_+LrGq8PNgaR4JFD=w@mail.gmail.com> (raw)
In-Reply-To: <4CEAC095.7020706@lwfinger.net>
2010/11/22 Larry Finger <Larry.Finger@lwfinger.net>:
> On 11/22/2010 12:53 PM, Michael B?sch wrote:
>> 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.
>
> Thanks. I'll see if I can figure out a way for the driver to recover more
> gracefully. In the meantime, I will be dumping the entire TX status struct to
> see if that helps in seeing what is wrong.
Larry, did you try debugging this? Juan noticed this issue on his
14e4:4315 as well.
[ 854.826369] b43-phy0 debug: Out of order TX status report on DMA
ring 1. Expected 74, but got 54
[ 854.827348] b43-phy0 debug: Out of order TX status report on DMA
ring 1. Expected 74, but got 56
[ 854.828080] b43-phy0 debug: Out of order TX status report on DMA
ring 1. Expected 74, but got 58
[ 854.831431] b43-phy0 debug: Out of order TX status report on DMA
ring 1. Expected 74, but got 60
[ 854.831453] b43-phy0 debug: Out of order TX status report on DMA
ring 1. Expected 74, but got 62
[ 854.832440] b43-phy0 debug: Out of order TX status report on DMA
ring 1. Expected 74, but got 64
[ 854.833836] b43-phy0 debug: Out of order TX status report on DMA
ring 1. Expected 74, but got 66
[ 854.834567] b43-phy0 debug: Out of order TX status report on DMA
ring 1. Expected 74, but got 68
[ 854.834588] b43-phy0 debug: Out of order TX status report on DMA
ring 1. Expected 74, but got 70
[ 854.835378] b43-phy0 debug: Out of order TX status report on DMA
ring 1. Expected 74, but got 72
Connection is lost, reloading of the driver is needer.
--
Rafa?
next prev parent reply other threads:[~2011-05-10 5:08 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 [this message]
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='BANLkTimjRA5CsSDp_+LrGq8PNgaR4JFD=w@mail.gmail.com' \
--to=zajec5@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=juancarlos.romero@gmail.com \
--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).