Description of problem:
the wl binary driver in combination with the BCM4352 wifi adapter as in Dell XPS 13 triggers kernel panic when trying to setup wifi with static IP, and also causes kernel-panics on suspned/resume for other users and other card variants.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. try to configure network with static IP
2. connect to it and
3. once real data transfer occurs â panic
pinging the router is OK, but launching Chrome/Firefox or just trying to use curl to fetch a webpage â crash
There's patch available at the launchpad URL that I successfully added to the dkms version of the driver package (dkms-broadcom-wl-188.8.131.52)
With that no crash/kernel panic anymore
Steps to Reproduce:
see the linked https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880 for patch and more symptoms/other affected hardware.
Arch & Fedora also use that patch.
Thanks for the bugreport and the reference to the fix
This update fixes a null pointer crash in the proprietary
broadcom wl driver.
*** Bug 15893 has been marked as a duplicate of this bug. ***
*** Bug 16258 has been marked as a duplicate of this bug. ***
IMHO this build of driver can leave updates_testing and can come to updates dir. Works for me for few days now without crashing. Many thanks!
Broadcom users: Please test these packages and report here whether they resolve the issues for you. Please also state whether your installation is i586 or x86_64
Dusted off an HP zd800 with Broadcom BCM4318 controller
Installed Mageia 5 using bootnonfree.iso x86_64.
Set up an unused IP. Wifi connected with no obvious issues.
MCC Network Center showed two Wifi interfaces - Broadcom and wlan0. There is only one physical wireless card. Setting up the BCM with MCC did result in a connection which then died disconnected and the wlan0 connection started instead.
lspci | grep -i wireless gave BCM4318
iwconfig gave wlan0
I could not reproduce this problem, but I don't know which device driver module is in use with the BCM. ssl was associated with the BCM and seemed not to work.
Maybe a different driver module is loaded in my case.
MGA5-64 on HP Probook 6555b KDE with Broadcom BCM4313 wifi chipset.
I installed only the desktop packages, not the server.
The installation removed the broadcom-bcma-config package.
Went then to MCC-New network interface, and could there configure the wifi as wl01 device. The available wifi's were displayed (this never worked before, I had to define my wifi connection manually) and did take over the settings defined before.
Annoying was that I could not define my usual fixed IP address as this was reported to be in use by device wlp7s0b1, which was the usual way to get the wifi working at installation time for this device. This device wlp7s0b1 is nowhere shown in New network interface nor Network Network Center. Completely rebooting does not remove it either, and I still cannot the fixed IP address I want
But the network connection works OK, if not faster than before
(In reply to Tadej Panjtar from comment #5)
> IMHO this build of driver can leave updates_testing and can come to updates
> dir. Works for me for few days now without crashing. Many thanks!
I have MGA5-64 (x86_64) on HP Probook 6570b KDE with Broadcom BCM43228 chipset. This packages resolve issues for me.
If the question mark on the Whiteboard is directed to me: the update on itself seems OK and works better than before, but When applied to a standard installation of MGA5 as before, it causes a problem.
I wonder whether this problem is (at least partly) due to the fact that the broadcom packages in their older version would never been installed as the substitute wlp7s0b1 device works OK after installation, so most users (including me) would never have looked back.
(In reply to Vladimir Zawalinski from comment #7)
> Dusted off an HP zd800 with Broadcom BCM4318 controller
> Installed Mageia 5 using bootnonfree.iso x86_64.
> Set up an unused IP. Wifi connected with no obvious issues.
> MCC Network Center showed two Wifi interfaces - Broadcom and wlan0. There is
> only one physical wireless card. Setting up the BCM with MCC did result in a
> connection which then died disconnected and the wlan0 connection started
> lspci | grep -i wireless gave BCM4318
> iwconfig gave wlan0
> I could not reproduce this problem, but I don't know which device driver
> module is in use with the BCM. ssl was associated with the BCM and seemed
> not to work.
> Maybe a different driver module is loaded in my case.
Forcing hibernation by setting up then closing lid and opening it again did not cause any anomalous behaviour.
the proprietary driver does conflict with the opensource one. Mageia "forces" the opensource one if your card is supported by it.
(forces=whenever you use the GUI based configuration tools it will prompt you to install the opensource driver rpms (if you uninstalled those) and will set it up with opensourcedriver (even if you blacklisted the module) - it will leave it alone when just using netcenter (but there the effect of having two wlan devices showing up - one with binary driver - all ok with that. But if you try to expand the other one the opensource driver dance begins)
So when you have any of b44 b43 b43legacy ssb brcmsmac show up in lsmod, you're using the opensource driver.
That being said: the bug only affects the binary driver - and while a couple of different broadcom devices have been reported from suffering from the problems (to different extent) - it is not said that you can reproduce with every broadcom device.
My 0,02 â¬: enough people confirmed the fixed package to solve the problem (and not causing different problems) in this very bug as well as in the other distro's bugtrackers to send it out as update.
Won't affect most broadcom users (as opensource driver is not touched, and there is no benefit in using proprietary driver when opensource one works) - but fixes critical bug for those unlucky enough to be forced to use the binary-only one.
Validating based on Christian's comment 12, which describes the issue well and seems sensible. Advisory uploaded.
Thomas, please assess before pushing to 5 updates.
has_procedure advisory MGA5-64-OKCC:
An update for this issue has been pushed to Mageia Updates repository.