Hi Andreas, Thanks for the assistance... What kernel-version and model of the wifi- card are you using? Does it behave the same on both 2.4 and 5 Ghz?
For suspend/resume the pm-script seems to make it more stable atleast... When/if getting the "no traffic bug" it's enough to unload/load the module. It *may* take a few tries but the link comes back at least.. But i think that since you suspend (and unload the driver) it should perform better than before at least.... During a full day of normal usage i have lost my link once, so it's an improvement... unload / wait a few sec / load worked for me straight off today.. Yesterday i had to reload it a few times, but then i did not wait at all between unload/load, but it succeeded to come back anyway. Main part of the patch is for 4.x support, but there is a couple of things to prevent complete system-crashes. (Think it was in 3.18 or 3.19 that behavior started.) I'm currently just trying to figure out a way to trigger the issue here, in a reproducible way, to allow for some easier debugging. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1478592 Title: bcmwl-kernel-source fixes [Patch] Status in bcmwl package in Ubuntu: Confirmed Bug description: The broadcom-wl driver have a few issues that have not been corrected in the ubuntu package. Supplied with this bugreport is a monolithic patch that addresses some of those. Summary/testing of patch: - 2 days of local testing with associate/disassociate/scan between 2 access-points. (same model and running same openwrt version, so might not be a good test). - Suspend/resume seems to work (no extensive testing there yet). - Testing been done on a MBP 11,3 with a BCM4360 card running Ubuntu 15.04 with kernel 4.1.3 (vanilla) - Only 4.x changes are new, rest have been in use by several projects (ubuntu/gentoo/archlinux etc) for some time. Feel free to split it up into several patches.... This have been a locally maintained repo that have used several different sources and that's the reason for the monolithic patch. One issue that is left is the: if (WARN_ON(!bss)) return; in net/wireless/sme.c but this does not seem to cause issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1478592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
