14e4:4331 [Macbook Pro 10,1] Extremely high packet loss with BCM4331 wireless

[Seth Forshee]

When using the b43 driver I can bring up the wireless. I see fewer APs then expected when scanning. I can connect to an AP, but any attempt to use the network connection results in packet loss of nearly 100%.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-15-generic 3.5.0-15.23~lp000000v201209272258
ProcVersionSignature: Ubuntu 3.5.0-15.23~lp000000v201209272258-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ubuntu 1977 F.... pulseaudio
 /dev/snd/controlC0: ubuntu 1977 F.... pulseaudio
Date: Fri Sep 28 07:36:38 2012
HibernationDevice: RESUME=UUID=8cc5028d-5e31-4fc2-9dd4-a6cae2d4b76e
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
MachineType: Apple Inc. MacBookPro10,1
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 nouveaufb
 1 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-15-generic root=UUID=0fa98354-5cbd-4015-9f23-9df12bfd7896 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-15-generic N/A
 linux-backports-modules-3.5.0-15-generic N/A
 linux-firmware 1.94
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP101.88Z.00EE.B02.1208081132
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C3EC7CD22292981F
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C3EC7CD22292981F
dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B02.1208081132:bd08/08/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
dmi.product.name: MacBookPro10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

[Nickolay Ihalainen (ihanick)]

I have similar problem with MacBookPro8,1:
firmware version 666.2 (2011-02-23 01:15:07)
BCM4331 802.11a/b/g/n [14e4:4331] (rev 02)

There is a huge packet loss periodically that could be fixed by reloading b43 module:
ifconfig wlan0 down; rmmod b43 ; modprobe b43

The problem could be repeated with:
linux-image-3.5.0-18-generic
linux-image-3.7.0-030700rc4-generic_3.7.0-030700rc4
I have tried to rollback to 3.2 kernel:
linux-image-3.2.34-030234_3.2.34-030234.201211161335,
but the problem persist, but at least with smaller probability.

Steps to reproduce:
1) create a network load, like view video on youtube
2) browse normal web pages.

Without downloading files or online video the probability to have high packet loss is low for me. The problem could be reproduced with different wifi access points:
DDWRT on Dlink Dir-615 (G-only),
ASUS RT-N12 with a stock firmware (N)
TP-LINK TL-WR841ND (N)

I think the same problem described here:
http://permalink.gmane.org/gmane.linux.drivers.bcm54xx.devel/13499

[Seth Forshee (sforshee)]

On Fri, Nov 23, 2012 at 03:25:24PM -0000, Nickolay Ihalainen wrote:
> I have similar problem with MacBookPro8,1:
> firmware version 666.2 (2011-02-23 01:15:07)
> BCM4331 802.11a/b/g/n [14e4:4331] (rev 02)
>
> There is a huge packet loss periodically that could be fixed by reloading b43 module:
> ifconfig wlan0 down; rmmod b43 ; modprobe b43

You're talking about b43 rather than brcmsmac, so it cannot be the same
problem. You can file a new bug, but it's unlikely we'll be able to do
much about it because the information we have about BCM4331 is
incomplete. Broadcom has not provided Linux support for that device and
has not provided specifications for us to know how to properly configure
it.

[Nickolay Ihalainen (ihanick)]

Seth, according to your ProcModules.txt brcmsmac is not loaded, but you have b43 loaded.
b43 is used for wlan0 interface according to WifiSyslog.txt.

BCM4331 is not supported by brcmsmac, see
http://linuxwireless.org/en/users/Drivers/brcm80211#Supported_Chips

From your lspci you have:
BCM4331 802.11a/b/g/n [14e4:4331] (rev 02)

It's exactly the same as mine:
BCM4331 802.11a/b/g/n [14e4:4331] (rev 02)

[Seth Forshee (sforshee)]

Bah, sorry, I got this bug confused with a different one. So yes, the bug is the same and no new bug is needed. The statement about not knowing how to configure the hardware is still correct however; specifically, we have incomplete information about how to program the PHY.

[Nickolay Ihalainen (ihanick)]

Hello Seth,
Could you try to reproduce the problem with b43 driver and disable hardware encryption:
# echo options b43 nohwcrypt=1 >> /etc/modprobe.d/b43.conf
rmmod b43;modprobe b43

The problem is gone for me.
Today is one week since the problem is fixed for me, no unexpected connection drops even with constant suspend usage (I have SUSPEND_MODULES="b43 bcma")

[tjbp (tjbp)]

Nickolay; what kernel version are you running? I'm running 3.6.11 x86_64 on a MacBookPro10,1 and have this issue. I've tried several different module options (including the one you mentioned) and none have stopped the packet loss - I'm curious to see if this is a regression or just the same bug.

[Nickolay Ihalainen (ihanick)]

tjbp, I'm using an 64-bit kernel from ubuntu: 3.5.0-22-generic

The time to "crash" is really differs on access point model.
Currently I'm running for two weeks without packetloss problem.

Linux bb 3.5.0-22-generic #33-Ubuntu SMP Wed Jan 2 21:47:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
[ 25.692170] b43-phy0: Broadcom 4331 WLAN found (core revision 29)
[ 25.692316] b43-phy0 debug: Found PHY: Analog 9, Type 7, Revision 1
[ 25.692326] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2059, Revision 0
[ 28.410803] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)

Have only:
 options b43 verbose=4 nohwcrypt=1
under /etc/modprobe.d/b43.conf

If I will remove nohwcrypt=1, in 5-10 minutes under usual load I'm getting huge packet loss, can't use web, just icmp packets. After any of interface restart, the connection starts working again: (ifconfig down/up, rfkill)