Jun 18 08:35:04 M-G kernel: [ 360.869891] cfg80211: All devices are disconnected, going to restore regulatory settings Jun 18 08:35:04 M-G kernel: [ 360.869901] cfg80211: Restoring regulatory settings Jun 18 08:35:04 M-G kernel: [ 360.869911] cfg80211: Calling CRDA to update world regulatory domain Jun 18 08:35:04 M-G kernel: [ 360.875466] ------------[ cut here ]------------ Jun 18 08:35:04 M-G kernel: [ 360.875493] WARNING: at net/wireless/sme.c:750 cfg80211_disconnected+0x10a/0x130 [cfg80211]() Jun 18 08:35:04 M-G kernel: [ 360.875497] Hardware name: 32607AG Jun 18 08:35:04 M-G kernel: [ 360.875500] Modules linked in: uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_core bluetooth videodev media lib80211_crypt_tkip wl(PO) fglrx(PO) i2c_piix4 cfg80211 ghash_clmulni_intel thinkpad_acpi lib80211 nvram rfkill fuse xfs exportfs nfs fscache dns_resolver lockd sunrpc jfs reiserfs btrfs hid_monterey hid_microsoft hid_logitech hid_ezkey hid_cypress hid_chicony hid_cherry hid_belkin hid_apple hid_a4tech usbhid usb_storage Jun 18 08:35:04 M-G kernel: [ 360.875550] Pid: 3292, comm: wl_event_handle Tainted: P W IO 3.8.13-gentoo #18 Jun 18 08:35:04 M-G kernel: [ 360.875554] Call Trace: Jun 18 08:35:04 M-G kernel: [ 360.875566] [<ffffffff81089c6a>] warn_slowpath_common+0x7a/0xb0 Jun 18 08:35:04 M-G kernel: [ 360.875573] [<ffffffff81089cb5>] warn_slowpath_null+0x15/0x20 Jun 18 08:35:04 M-G kernel: [ 360.875589] [<ffffffffa034ea1a>] cfg80211_disconnected+0x10a/0x130 [cfg80211] Jun 18 08:35:04 M-G kernel: [ 360.875640] [<ffffffffa0a4bdae>] wl_tkip_printstats+0x45ce/0x5ab0 [wl] Jun 18 08:35:04 M-G kernel: [ 360.875686] [<ffffffffa0a47c1d>] wl_tkip_printstats+0x43d/0x5ab0 [wl] Jun 18 08:35:04 M-G kernel: [ 360.875732] [<ffffffffa0a47bd0>] ? wl_tkip_printstats+0x3f0/0x5ab0 [wl] Jun 18 08:35:04 M-G kernel: [ 360.875740] [<ffffffff810a722b>] kthread+0xbb/0xc0 Jun 18 08:35:04 M-G kernel: [ 360.875747] [<ffffffff810a7170>] ? flush_kthread_work+0x120/0x120 Jun 18 08:35:04 M-G kernel: [ 360.875754] [<ffffffff815812ec>] ret_from_fork+0x7c/0xb0 Jun 18 08:35:04 M-G kernel: [ 360.875761] [<ffffffff810a7170>] ? flush_kthread_work+0x120/0x120 Jun 18 08:35:04 M-G kernel: [ 360.875764] ---[ end trace 49bed4dc593960c4 ]--- Besides that if have problems receiving an IP to an already connected access point and the driver is significant slower is most cases. With =net-wireless/broadcom-sta-5.100.82.112-r3 the problems are gone. Reproducible: Always
Does this happen out of the blue? The output suggests it occurs when you disconnect. Is wireless function impaired after you get this output? What do you mean by "significantly slower"? Is it just the DHCP or association or all traffic? Also, please give me your kernel version. And finally (off topic, though), does 5.100.82.112-r3 work fine for you? I've not received any feedback for it so far, i just know it does not work with my chip. (BCM4313)
I'm using gentoo-sources-3.8.13 and significant slower means that I'm unable to surf and IRC is the only protocol that is able to connect. I did some research ... If I use net-misc/dhcpcd as an DHCP-Client didn't receive an address If I use net-misc/dhcp as an DHCP-Client I receive an address But, even if I receive an address the connection is very slow - unable to surf slow. So switch back to the current version and I have an BCM4313 too. Until now the bug only appears if I'm turn of the laptop
Hmm. I've had similar problems using series 5 - which was the reason why i originally investigated a series 6. By "if I'm turn of the laptop" do you mean that you put the laptop into sleep mode? Suspend to ram or suspend to disk? Are you sure you have blacklisted bcma, mac80211 as well as brcmsmac?
Addendum: grepping my messages i found 1 occasion of this happening in the past week. It appeared a few times, then nothing again. I don't recall any connectivity issues. I don't keep logs for a longer period of time.
okay, i can confirm this bug; i found it happening 2 more times this week, but it seems like the driver is recovering itself. since the driver is a blob there is not much i can do about it at this point in terms of debugging. i would still stabilization - if mjjoker can confirm it actually does work with his chipset. if a no comes from him, i'll close it as CANTFIX.
The only thing I'm sure about is the fact that I don't like the vendor of that chipset. When running on Windows 7 the card is called BCM4313 With Gentoo /var/log/messages says BCM4727 and "lspci" BCM4313. I don't really know what to belive. I'm still not able to use WLAN with the new driver and the kernel oops occur if I shutdown the laptop. So I would say "CANTFIX" too.
same with me. regarding the driver confusion, its pciid is 14e4:4727, but it's marketed/sold as BCM4313. Anyway, let's see if it works out in the future.
