From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Request for testing b43 & Broadcom 14e4:4315 cards for DMA ERRORs (Linux 3.0)
Date: Wed, 1 Jun 2011 11:17:37 +0200 [thread overview]
Message-ID: <BANLkTikMZ-HR73o+d=xge1Hb0izhqPYZKw@mail.gmail.com> (raw)
In-Reply-To: <20110601002941.1ab83b28@boulder.homenet>
W dniu 1 czerwca 2011 01:29 u?ytkownik Chris Vine
<chris@cvine.freeserve.co.uk> napisa?:
> On Mon, 30 May 2011 09:22:32 +0200
> Rafa? Mi?ecki <zajec5@gmail.com> wrote:
>> Hello everybody,
>>
>> I believe I've grabbed e-mails of all the people reporting DMA errors
>> on b43/bcm43xx mailing list.
>>
>> Short remind of the problem. When using b43 and LP-PHY card on some
>> specific machines you got:
>> b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000,
>> 0x00000000, 0x00000000, 0x00000000
>> b43-phy0: Controller RESET (DMA error) ...
>>
>> The workaround was to use PIO instead of DMA, or "modprobe wl &&
>> rmmod wl".
>>
>> I believe we've fixed that errors in Linux 3.0-rc1. Can you give it a
>> chance and report back?
>
> This deals with the fatal DMA errors on my machine. ?Well done.
Wohoo, that's great, thank you for info!
> However, fixing this bug reveals something else. ?After about 2 hours of
> streaming on MLB.TV I got this, apparently at random (but this is not a
> hard error: by disassociating from the AP and reassociating, the rest of
> the game played fine, and there was no need to load or unload modules):
>
> 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
This is known to happen when there is some high traffic happening.
Please use "b43 error under heavy load" thread to continue discussion
on this issue.
--
Rafa?
next prev parent reply other threads:[~2011-06-01 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 7:22 Request for testing b43 & Broadcom 14e4:4315 cards for DMA ERRORs (Linux 3.0) Rafał Miłecki
2011-05-30 7:45 ` Rafał Miłecki
2011-05-31 23:29 ` Chris Vine
2011-06-01 9:17 ` Rafał Miłecki [this message]
2011-06-02 3:40 ` William Bourque
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='BANLkTikMZ-HR73o+d=xge1Hb0izhqPYZKw@mail.gmail.com' \
--to=zajec5@gmail.com \
--cc=b43-dev@lists.infradead.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).