From: Michael Buesch <mb@bu3sch.de>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: John Daiker <daikerjohn@gmail.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Dave Young <hidave.darkstar@gmail.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
bcm43xx-dev@lists.berlios.de
Subject: Re: b43 dma error
Date: Tue, 8 Sep 2009 20:15:16 +0200 [thread overview]
Message-ID: <200909082015.17943.mb@bu3sch.de> (raw)
In-Reply-To: <69e28c910909081106p413b70d8u83a48a63943f123e@mail.gmail.com>
On Tuesday 08 September 2009 20:06:49 Gábor Stefanik wrote:
> On Tue, Sep 8, 2009 at 7:50 PM, John Daiker<daikerjohn@gmail.com> wrote:
> > On 09/08/2009 07:54 AM, Larry Finger wrote:
> >>
> >> Michael Buesch wrote:
> >>>
> >>> On Tuesday 08 September 2009 15:47:32 Dave Young wrote:
> >>>>
> >>>> I tested wireless-testing b43 driver, but got "Fatal DMA error"
> >>>> then the controller keep restarting...
> >>>>
> >>>> Please tell what I can provide or test, Thanks.
> >>>
> >>> Is this a regression? If so, please bisect.
> >>
> >> It is something specific to his system as I don't see anything like
> >> this. In addition, there are some users on the openSUSE forums that
> >> have implemented the latest compat-wireless and switched away from
> >> Broadcom wl to b43 on their LP PHY devices. So far, no complaints from
> >> them.
> >>
> >> Please reboot so that we see the ssb output as well. Use the command
> >>
> >> dmesg | egrep "ssb|b43"
> >>
> >> That way we will be able to see exactly what kind of device you have
> >> and what revisions are in it. AFAIK, the testing to date has been
> >> limited to Rev 1 PHYs and Rev 2 radios.
> >>
> >> Larry
> >>
> >
> > I can confirm the same issue. I have a HP Mini 1116NR with a Broadcom 4312.
> > Looks to be a PHY 1, Radio 2:
> >
> > --snip--
> > [ 456.165296] b43-phy0 debug: Found PHY: Analog 6, Type 5, Revision 1
> > [ 456.165364] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2062,
> > Revision 2
> > --snip--
> >
> > I've attached the output of 'dmesg | egrep "ssb|b43"', my kernel config, and
> > lspci -vv and lspci -nn
> >
> > Note: With the dmesg output, I had unloaded the b43 module previous
> > 'modprobe -r b43' and then loaded it again with debug output: 'modprobe b43
> > verbose=3'
> >
> > John Daiker
> >
>
> Again, please test with v478 or v5xx firmware.
>
This won't help. The DMA engine reports a descriptor error. That means the device
was unable to fetch the control data via DMA. Most of the time this indicates
a bug/failure/quirk in the platform DMA implementation.
--
Greetings, Michael.
next prev parent reply other threads:[~2009-09-08 18:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 13:47 b43 dma error Dave Young
2009-09-08 14:08 ` Gábor Stefanik
2009-09-09 7:54 ` Dave Young
2009-09-08 14:38 ` Michael Buesch
2009-09-08 14:54 ` Larry Finger
2009-09-08 17:50 ` John Daiker
2009-09-08 18:06 ` Gábor Stefanik
2009-09-08 18:15 ` Michael Buesch [this message]
2009-09-08 18:26 ` Larry Finger
2009-09-10 5:39 ` John Daiker
2009-09-10 6:24 ` John Daiker
2009-09-08 18:13 ` Michael Buesch
2009-09-08 18:26 ` John Daiker
2009-09-08 18:16 ` Larry Finger
2009-09-08 18:24 ` Gábor Stefanik
2009-09-08 18:30 ` Larry Finger
2009-09-08 18:32 ` Gábor Stefanik
2009-09-09 2:07 ` Larry Finger
2009-09-09 7:41 ` Markus Mueller
2009-09-08 18:32 ` John Daiker
2009-09-09 8:05 ` Dave Young
2009-09-09 8:02 ` Dave Young
2009-09-09 7:56 ` Dave Young
2009-09-10 1:28 ` Dave Young
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=200909082015.17943.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=daikerjohn@gmail.com \
--cc=hidave.darkstar@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netrolller.3d@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).