Bug 754218 - %50 packet loss with BCM43224 rev 01 in MacBook Pro
Summary: %50 packet loss with BCM43224 rev 01 in MacBook Pro
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-15 18:07 UTC by joshua
Modified: 2012-03-29 05:52 UTC (History)
7 users (show)

Fixed In Version: kernel-3.3.0-4.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-29 05:52:03 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description joshua 2011-11-15 18:07:57 UTC
Description of problem:

I have a MacBook Pro, with this hardware:

03:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01)
        Subsystem: Apple Computer Inc. Device 0093
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at c1b00000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: wl
        Kernel modules: wl, brcmsmac

It mostly works, but with about 50 percent packet loss.  Removing it, and loading kmod-wl from rpmfusion, it works with 0% packet loss.

Maybe b43-openfwwf isn't yet ready to support my chipset, but if it isn't, it should probably refuse to try for it.  If not, the functionality needs to be improved.


Version-Release number of selected component (if applicable):

b43-openfwwf-5.2-6.fc15.noarch

Comment 1 joshua 2011-11-17 22:05:17 UTC
Here is what dmesg says when I'm having wifi problems:

[74695.300084] ieee80211 phy0: brcms_c_ampdu_dotxstatus_complete: Pkt tx suppres
sed, illegal channel possibly 40
[74695.300087] ieee80211 phy0: AMPDU status: BA Timeout, seq 633, in_transit 0
[74700.338206] ieee80211 phy0: brcms_c_ampdu_dotxstatus_complete: Pkt tx suppres
sed, illegal channel possibly 40
[74700.338215] ieee80211 phy0: AMPDU status: BA Timeout, seq 686, in_transit 0
[74700.338258] ieee80211 phy0: brcms_c_ampdu_dotxstatus_complete: Pkt tx suppres
sed, illegal channel possibly 40
[74700.338265] ieee80211 phy0: AMPDU status: BA Timeout, seq 687, in_transit 0
[74747.606302] ieee80211 phy0: brcms_c_ampdu_dotxstatus_complete: Pkt tx suppres
sed, illegal channel possibly 40
[74747.606314] ieee80211 phy0: AMPDU status: BA Timeout, seq 1372, in_transit 0
[74747.606371] ieee80211 phy0: brcms_c_ampdu_dotxstatus_complete: Pkt tx suppres
sed, illegal channel possibly 40
[74747.606380] ieee80211 phy0: AMPDU status: BA Timeout, seq 1373, in_transit 0



This happens enough that the network is effectively unusable.

Comment 2 Peter Lemenkov 2011-12-28 19:08:49 UTC
This issue has nothing with b43-openfwwf. Reassigning to kernel.

Comment 3 John W. Linville 2012-01-03 16:32:29 UTC
Please try to replicate the issue with kernel-3.1.6-1 or later.  You will not need to use the kmod-wl package.  Does the issue persist?

Comment 4 joshua 2012-01-03 17:08:43 UTC
Alright, here it is:

$ rpm -qa | egrep "b43|kernel-|-wl" | sort
b43-fwcutter-014-1.fc15.x86_64
b43-openfwwf-5.2-6.fc15.noarch
b43-tools-0-0.7.git20090125.fc15.x86_64
kernel-3.1.6-1.fc16.x86_64

$ uname -a
Linux f16-laptop 3.1.6-1.fc16.x86_64 #1 SMP Wed Dec 21 22:41:17 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux


I get about 700 bits per seconds :-(   I'll note that this is on a PEAP/MSCHAPv2 WPA2 Enterprise type network.

On a WPA2 Personal or Open wifi network, functionality and throughput is just fine.

Comment 5 John W. Linville 2012-01-03 18:49:13 UTC
That kernel should be using the brcmsmac driver, the new upstream driver supported by Broadcom.  Let's hope that they have some insight. :-)

Comment 6 Arend van Spriel 2012-01-04 20:53:26 UTC
What frequency/channel is the AP operating on?

Comment 7 joshua 2012-01-04 21:26:04 UTC
Good question.  Is there a way to tell from Linux?  I will say that rebooting to Windows and using wireless works flawlessly.

Does iwconfig or something show this detail?

Comment 8 John W. Linville 2012-01-05 14:08:13 UTC
"iwconfig wlan0" should give the requested info.

Comment 9 joshua 2012-01-05 19:21:37 UTC
$ sudo iwconfig wlan0
wlan0     IEEE 802.11abgn  ESSID:"something"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: 88:F0:77:77:82:00   
          Bit Rate=115.6 Mb/s   Tx-Power=19 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=41/70  Signal level=-69 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:23  Invalid misc:41   Missed beacon:0

Comment 10 Dave Jones 2012-03-22 16:44:43 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 11 Dave Jones 2012-03-22 16:49:10 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 12 Dave Jones 2012-03-22 16:58:30 UTC
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.

Comment 13 joshua 2012-03-28 14:03:31 UTC
Working well on the new kernel.  I'm on Freq 5.745 GHZ now, but assuming that doesn't matter, yes, this new kernel seems to have fixed something.

Comment 14 Peter Lemenkov 2012-03-29 05:52:03 UTC
So I think it's safe to close this now.


Note You need to log in before you can comment on or make changes to this bug.