From: Nathan Schulte <reklipz@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: Make b43 driver fall back gracefully to PIO mode after fatal DMA errors
Date: Sat, 27 Feb 2010 20:12:54 +0000 (UTC) [thread overview]
Message-ID: <loom.20100227T210822-109@post.gmane.org> (raw)
In-Reply-To: 201002271836.04673.mb@bu3sch.de
Michael Buesch <mb@...> writes:
> Please check if the following patch makes any difference.
> Also please show me the result of the printks.
I applied your modifications to 2.6.33 vanilla and they did not resolve the
issue for me. My logs are as follows:
[ 63.831811] b43-pci-bridge 0000:06:00.0: PCI INT A -> GSI 19 (level, low) ->
IRQ 19
[ 63.832210] b43-pci-bridge 0000:06:00.0: setting latency timer to 64
[ 63.840750] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x16, vendor 0x4243)
[ 63.840776] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0F, vendor 0x4243)
[ 63.840800] ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x0A, vendor 0x4243)
[ 63.840823] ssb: Core 3 found: PCI-E (cc 0x820, rev 0x09, vendor 0x4243)
[ 63.848426] PMU res init 4312/4322
[ 63.865510] ssb: Sonics Silicon Backplane found on PCI device 0000:06:00.0
[ 63.891491] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
[ 63.920485] phy0: Selected rate control algorithm 'minstrel'
[ 63.923025] Registered led device: b43-phy0::tx
[ 63.923624] Registered led device: b43-phy0::rx
[ 63.924105] Registered led device: b43-phy0::radio
[ 63.924749] Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]
[ 68.014700] b43 ssb0:0: firmware: requesting b43/ucode15.fw
[ 68.101055] b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw
[ 68.116067] b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
[ 68.359461] b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
[ 68.363765] Set LDO 4312
[ 68.363878] Set LDO paref
[ 69.775354] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 70.363498] b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000,
0x00000000, 0x00000000, 0x00000000, 0x00000000
[ 70.363514] b43-phy0 ERROR: This device does not support DMA on your system.
Please use PIO instead.
[ 70.363522] b43-phy0 ERROR: CONFIG_B43_FORCE_PIO must be set in your kernel
configuration.
[ 77.437270] wlan0: direct probe to AP 00:1c:f0:e8:e2:13 (try 1)
[ 77.637152] wlan0: direct probe to AP 00:1c:f0:e8:e2:13 (try 2)
[ 77.837166] wlan0: direct probe to AP 00:1c:f0:e8:e2:13 (try 3)
[ 78.037074] wlan0: direct probe to AP 00:1c:f0:e8:e2:13 timed out
[ 101.047357] b43-pci-bridge 0000:06:00.0: PCI INT A disabled
-Nate
next prev parent reply other threads:[~2010-02-27 20:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.00.1002261034140.4513@localhost.localdomain>
2010-02-26 19:09 ` Make b43 driver fall back gracefully to PIO mode after fatal DMA errors Larry Finger
2010-02-26 19:13 ` Linus Torvalds
2010-02-26 20:06 ` Linus Torvalds
2010-02-26 20:09 ` Gábor Stefanik
2010-02-26 20:50 ` Linus Torvalds
2010-02-26 21:01 ` Larry Finger
2010-02-26 21:45 ` Linus Torvalds
2010-02-26 21:50 ` Linus Torvalds
2010-02-26 22:08 ` Gábor Stefanik
2010-02-26 22:46 ` Linus Torvalds
2010-02-26 22:54 ` Gábor Stefanik
2010-02-27 15:04 ` Michael Buesch
2010-02-27 14:59 ` Michael Buesch
2010-02-27 18:31 ` Linus Torvalds
2010-02-27 18:51 ` Michael Buesch
2010-02-26 19:59 ` Michael Buesch
2010-02-26 20:07 ` Linus Torvalds
2010-02-26 20:20 ` Michael Buesch
2010-02-26 20:33 ` Linus Torvalds
2010-02-26 20:42 ` Linus Torvalds
2010-02-27 14:44 ` Michael Buesch
2010-02-27 14:49 ` Michael Buesch
2010-02-27 17:36 ` Michael Buesch
2010-02-27 20:12 ` Nathan Schulte [this message]
2010-02-27 21:08 ` Linus Torvalds
2010-02-27 21:43 ` Michael Buesch
2010-02-27 22:12 ` Linus Torvalds
2010-02-26 20:46 Nathan Schulte
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=loom.20100227T210822-109@post.gmane.org \
--to=reklipz@gmail.com \
--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).