Bug 754218
Summary: | %50 packet loss with BCM43224 rev 01 in MacBook Pro | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | joshua |
Component: | kernel | Assignee: | John W. Linville <linville> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | arend, gansalmon, itamar, jonathan, kernel-maint, lemenkov, madhu.chinakonda |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | kernel-3.3.0-4.fc16 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-03-29 05:52:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
joshua
2011-11-15 18:07:57 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. This issue has nothing with b43-openfwwf. Reassigning to kernel. 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? 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. That kernel should be using the brcmsmac driver, the new upstream driver supported by Broadcom. Let's hope that they have some insight. :-) What frequency/channel is the AP operating on? 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? "iwconfig wlan0" should give the requested info. $ 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 [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. [mass update] kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository. Please retest with this update. 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. So I think it's safe to close this now. |