On Mon, Jan 25, 2010 at 9:15 PM, Lucas Thode <ljth...@gmail.com> wrote: > ---start dmesg snippet--- > [17189.121003] b43-pci-bridge 0000:06:00.0: PCI INT A disabled > [17192.494272] cfg80211: Using static regulatory domain info > [17192.494279] cfg80211: Regulatory domain: US > [17192.494283] (start_freq - end_freq @ bandwidth), (max_antenna_gain, > max_eirp > ) > [17192.494292] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm) > [17192.494299] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) > [17192.494306] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) > [17192.494314] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) > [17192.494321] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) > [17192.494328] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm) > [17192.494418] cfg80211: Calling CRDA for country: US > [17192.658174] b43-pci-bridge 0000:06:00.0: PCI INT A -> GSI 19 (level, low) > -> > IRQ 19 > [17192.658206] b43-pci-bridge 0000:06:00.0: setting latency timer to 64 > [17192.724352] ssb: Sonics Silicon Backplane found on PCI device > 0000:06:00.0 > [17192.769108] b43-phy0: Broadcom 4312 WLAN found (core revision 15) > [17192.843094] phy0: Selected rate control algorithm 'minstrel' > [17192.844206] Registered led device: b43-phy0::tx > [17192.844444] Registered led device: b43-phy0::rx > [17192.844500] Registered led device: b43-phy0::radio > [17192.844859] Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: > FW13 ] > [17196.776755] b43 ssb0:0: firmware: requesting b43/ucode15.fw > [17196.780967] b43 ssb0:0: firmware: requesting b43/lp0initvals15.fw > [17196.784551] b43 ssb0:0: firmware: requesting b43/lp0bsinitvals15.fw > [17196.921708] b43-phy0: Loading firmware version 410.2160 (2007-05-26 > 15:32:10) > [17202.497881] ADDRCONF(NETDEV_UP): wlan0: link is not ready > [17202.934136] b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, > 0x00000000, 0x00000000, 0x00000000, 0x00000000 > [17202.934153] b43-phy0: Controller RESET (DMA error) ... > [17203.148369] b43-phy0: Loading firmware version 410.2160 (2007-05-26 > 15:32:10) > [17208.681254] b43-phy0: Controller restarted > [17208.696481] b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, > 0x00000000, 0x00000000, 0x00000000, 0x00000000 > [17208.696490] b43-phy0: Controller RESET (DMA error) ... > [17208.914882] b43-phy0: Loading firmware version 410.2160 (2007-05-26 > 15:32:10) > [17214.461361] b43-phy0: Controller restarted > [17214.461610] b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, > 0x00000000, 0x00000000, 0x00000000, 0x00000000 > [17214.461626] b43-phy0: Controller RESET (DMA error) ... > [17214.676285] b43-phy0: Loading firmware version 410.2160 (2007-05-26 > 15:32:10) > ---end dmesg snippet---...and on and on the dma errors go. > > This occured about (sorry, not sure exactly, but I don't think it quite > matters with this particular error) when I used "iwlist scan" to search for > wireless networks after I used the b43-fwcutter from Debian testing to > install the firmware and re-inserted the driver with 'modprobe -r b43; > modprobe b43'. > > kb...@kb1rd-mobroost:~$ uname -a > Linux kb1rd-mobroost 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 > x86_64 GNU/Linux > kb...@kb1rd-mobroost:~$ lspci -vvn | grep 43 -A7 > 06:00.0 0280: 14e4:4315 (rev 01) > Subsystem: 1028:000b > 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 19 > Region 0: Memory at f4000000 (64-bit, non-prefetchable) [size=16K] > Capabilities: <access denied> > Kernel driver in use: b43-pci-bridge > > <extraneous output having to do with my Ethernet chip snipped> > kb...@kb1rd-mobroost:~$ cat /proc/cpuinfo > processor : 0 > vendor_id : GenuineIntel > cpu family : 6 > model : 15 > model name : Intel(R) Core(TM)2 Duo CPU T5670 @ 1.80GHz > stepping : 13 > cpu MHz : 800.000 > cache size : 2048 KB > physical id : 0 > siblings : 2 > core id : 0 > cpu cores : 2 > apicid : 0 > initial apicid : 0 > fpu : yes > fpu_exception : yes > cpuid level : 10 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm > constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64 monitor > ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm ida > bogomips : 3590.43 > clflush size : 64 > cache_alignment : 64 > address sizes : 36 bits physical, 48 bits virtual > power management: > > <output for core 1 snipped> > > As you can tell, this processor is neither an Atom nor a ULV Core 2 Duo. > The WLAN card is the Dell Wireless 1395 that came with the laptop (a Vostro > 1510). I can build a custom kernel based on the Debian kernel sources if > need be; just tell me what config options to flip/patches to apply. Also, > wl.o works on this laptop with the Debian 2.6.30 kernel. Aptitude lists the > kernel version as a 2.6.32-5. > > > --Lucas > > _______________________________________________ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > >
A few things to check: -Is this on PhoenixBios? -Does loading wl, doing a warm reboot and loading b43 make b43 work? -Try updating the firmware to v478. (AFAIK there was someone on the list before with a DMA error on a non-ULV, and it was solved by updating the firmware. Broadcom's wl.ko uses a v5xx firmware for the record.) -- 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
