Description of problem: I have a Dell Inspiron 1564 laptop which uses a Broadcom wireless card (PCI ID 14e4:4315). After I upgraded to kernel 2.6.32.9-70.fc12.x86_64, the card was detected, and the b43 driver was loaded automatically. The card also needs proprietary firmware, so I have tried both broadcom-wl-4.178.10.4.tar.bz2 and the older broadcom-wl-4.150.10.5.tar.bz2. Installing the firmware with b43-fwcutter works fine, and when I do 'ifconfig wlan0 up', the firmware loads as it should. Unfortunately, it only takes a few seconds before the kernel log floods with messages like this: b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000 b43-phy0: Controller RESET (DMA error) ... b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) b43-phy0: Controller restarted b43-phy0 ERROR: Fatal DMA error: 0x00000400, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000 b43-phy0: Controller RESET (DMA error) ... b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) b43-phy0: Controller restarted This sequence repeats until the computer freezes (takes less than a minute), at which point a hard reboot is the only way out. Version-Release number of selected component (if applicable): Kernel: 2.6.32.9-70.fc12.x86_64 Broadcom firmware: 4.150.10.5 and 4.178.10.4 How reproducible: Always Steps to Reproduce: sudo ifconfig wlan0 up Additional info: CPU: Intel i3 M 350 @ 2.27GHz Output from lspci: 00:00.0 Host bridge: Intel Corporation Device 0044 (rev 12) 00:02.0 VGA compatible controller: Intel Corporation Device 0046 (rev 12) 00:16.0 Communication controller: Intel Corporation Ibex Peak HECI Controller (rev 06) 00:1a.0 USB Controller: Intel Corporation Ibex Peak USB2 Enhanced Host Controller (rev 06) 00:1b.0 Audio device: Intel Corporation Ibex Peak High Definition Audio (rev 06) 00:1c.0 PCI bridge: Intel Corporation Ibex Peak PCI Express Root Port 1 (rev 06) 00:1c.1 PCI bridge: Intel Corporation Ibex Peak PCI Express Root Port 2 (rev 06) 00:1c.5 PCI bridge: Intel Corporation Ibex Peak PCI Express Root Port 6 (rev 06) 00:1d.0 USB Controller: Intel Corporation Ibex Peak USB2 Enhanced Host Controller (rev 06) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6) 00:1f.0 ISA bridge: Intel Corporation Ibex Peak LPC Interface Controller (rev 06) 00:1f.2 SATA controller: Intel Corporation Ibex Peak 4 port SATA AHCI Controller (rev 06) 00:1f.3 SMBus: Intel Corporation Ibex Peak SMBus Controller (rev 06) 00:1f.6 Signal processing controller: Intel Corporation Ibex Peak Thermal Subsystem (rev 06) 03:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01) 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) ff:00.0 Host bridge: Intel Corporation Device 2c62 (rev 02) ff:00.1 Host bridge: Intel Corporation Device 2d01 (rev 02) ff:02.0 Host bridge: Intel Corporation Device 2d10 (rev 02) ff:02.1 Host bridge: Intel Corporation Device 2d11 (rev 02) ff:02.2 Host bridge: Intel Corporation Device 2d12 (rev 02) ff:02.3 Host bridge: Intel Corporation Device 2d13 (rev 02)
What kernel version were you using before? Could this related to bug 575470?
(In reply to comment #1) > What kernel version were you using before? Could this related to bug 575470? I was using 2.6.31.5-127.fc12.x86_64 before upgrading to 2.6.32.9-70.fc12.x86_64. The bug might be related, but I don't think it's exactly the same. My card was not detected *at all* before 2.6.32.* kernels, so there was no way to reproduce the crash bug.
A few things: o Just verified that the bug is also present in 2.6.32.10-90 and 2.6.32.11-99 o It is not enough to just do 'ifconfig wlan0 up' to reproduce this, one must also connect to an access point (i.e., it only crashes after starting wpa_supplicant) o Here's another guy with the same problem (doesn't seem to crash his system though): http://forums.fedoraforum.org/showthread.php?t=235182
http://koji.fedoraproject.org/koji/taskinfo?taskID=2111547 The kernels above should switch to PIO mode when DMA errors occur. Please give them a try (after the build completes) and post the results here...thanks!
I have just tried it after installing a fresh Fedora 12 on a Lenovo S10e. I even tried the -102 kernel in updates-testing without any luck, but this -101 kernel from koji works as it should. Before this I have once seen the adapter bind to a network, but it reset itself as soon as I tried to use it. The rest of the time it has reset itself before it even got that far. In fact I am typing this over the wlan link, so if you can read this it works!
I can also confirm that 2.6.32.11-101.bz575571.fc12.x86_64 is working perfectly! :-) No more crashing; in fact, not a single wlan-related warning in the kernel log with this one. (FYI: I'm using Broadcom firmware v4.178.10.4.)
kernel-2.6.32.11-104.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/kernel-2.6.32.11-104.fc12
kernel-2.6.32.11-104.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update kernel'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/kernel-2.6.32.11-104.fc12
I have done more testing with 2.6.32.11-104.fc12, and unfortunately, I seem to have been too quick to celebrate earlier. :-( The box never crashes after you added the PIO mode fallback patch, but for some reason, the connection dies after a couple of minutes or so. It never disconnects from the access point, but no packets are going in or out. I have tried using both NetworkManager and wpa_supplicant/dhclient to set it up, but that doesn't make any difference. To eliminate the possibility of a hardware problem, I will do some thorough testing with Broadcom's proprietary drivers (both in Windows and Linux). I will post the results here tomorrow. birger: Is -104 working for you?
It's working perfectly with Broadcom's proprietary Linux driver (ping was running all night with less than 0.02% packet loss), so it's not a hardware problem.
kernel-2.6.32.16-141.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/kernel-2.6.32.16-141.fc12
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.