Arch Linux

Nothing4You

Member

From: Germany

Registered: 2013-03-02

Posts: 10

BCM43228 with broadcom_wl throwing warnings & problems with connection

Hey there,

I'm using a Thinkpad X131e with a BCM43228 wlan chip with broadcom-wl driver from AUR.

Cut from `lspci -vvDnn`:

0000:02:00.0 Network controller [0280]: Broadcom Corporation BCM43228 802.11a/b/g/n [14e4:4359]
	Subsystem: Broadcom Corporation Device [14e4:0607]
	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: 0, Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 17
	Region 0: Memory at f0a00000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=2 PME-
	Capabilities: [58] Vendor Specific Information: Len=78 <?>
	Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [d0] Express (v1) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L1, Latency L0 <4us, L1 <64us
			ClockPM+ Surprise- LLActRep+ BwNot-
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+ BWMgmt- ABWMgmt-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
		AERCap:	First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
	Capabilities: [13c v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [160 v1] Device Serial Number 00-00-e6-ff-ff-fa-e0-06
	Capabilities: [16c v1] Power Budgeting <?>
	Kernel driver in use: wl
	Kernel modules: bcma, wl

I often see in my `journalctl -xfn` these lines and my wpa_supplicant using nl80211 has problems with my connection. first it works for a while, then it suddenly dies and doesn't want to reconnect. After some time it works again until it suddenly dies the next time.

Jun 01 01:55:53 gibson.local kernel: ------------[ cut here ]------------
Jun 01 01:55:53 gibson.local kernel: WARNING: at net/wireless/sme.c:642 cfg80211_roamed+0x8c/0x90 [cfg80211]()
Jun 01 01:55:53 gibson.local kernel: Hardware name: 3372CTO
Jun 01 01:55:53 gibson.local kernel: Modules linked in: ppp_deflate zlib_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc sr_mod cdrom option usb_wwan u
Jun 01 01:55:53 gibson.local kernel:  snd rfkill ac button soundcore r8169 video mii battery processor ext4 crc16 mbcache jbd2 sd_mod usb_storage rtsx_pci_sdmmc mmc_core ahci lib...mmon rtsx_pci
Jun 01 01:55:53 gibson.local kernel: Pid: 147, comm: wl_event_handle Tainted: P           O 3.9.4-1-ARCH #1
Jun 01 01:55:53 gibson.local kernel: Call Trace:
Jun 01 01:55:53 gibson.local kernel:  [<ffffffff810580b0>] warn_slowpath_common+0x70/0xa0
Jun 01 01:55:53 gibson.local kernel:  [<ffffffff8105819a>] warn_slowpath_null+0x1a/0x20
Jun 01 01:55:53 gibson.local kernel:  [<ffffffffa03b68dc>] cfg80211_roamed+0x8c/0x90 [cfg80211]
Jun 01 01:55:53 gibson.local kernel:  [<ffffffffa0611a35>] wl_bss_connect_done.isra.21+0x105/0x1b0 [wl]
Jun 01 01:55:53 gibson.local kernel:  [<ffffffffa0611dbf>] wl_notify_connect_status+0x2df/0x3c0 [wl]
Jun 01 01:55:53 gibson.local kernel:  [<ffffffffa060e4e5>] wl_event_handler+0x55/0x1f0 [wl]
Jun 01 01:55:53 gibson.local kernel:  [<ffffffffa060e490>] ? wl_deinit_priv_mem+0xa0/0xa0 [wl]
Jun 01 01:55:53 gibson.local kernel:  [<ffffffff8107b600>] kthread+0xc0/0xd0
Jun 01 01:55:53 gibson.local kernel:  [<ffffffff8107b540>] ? kthread_create_on_node+0x120/0x120
Jun 01 01:55:53 gibson.local kernel:  [<ffffffff814d9dec>] ret_from_fork+0x7c/0xb0
Jun 01 01:55:53 gibson.local kernel:  [<ffffffff8107b540>] ? kthread_create_on_node+0x120/0x120
Jun 01 01:55:53 gibson.local kernel: ---[ end trace 92d276a463b89308 ]---
Jun 01 01:55:53 gibson.local kernel: ------------[ cut here ]------------
Jun 01 01:55:53 gibson.local kernel: WARNING: at net/wireless/sme.c:642 cfg80211_roamed+0x8c/0x90 [cfg80211]()
Jun 01 01:55:53 gibson.local kernel: Hardware name: 3372CTO
Jun 01 01:55:53 gibson.local kernel: Modules linked in: ppp_deflate zlib_deflate bsd_comp ppp_async crc_ccitt ppp_generic slhc sr_mod cdrom option usb_wwan u
Jun 01 01:55:53 gibson.local kernel:  snd rfkill ac button soundcore r8169 video mii battery processor ext4 crc16 mbcache jbd2 sd_mod usb_storage rtsx_pci_sdmmc mmc_core ahci lib...mmon rtsx_pci
Jun 01 01:55:53 gibson.local kernel: Pid: 147, comm: wl_event_handle Tainted: P        W  O 3.9.4-1-ARCH #1
Jun 01 01:55:53 gibson.local kernel: Call Trace:
Jun 01 01:55:53 gibson.local kernel:  [<ffffffff810580b0>] warn_slowpath_common+0x70/0xa0
Jun 01 01:55:53 gibson.local kernel:  [<ffffffff8105819a>] warn_slowpath_null+0x1a/0x20
Jun 01 01:55:53 gibson.local kernel:  [<ffffffffa03b68dc>] cfg80211_roamed+0x8c/0x90 [cfg80211]
Jun 01 01:55:53 gibson.local kernel:  [<ffffffffa06118ac>] wl_notify_roaming_status+0xac/0x130 [wl]
Jun 01 01:55:53 gibson.local kernel:  [<ffffffffa060e4e5>] wl_event_handler+0x55/0x1f0 [wl]
Jun 01 01:55:53 gibson.local kernel:  [<ffffffffa060e490>] ? wl_deinit_priv_mem+0xa0/0xa0 [wl]
Jun 01 01:55:53 gibson.local kernel:  [<ffffffff8107b600>] kthread+0xc0/0xd0
Jun 01 01:55:53 gibson.local kernel:  [<ffffffff8107b540>] ? kthread_create_on_node+0x120/0x120
Jun 01 01:55:53 gibson.local kernel:  [<ffffffff814d9dec>] ret_from_fork+0x7c/0xb0
Jun 01 01:55:53 gibson.local kernel:  [<ffffffff8107b540>] ? kthread_create_on_node+0x120/0x120
Jun 01 01:55:53 gibson.local kernel: ---[ end trace 92d276a463b89309 ]---

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: BCM43228 with broadcom_wl throwing warnings & problems with connection

Have you treid rebuilding the module?  I have this same card, and it works amazingly.  After searching through my logs this has actually shown up once.  But it sounds like in your case, it has happened on numerous occasions.

If you read the readme or whatever is included with the source, it tells you how to build it to use the old wext driver instead.  I have just never seen a reason to do this.  It sounds as though you attribute this to nl80211, so maybe it is worth a shot...

Nothing4You

Member

From: Germany

Registered: 2013-03-02

Posts: 10

Re: BCM43228 with broadcom_wl throwing warnings & problems with connection

I've rebuilt the module on every kernel upgrade.
I also noticed this with earlier kernel versions than 3.9.4, which means I rebuilt it a couple times already. iirc I didn't have this problem with the 3.7 kernel but i'm not entirely sure about that, might have been coincidence.

I have no idea whether this is related to nl80211 or not, I just mentioned it because it's not (yet?) the default for wpa_supplicant.
I'll try using wpa_supplicant with wext later.

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: BCM43228 with broadcom_wl throwing warnings & problems with connection

When you update and rebuild the kernel module, are you just using the same tarball over and over again?  I ask because upon the move to 3.9.*, the maintainer of the AUR package, added an additional patch to the package.  I'm not exactly sure what it does, as I have never had a reason to doubt it was needed since mine is working flawlessly.

I wonder if your card would do the same thing if you were running a different distribution.  I think that something like fedora might be a good choice to test since they have a pretty up to date kernel and everything.

Nothing4You

Member

From: Germany

Registered: 2013-03-02

Posts: 10

Re: BCM43228 with broadcom_wl throwing warnings & problems with connection

i always update with the latest aur version, so yeah, i included that patch.

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: BCM43228 with broadcom_wl throwing warnings & problems with connection

Well, sorry I can't be of more help than this.  I think the only reasonable thing to try would be to see if it happens in another distirbution with a similar kernel version.  At least then you could try to narrow it down to whether it is specific to your setup, or something that is actually wrong with the hardware.

I think the ultimate test would be to see if it happens in windows.  Then if it still does it, you can call Lenovo with certainty that it is an issue with the hardware and that you need another.  Fortunately, I am pretty sure it is considered a CRU (Custoner Replaceable Unit), so they would likely just send you a new one, rather than require you send your entire system to them.