On Sun, Oct 25, 2009 at 7:17 PM, Linus Torvalds
<torva...@linux-foundation.org> wrote:
>
> Ok, so I got myself (or rather, Patricia) a new Dell 11 inspiron laptop,
> and everything seems to work, except for the wireless. It's a Broadcom
> BCM4312b/g LP-PHY.
>
> In fact, even the wireless works at least to _some_ degree, because I saw
> the wireless networks listed once (but I can't seem to recreate that now),
> but:
>
>  - I get a _lot_ of noise in dmesg:
>
>        b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 
> 0x00000000, 0x00000000, 0x00000000
>        b43-phy0: Controller RESET (DMA error) ...
>        b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
>        b43-phy0: Controller restarted
>
>  - the 'phy0' kernel thread seems to spend all its time presumably doing
>   that firmware reloading (looks like 20% CPU time in top)
>
>  - the wireless doesn't seem to actually ever succeed in connecting even
>   the one time it saw something, and 'rmmod b43' just hangs.
>
> The network I'm trying to connect to is just a random 128-bit WEP thing.
> But while I once got far enough to see it (I think that was with the
> 4.150.10.5 firmware - I started out using the wrong one by mistake), now I
> can't even see the networks, so I doubt that matters.
>
> Maybe it's all as simple as me just having the wrong firmware version or
> something. But it's the version documented at
>
>        http://linuxwireless.org/en/users/Drivers/b43
>
> for the LP-PHY case.
>
> This is with current -git (v2.6.32-rc5-81-g964fe08), and lspci reports
>
>        08:00.0 0280: 14e4:4315 (rev 01)
>                Subsystem: 1028:000c
>                Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
> ParErr- Stepping- SERR- FastB2B- DisINTx-
>                Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
> <TAbort- <MAbort- >SERR- <PERR- INTx-
>                Latency: 0, Cache Line Size: 64 bytes
>                Interrupt: pin A routed to IRQ 17
>                Region 0: Memory at f0600000 (64-bit, non-prefetchable) 
> [size=16K]
>                Capabilities: <access denied>
>                Kernel driver in use: b43-pci-bridge
>                Kernel modules: ssb
>        00: e4 14 15 43 06 00 10 00 01 00 80 02 10 00 00 00
>        10: 04 00 60 f0 00 00 00 00 00 00 00 00 00 00 00 00
>        20: 00 00 00 00 00 00 00 00 00 00 00 00 28 10 0c 00
>        30: 00 00 00 00 40 00 00 00 00 00 00 00 0a 01 00 00
>
> with dmesg saying
>
>        b43-pci-bridge 0000:08:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
>        b43-pci-bridge 0000:08:00.0: setting latency timer to 64
>        ...
>        cfg80211: Calling CRDA to update world regulatory domain
>        ...
>        cfg80211: World regulatory domain updated:
>                (start_freq - end_freq @ bandwidth), (max_antenna_gain, 
> max_eirp)
>                (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>                (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
>                (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
>                (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>                (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>        b43-phy0: Broadcom 4312 WLAN found (core revision 15)
>        ...
>        phy0: Selected rate control algorithm 'minstrel'
>        Registered led device: b43-phy0::tx
>        Registered led device: b43-phy0::rx
>        Registered led device: b43-phy0::radio
>        Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ]
>        ...
>        cfg80211: Calling CRDA for country: US
>        cfg80211: Regulatory domain changed to country: US
>                (start_freq - end_freq @ bandwidth), (max_antenna_gain, 
> max_eirp)
>                (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
>                (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
>                (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>                (5490000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
>                (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
>        ...
>        b43 ssb0:0: firmware: requesting b43/ucode15.fw
>        b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw
>        b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw
>        b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
>        ...
>        b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 
> 0x00000000, 0x00000000, 0x00000000
>        b43-phy0: Controller RESET (DMA error) ...
>        b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
>        b43-phy0 ERROR:
>        b43-phy0: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 
> 0x00000000, 0x00000000, 0x00000000
>        b43-phy0: Controller RESET (DMA error) ...
>        Controller restarted
>        b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 
> 0x00000000, 0x00000000, 0x00000000
>        b43-phy0: Controller RESET (DMA error) ...
>
> with that "b43-phy0" mess then going on forever (happily at least
> ratelimited).
>
> I can obviously test patches etc.
>
>                        Linus
>

Hello,

Could you please test the tag "master-2009-08-26" from
wireless-testing? That one was the first version that worked, and in
that specific build, my card (exactly the same as yours) worked
perfectly, leading me to suspect a regression (probably not in the b43
driver, but in something else interfering with b43). Also try apic=off
& acpi=off (IIRC another DMA error victim, but with error code
0x00000800 had ACPI clobbering his DMA).

Also, is there any reference to a failed channel switch in the log?

Thanks,
Gábor

-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to