Fwd: [Bug 515668] New: kernel BUG at drivers/net/wireless/b43/dma.c:1406! when using openfwwf firmware
Hello,All! Here is a bug report regarding DMA issues with openfwwf ver. 5.2 . I suspect, that this is a known issue, but anyway, maybe this bugzilla ticket will add something important. -- Forwarded message -- From: bugzi...@redhat.com Date: 2009/8/5 Subject: [Bug 515668] New: kernel BUG at drivers/net/wireless/b43/dma.c:1406! when using openfwwf firmware To: lemen...@gmail.com Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: kernel BUG at drivers/net/wireless/b43/dma.c:1406! when using openfwwf firmware https://bugzilla.redhat.com/show_bug.cgi?id=515668 Summary: kernel BUG at drivers/net/wireless/b43/dma.c:1406! when using openfwwf firmware Product: Fedora Version: 11 Platform: i686 OS/Version: Linux Status: NEW Severity: urgent Priority: low Component: b43-openfwwf AssignedTo: lemen...@gmail.com ReportedBy: arethus...@gmail.com QAContact: extras...@fedoraproject.org CC: lemen...@gmail.com Estimated Hours: 0.0 Classification: Fedora 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 c400 (32-bit, non-prefetchable) [size=8K] Kernel driver in use: b43-pci-bridge Kernel modules: ssb -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. You are the assignee for the bug. -- With best regards, Peter Lemenkov. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [Bug 515668] New: kernel BUG at drivers/net/wireless/b43/dma.c:1406! when using openfwwf firmware
On Aug 5, 2009, at 1:07 PM, Peter Lemenkov wrote: Hello,All! Here is a bug report regarding DMA issues with openfwwf ver. 5.2 . I suspect, that this is a known issue, but anyway, maybe this bugzilla ticket will add something important. Hi Peter, many thanks. I added a note on the website. I have a few cards like that, I will do some tests to catch the bug. Cheers, -FG -- Forwarded message -- From: bugzi...@redhat.com Date: 2009/8/5 Subject: [Bug 515668] New: kernel BUG at drivers/net/wireless/b43/dma.c:1406! when using openfwwf firmware To: lemen...@gmail.com Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. Summary: kernel BUG at drivers/net/wireless/b43/dma.c:1406! when using openfwwf firmware https://bugzilla.redhat.com/show_bug.cgi?id=515668 Summary: kernel BUG at drivers/net/wireless/b43/dma.c:1406! when using openfwwf firmware Product: Fedora Version: 11 Platform: i686 OS/Version: Linux Status: NEW Severity: urgent Priority: low Component: b43-openfwwf AssignedTo: lemen...@gmail.com ReportedBy: arethus...@gmail.com QAContact: extras...@fedoraproject.org CC: lemen...@gmail.com Estimated Hours: 0.0 Classification: Fedora 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 c400 (32-bit, non-prefetchable) [size=8K] Kernel driver in use: b43-pci-bridge Kernel modules: ssb -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. You are the assignee for the bug. -- With best regards, Peter Lemenkov. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev --- Francesco Gringoli, PhD - Assistant Professor Dept. of Electrical Engineering for Automation University of Brescia via Branze, 38 25123 Brescia ITALY Ph: ++39.030.3715843 FAX: ++39.030.380014 WWW: http://www.ing.unibs.it/~gringoli INFORMATIVA SUL TRATTAMENTO DEI DATI PERSONALI I dati utilizzati per l'invio del presente messaggio sono trattati dall' Universita' degli studi di Brescia esclusivamente per finalita' istituzionali. Informazioni piu' dettagliate anche in ordine ai diritti dell'interessato sono riposte nell'informativa generale e nelle notizie pubblicate sul sito web dell'Ateneo nella sezione privacy. Il contenuto di questo messaggio e' rivolto unicamente alle persone cui e' indirizzato e puo' contenere informazioni la cui riservatezza e' tutelata legalmente. Ne sono vietati la riproduzione, la diffusione e l'uso in mancanza di autorizzazione del destinatario. Qualora il messaggio fosse pervenuto per errore, preghiamo di eliminarlo. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de
Re: [Bug 515668] New: kernel BUG at drivers/net/wireless/b43/dma.c:1406! when using openfwwf firmware
Francesco Gringoli wrote: On Aug 5, 2009, at 1:07 PM, Peter Lemenkov wrote: Hello,All! Here is a bug report regarding DMA issues with openfwwf ver. 5.2 . I suspect, that this is a known issue, but anyway, maybe this bugzilla ticket will add something important. Hi Peter, many thanks. I added a note on the website. I have a few cards like that, I will do some tests to catch the bug. Francesco, This bug is the same as the one I reported for both my 4311 and my 4318. When the TX status interrupt is entered for a particular cookie, the skb is freed, and the buffer pointer is replaced with a NULL. The kernel panic reported here is the result of detecting a NULL value for that buffer pointer. I think the conclusion is that the firmware is calling the interrupt routine with a cookie that was previously reported. Why? I don't know. Even with the source to look at, firmware is a big mystery. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [Bug 515668] New: kernel BUG at drivers/net/wireless/b43/dma.c:1406! when using openfwwf firmware
On Aug 5, 2009, at 4:41 PM, Larry Finger wrote: Francesco Gringoli wrote: On Aug 5, 2009, at 1:07 PM, Peter Lemenkov wrote: Hello,All! Here is a bug report regarding DMA issues with openfwwf ver. 5.2 . I suspect, that this is a known issue, but anyway, maybe this bugzilla ticket will add something important. Hi Peter, many thanks. I added a note on the website. I have a few cards like that, I will do some tests to catch the bug. Francesco, This bug is the same as the one I reported for both my 4311 and my 4318. When the TX status interrupt is entered for a particular cookie, the skb is freed, and the buffer pointer is replaced with a NULL. The kernel panic reported here is the result of detecting a NULL value for that buffer pointer. I think the conclusion is that the firmware is calling the interrupt routine with a cookie that was previously reported. Why? I don't know. Even with the source to look at, firmware is a big mystery. Hi Larry, D'oh!... so I already had some boards which displayed that behavior!! Ok ok, I will have two more (if the two minipci-e I bought will ever arrive, I'm still waiting) :-) Taking back my old laptop with PCMCIA slot. Cheers, -Francesco Larry INFORMATIVA SUL TRATTAMENTO DEI DATI PERSONALI I dati utilizzati per l'invio del presente messaggio sono trattati dall' Universita' degli studi di Brescia esclusivamente per finalita' istituzionali. Informazioni piu' dettagliate anche in ordine ai diritti dell'interessato sono riposte nell'informativa generale e nelle notizie pubblicate sul sito web dell'Ateneo nella sezione privacy. Il contenuto di questo messaggio e' rivolto unicamente alle persone cui e' indirizzato e puo' contenere informazioni la cui riservatezza e' tutelata legalmente. Ne sono vietati la riproduzione, la diffusione e l'uso in mancanza di autorizzazione del destinatario. Qualora il messaggio fosse pervenuto per errore, preghiamo di eliminarlo. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
BCM 4310 USB (14e4:4315). Any progress?
Hello, Sorry for pinging this list but I did some searches and I couldn't find responses... I've got a new Dell Mini-10 (Inspiron 1010), with the following wifi chipset: BCM 4310 USB. It's got PCI-ID: 14e4:4315. Despite being marked as USB, I suppose it's a mini-pci (as stated in this list's archives and some other places). But looking at: http://linuxwireless.org/en/users/Drivers/b43#Known_PCI_devices I can see: 14e4:4315 not supported BCM4312 802.11b/g - low power So my 1st question is: are BCM4312 and BCM4310 the same? Why do they have the same pci-id? My second question: at the same page I can read: BCM 4310 USB - This device has an LP PHY. We think that means low power. In any case, previous code does not work. The reverse engineers have generated specs for the code writers and development is in progress. Note: This card uses the PCI bus, despite its name. Please, could you update this info? I don't know whether the comment is up to date or whether (perhaps) some progress happened since then... any experimental driver out there? Thank you. -- Saludos, -Roman PGP Fingerprint: 09BB EFCD 21ED 4E79 25FB 29E1 E47F 8A7D EAD5 6742 [Key ID: 0xEAD56742. Available at KeyServ] ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM 4310 USB (14e4:4315). Any progress?
On Thu, Aug 6, 2009 at 12:05 AM, Roman Medina-Heigl Hernandezro...@rs-labs.com wrote: Hello, Sorry for pinging this list but I did some searches and I couldn't find responses... I've got a new Dell Mini-10 (Inspiron 1010), with the following wifi chipset: BCM 4310 USB. It's got PCI-ID: 14e4:4315. Despite being marked as USB, I suppose it's a mini-pci (as stated in this list's archives and some other places). But looking at: http://linuxwireless.org/en/users/Drivers/b43#Known_PCI_devices I can see: 14e4:4315 not supported BCM4312 802.11b/g - low power So my 1st question is: are BCM4312 and BCM4310 the same? Why do they have the same pci-id? The correct name of the card is BCM4312; some older pci.ids files incorrectly list it as BCM4310 USB. Update your pci.ids to fix this. My second question: at the same page I can read: BCM 4310 USB - This device has an LP PHY. We think that means low power. In any case, previous code does not work. The reverse engineers have generated specs for the code writers and development is in progress. Note: This card uses the PCI bus, despite its name. Please, could you update this info? I don't know whether the comment is up to date or whether (perhaps) some progress happened since then... any experimental driver out there? Thank you. There is no experimental driver yet. I'm currently working on an implementation, but right now, not even the hardware init code is complete. -- Saludos, -Roman PGP Fingerprint: 09BB EFCD 21ED 4E79 25FB 29E1 E47F 8A7D EAD5 6742 [Key ID: 0xEAD56742. Available at KeyServ] ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev -- 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
Re: BCM 4310 USB (14e4:4315). Any progress?
Gábor Stefanik wrote: On Thu, Aug 6, 2009 at 12:05 AM, Roman Medina-Heigl Hernandezro...@rs-labs.com wrote: Hello, Sorry for pinging this list but I did some searches and I couldn't find responses... I've got a new Dell Mini-10 (Inspiron 1010), with the following wifi chipset: BCM 4310 USB. It's got PCI-ID: 14e4:4315. Despite being marked as USB, I suppose it's a mini-pci (as stated in this list's archives and some other places). But looking at: http://linuxwireless.org/en/users/Drivers/b43#Known_PCI_devices I can see: 14e4:4315 not supported BCM4312 802.11b/g - low power So my 1st question is: are BCM4312 and BCM4310 the same? Why do they have the same pci-id? The correct name of the card is BCM4312; some older pci.ids files incorrectly list it as BCM4310 USB. Update your pci.ids to fix this. See below. My second question: at the same page I can read: BCM 4310 USB - This device has an LP PHY. We think that means low power. In any case, previous code does not work. The reverse engineers have generated specs for the code writers and development is in progress. Note: This card uses the PCI bus, despite its name. Please, could you update this info? I don't know whether the comment is up to date or whether (perhaps) some progress happened since then... any experimental driver out there? As you have discovered, this info is up to date. There is no experimental driver yet. I'm currently working on an implementation, but right now, not even the hardware init code is complete. Broadcom really has messed up the naming of the LP devices. For example, (a) BCM4312 802.11abg devices with ID 14e4:4312 that works with b43 (b) BCM4312 802.11bg devices with ID 14e4:4315 that does not work (c) BCM4310 USB with ID 14e4:4315 that also does not work with b43 The device in (c) has a USB core that is not enabled. I think Broadcom was considering a USB implementation; however these have never been released AFAIK. All of them are built on a PCI base. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
