Bug 515668 - kernel BUG at drivers/net/wireless/b43/dma.c:1406! when using openfwwf firmware
Summary: kernel BUG at drivers/net/wireless/b43/dma.c:1406! when using openfwwf firmware
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: b43-openfwwf
Version: 11
Hardware: i686
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-05 10:08 UTC by Andrew Nguyen
Modified: 2010-01-27 09:06 UTC (History)
1 user (show)

Fixed In Version: 2.6.31.5-127.fc12.i686
Clone Of:
Environment:
Last Closed: 2010-01-27 09:06:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Captured kernel panic backtrace (4.42 KB, text/plain)
2009-08-05 10:09 UTC, Andrew Nguyen
no flags Details

Description Andrew Nguyen 2009-08-05 10:08:30 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.1) Gecko/20090717 Fedora/3.5.1-3.fc11 Firefox/3.5.1

I am using a Linksys PCMCIA wireless card, which is model WPC54GS at version 2, on a Fedora 11 system installed on a Thinkpad T42. When I am using the b43 kernel module in conjunction with the b43-openfwwf firmware, I frequently observe the system panic when there is heavy amounts of network activity on the wireless card interface. Empirically, this issue only seems to happen when the card is associated with the residential wireless network broadcast by the Actiontec MI424WR wireless router, and it does not occur when using the Broadcom firmware extracted according to the instructions from http://www.linuxwireless.org/en/users/Drivers/b43#device_firmware. I can most consistently cause a crash by using the speed testing service at http://www.speedtest.net/ to stress test the wireless interface.

Reproducible: Always

Steps to Reproduce:
1. Install b43-openfwwf to get the wireless card operational.
2. Visit http://www.speedtest.net/ for an easy way to stress test the card.
3. Start a speed test. The kernel should panic shortly after the test is begun.
Actual Results:  
The system halts with a kernel panic.

Expected Results:  
The system should not crash.

I captured the resulting kernel panic using netconsole, since the system did not switch to a text console when the panic occurred. The information from lspci -vv regarding the card is:

03:00.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
	Subsystem: Linksys Device 0049
	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: 64
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at c4000000 (32-bit, non-prefetchable) [size=8K]
	Kernel driver in use: b43-pci-bridge
	Kernel modules: ssb

Comment 1 Andrew Nguyen 2009-08-05 10:09:26 UTC
Created attachment 356296 [details]
Captured kernel panic backtrace

Comment 2 Peter Lemenkov 2009-08-05 10:20:25 UTC
Thanks for the report!

Does the issue exists with the latest b43-openfwwf-5.2 ?

Comment 3 Andrew Nguyen 2009-08-05 10:39:48 UTC
Yes, I am using b43-openfwwf-5.2-1.fc11 as reported by PackageKit.

Comment 4 Peter Lemenkov 2009-08-05 14:12:11 UTC
Report sent to upstream:

http://thread.gmane.org/gmane.linux.drivers.bcm54xx.devel/9064

Comment 5 Peter Lemenkov 2009-11-19 10:41:52 UTC
Andrew, could you, please, re-check whether this issue still exists in the latest F-11 (or even F-12) kernels?

Comment 6 Andrew Nguyen 2009-11-23 19:25:44 UTC
I can't reproduce a crash with Fedora 12 kernel 2.6.31.5-127.fc12.i686, so I'm inclined to say that this bug is fixed.


Note You need to log in before you can comment on or make changes to this bug.