search

kaloz / mwlwifi

mac80211 driver for the Marvell 88W8864 802.11ac chip
397 stars 119 forks source link

ba/ampdu error with 10.3.0.12 #41

Closed kristrev closed 8 years ago

kristrev commented 9 years ago

Opened a new issue on @yuhhaurlin request.

Things have improved significanlty since 10.3.0.10, but the ba/ampdu error still occurs:

[ 562.110063] ieee80211 phy0: check ba result error 1 [ 562.114983] ieee80211 phy0: ampdu start error code: -22 [ 562.170025] ieee80211 phy0: check ba result error 1 [ 562.174939] ieee80211 phy0: ampdu start error code: -22 [ 562.220015] ieee80211 phy0: check ba result error 1 [ 562.224924] ieee80211 phy0: ampdu start error code: -22 [ 562.270014] ieee80211 phy0: check ba result error 1 [ 562.274923] ieee80211 phy0: ampdu start error code: -22 [ 562.320028] ieee80211 phy0: check ba result error 1 [ 562.324939] ieee80211 phy0: ampdu start error code: -22 [ 562.380019] ieee80211 phy0: check ba result error 1 [ 562.384922] ieee80211 phy0: ampdu start error code: -22 [ 562.430018] ieee80211 phy0: check ba result error 1 [ 562.434919] ieee80211 phy0: ampdu start error code: -22

Things work fine for a while, then some random event X happens and the errors start happening (while transferring data). The devices connected to 5GHz is an iPhone 6 Plus and a Lenovo X1 Carbon 2. gen. After some time it seems the 5Ghz just gives up and takes a long nap. By connecting to the 2.4 GHz and restarting wifi, 5GHz works again but at reduced speed.

Another, potentially related error, is that the iPhone has trouble connecting to the 5GHz network. It keeps requesting me for the key, and seemingly only accepts the key when another devices (the laptop) has been connected. Otherwise it just gives me an error.

Debug fs output (in case it helps debugging):

/ampdu:
stream: 0
idx: 0
state: 3
mac address: 7c:7a:91:a3:37:c5
tid: 0
stream: 1
idx: 1
state: 3
mac address: e0:b5:2d:15:cf:da
tid: 0
stream: 2
idx: 0
state: 0
stream: 3
idx: 0
state: 0

/info:
driver name: mwlwifi
chip type: 88W8864
hw version: 7
driver version: 10.3.0.12
firmware version: 0x07020806
mac address: 00:25:9c:13:ab:6f
2g: disable
5g: enable
antenna: 2 2
irq number: 101
iobase0: e0e00000
iobase1: e1000000
tx limit: 768
rx limit: 64
ap macid support: 0000ffff
sta macid support: 00010000
macid used: 00000001
mfg mode: false

/sta

mac address: 7c:7a:91:a3:37:c5
aid: 1
ampdu: true
amsdu: false
IV: 00000012d4b9

mac address: e0:b5:2d:15:cf:da
aid: 2
ampdu: true
amsdu: false
IV: 000000032348

/vif

macid: 0
type: ap
ssid: XXXXXXX
mac address: 00:25:9c:13:ab:6f
hw_crypto_enabled: true
key idx: 0
IV: 000000000001
WMM:
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 
0x00 0x00 
RSN:
RSN48:
0x49 0x4a 0x41 0x42 0x43 0x44 0x45 0x46 
0x47 0x48 0x49 0x4a 0x41 0x42 0x43 0x44 
0x45 0x46 0x47 0x48 0x49 0x4a 0x41 0x42 
0x43 0x44 
HT:
0x2d 0x1a 0x6f 0x00 0x17 0xff 0xff 0x00 
0x00 0x01 0x00 0x00 0x00 0x00 0x00 0x00 
0x00 0x01 0x00 0x00 0x00 0x00 0x00 0x00 
0x00 0x00 0x00 0x00 0x3d 0x16 0xa1 0x07 
0x04 0x00 0x00 0x00 0x00 0x00 0x00 0x00 
0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 
0x00 0x00 0x00 0x00 0x7f 0x08 0x00 0x00 
0x00 0x00 0x00 0x00 0x00 0x40 
VHT:
0xbf 0x0c 0x31 0x18 0x80 0x33 0xfa 0xff 
0x00 0x00 0xfa 0xff 0x00 0x00 0xc0 0x05 
0x01 0x9b 0x00 0xfc 0xff

@bmork also reports still seeing this issue with a Galaxy S3. He instrumented the driver with debug output and posted the following output in the other issue:

[ 3688.592193] mwl_rx_recv: ieee80211 phy0: c4:42:02:e2:8c:f3 - addba.resp.capab=0x802
[ 8398.001127] mwl_rx_recv: ieee80211 phy0: 5c:0a:5b:79:ae:68 - addba.resp.capab=0x202
[10097.335747] mwl_rx_recv: ieee80211 phy0: 0c:8b:fd:08:09:71 - addba.resp.capab=0x1002
[11268.034546] mwl_rx_recv: ieee80211 phy0: 5c:0a:5b:79:ae:68 - addba.resp.capab=0x202
[19654.992154] mwl_rx_recv: ieee80211 phy0: 58:c3:8b:ec:66:82 - addba.resp.capab=0x202
[20421.038180] mwl_rx_recv: ieee80211 phy0: 58:c3:8b:ec:66:82 - addba.resp.capab=0x202
[20656.173799] ieee80211 phy1: check ba result error 1
[20656.178722] ieee80211 phy1: ampdu start error code: -22
[20656.223819] ieee80211 phy1: check ba result error 1
[20656.228741] ieee80211 phy1: ampdu start error code: -22
[20656.344165] ieee80211 phy1: check ba result error 1
[20656.349168] ieee80211 phy1: ampdu start error code: -22
[20656.393800] ieee80211 phy1: check ba result error 1
[20656.398763] ieee80211 phy1: ampdu start error code: -22
[20656.443813] ieee80211 phy1: check ba result error 1
[20656.448735] ieee80211 phy1: ampdu start error code: -22
[20656.503806] ieee80211 phy1: check ba result error 1
[20656.508782] ieee80211 phy1: ampdu start error code: -22
[20656.553770] ieee80211 phy1: check ba result error 1
[20656.558693] ieee80211 phy1: ampdu start error code: -22
[20657.633966] ieee80211 phy1: check ba result error 1
[20657.638893] ieee80211 phy1: ampdu start error code: -22
[20831.758119] mwl_rx_recv: ieee80211 phy0: 58:c3:8b:ec:66:82 - addba.resp.capab=0x202
[22123.133692] mwl_rx_recv: ieee80211 phy0: 58:c3:8b:ec:66:82 - addba.resp.capab=0x202
[23020.998999] mwl_rx_recv: ieee80211 phy1: 58:c3:8b:ec:66:82 - addba.resp.capab=0x202
[23058.813849] ieee80211 phy0: check ba result error 1
[23058.818816] ieee80211 phy0: ampdu start error code: -22
[23058.854137] ieee80211 phy0: check ba result error 1
[23058.859108] ieee80211 phy0: ampdu start error code: -22
[23058.904165] ieee80211 phy0: check ba result error 1
[23058.909181] ieee80211 phy0: ampdu start error code: -22
[23058.973989] ieee80211 phy0: check ba result error 1
[23058.979005] ieee80211 phy0: ampdu start error code: -22
[23059.014102] ieee80211 phy0: check ba result error 1
[23059.019094] ieee80211 phy0: ampdu start error code: -22
[23059.054064] ieee80211 phy0: check ba result error 1
[23059.059037] ieee80211 phy0: ampdu start error code: -22
[23059.094271] ieee80211 phy0: check ba result error 1
[23059.099239] ieee80211 phy0: ampdu start error code: -22
[23059.144212] ieee80211 phy0: check ba result error 1
[23059.149338] ieee80211 phy0: ampdu start error code: -22
[23059.223957] ieee80211 phy0: check ba result error 1
[23059.228985] ieee80211 phy0: ampdu start error code: -22
[23059.264327] ieee80211 phy0: check ba result error 1
[23059.269315] ieee80211 phy0: ampdu start error code: -22
[23059.324148] ieee80211 phy0: check ba result error 1
[23059.329129] ieee80211 phy0: ampdu start error code: -22
[23059.404042] ieee80211 phy0: check ba result error 1
[23059.409010] ieee80211 phy0: ampdu start error code: -22
[23059.444121] ieee80211 phy0: check ba result error 1
[23059.449093] ieee80211 phy0: ampdu start error code: -22
[23059.488862] ieee80211 phy0: check ba result error 1
[23059.493785] ieee80211 phy0: ampdu start error code: -22
[23059.534212] ieee80211 phy0: check ba result error 1
[23059.539172] ieee80211 phy0: ampdu start error code: -22
[23059.584337] ieee80211 phy0: check ba result error 1
[23059.589358] ieee80211 phy0: ampdu start error code: -22
[23059.654218] ieee80211 phy0: check ba result error 1
[23059.659299] ieee80211 phy0: ampdu start error code: -22
[23059.704376] ieee80211 phy0: check ba result error 1
[23059.709357] ieee80211 phy0: ampdu start error code: -22
[23059.784334] ieee80211 phy0: check ba result error 1
[23059.789299] ieee80211 phy0: ampdu start error code: -22
[23059.836120] mwl_rx_recv: ieee80211 phy0: 58:c3:8b:ec:66:82 - addba.resp.capab=0x202
[28906.108176] mwl_rx_recv: ieee80211 phy0: 5c:0a:5b:79:ae:68 - addba.resp.capab=0x202
[29157.141050] mwl_rx_recv: ieee80211 phy1: 0c:8b:fd:08:09:71 - addba.resp.capab=0x1002
[32575.001086] ieee80211 phy1: check ba result error 1
[32575.006008] ieee80211 phy1: ampdu start error code: -22
[32575.051079] ieee80211 phy1: check ba result error 1
[32575.056002] ieee80211 phy1: ampdu start error code: -22
[32575.561088] ieee80211 phy1: check ba result error 1
[32575.566009] ieee80211 phy1: ampdu start error code: -22
[32575.611081] ieee80211 phy1: check ba result error 1
[32575.616006] ieee80211 phy1: ampdu start error code: -22
[32575.661130] ieee80211 phy1: check ba result error 1
[32575.666055] ieee80211 phy1: ampdu start error code: -22
[32575.721072] ieee80211 phy1: check ba result error 1
[32575.725994] ieee80211 phy1: ampdu start error code: -22
[32575.771084] ieee80211 phy1: check ba result error 1
[32575.776007] ieee80211 phy1: ampdu start error code: -22
[35788.932981] mwl_rx_recv: ieee80211 phy0: 5c:0a:5b:79:ae:68 - addba.resp.capab=0x202
[67524.758920] mwl_rx_recv: ieee80211 phy0: 80:86:f2:09:0f:b5 - addba.resp.capab=0x1002
[89605.118409] mwl_rx_recv: ieee80211 phy0: 0c:8b:fd:08:09:71 - addba.resp.capab=0x1002
[91525.521926] mwl_rx_recv: ieee80211 phy0: 5c:0a:5b:79:ae:68 - addba.resp.capab=0x202
[108434.204598] mwl_rx_recv: ieee80211 phy0: 58:c3:8b:ec:66:82 - addba.resp.capab=0x202
[108445.369578] mwl_rx_recv: ieee80211 phy0: 0c:8b:fd:08:09:71 - addba.resp.capab=0x1002
[108671.317061] mwl_rx_recv: ieee80211 phy1: 58:c3:8b:ec:66:82 - addba.resp.capab=0x202
[108742.047095] ieee80211 phy0: check ba result error 1
[108742.052155] ieee80211 phy0: ampdu start error code: -22
[108742.086924] ieee80211 phy0: check ba result error 1
[108742.092003] ieee80211 phy0: ampdu start error code: -22
[108742.127182] ieee80211 phy0: check ba result error 1
[108742.132250] ieee80211 phy0: ampdu start error code: -22
[108742.166947] ieee80211 phy0: check ba result error 1
[108742.172050] ieee80211 phy0: ampdu start error code: -22
[108742.207132] ieee80211 phy0: check ba result error 1
[108742.212301] ieee80211 phy0: ampdu start error code: -22
[108742.247162] ieee80211 phy0: check ba result error 1
[108742.252319] ieee80211 phy0: ampdu start error code: -22
[108742.287046] ieee80211 phy0: check ba result error 1
[108742.292106] ieee80211 phy0: ampdu start error code: -22
[108742.480842] mwl_rx_recv: ieee80211 phy0: 58:c3:8b:ec:66:82 - addba.resp.capab=0x202
[111659.302524] mwl_rx_recv: ieee80211 phy0: 0c:8b:fd:08:09:71 - addba.resp.capab=0x1006
[114157.963627] mwl_rx_recv: ieee80211 phy0: 5c:0a:5b:79:ae:68 - addba.resp.capab=0x202
[164362.167093] mwl_rx_recv: ieee80211 phy0: 0c:8b:fd:08:09:71 - addba.resp.capab=0x1002
Chadster766 commented 8 years ago

I had the delayed performance issue that's been mentioned. I haven't tested with the pcmd->cmd_hdr.result checks removed.

I'm hoping the pcmd->cmd_hdr.result checks removal solves this issue which I will start testing.

balintkozma commented 8 years ago

@Chadster766: Finally it turned out, that it solves only the printouts basically. @johnnysl pointed out what I missed during my tests (at least 1-1.5 day uptime) I have the same issue, as before.

Chadster766 commented 8 years ago

Thanks for the update.

Chadster766 commented 8 years ago

I'm actively testing the driver with removal of the pcmd->cmd_hdr.result checks, kept spinlock and kept mdelay.

I built a 4.2.4 kernel and modules with latencytop support to help troubleshoot the issue. This latency support disables SMP which might have some interesting results.

Chadster766 commented 8 years ago

latencytop didn't have any useful output. 1 WRT1900AC V2 and 2 WRT1900AC V1 in operation with the changes.

jbsky commented 8 years ago

With new driver, ampdu still return an error code.

Mar 25 13:58:00 WRT1900AC hostapd: wlan1: STA 00:cd:fe:8f:95:55 IEEE 802.11: authenticated Mar 25 13:58:00 WRT1900AC hostapd: wlan1: STA 00:cd:fe:8f:95:55 IEEE 802.11: associated (aid 3) Mar 25 13:58:00 WRT1900AC hostapd: wlan1: STA 00:cd:fe:8f:95:55 RADIUS: starting accounting session C02D3097-00000002 Mar 25 13:58:00 WRT1900AC hostapd: wlan1: STA 00:cd:fe:8f:95:55 WPA: pairwise key handshake completed (RSN) Mar 25 13:58:02 WRT1900AC kernel: [10135.436016] ieee80211 phy1: check ba result error 1 Mar 25 13:58:02 WRT1900AC kernel: [10135.441198] ieee80211 phy1: ampdu start error code: -22 Mar 25 13:58:02 WRT1900AC kernel: [10135.485993] ieee80211 phy1: check ba result error 1 Mar 25 13:58:02 WRT1900AC kernel: [10135.491012] ieee80211 phy1: ampdu start error code: -22 Mar 25 13:58:02 WRT1900AC kernel: [10135.536001] ieee80211 phy1: check ba result error 1 Mar 25 13:58:02 WRT1900AC kernel: [10135.540972] ieee80211 phy1: ampdu start error code: -22

Iperf from Windows 7 with Intel AC 7260 to WR1900AC v1

Server listening on 5201(2,4Ghz)

Accepted connection from 192.168.10.7, port 51980 [ 5] local 192.168.10.10 port 5201 connected to 192.168.10.7 port 51981 [ ID] Interval Transfer Bandwidth [ 5] 0.00-1.00 sec 4.29 MBytes 36.0 Mbits/sec [ 5] 1.00-2.00 sec 5.61 MBytes 47.0 Mbits/sec [ 5] 2.00-3.00 sec 5.57 MBytes 46.7 Mbits/sec [ 5] 3.00-4.00 sec 5.54 MBytes 46.5 Mbits/sec [ 5] 4.00-5.00 sec 5.58 MBytes 46.8 Mbits/sec [ 5] 5.00-6.00 sec 5.64 MBytes 47.3 Mbits/sec [ 5] 6.00-7.00 sec 5.54 MBytes 46.5 Mbits/sec [ 5] 7.00-8.00 sec 3.95 MBytes 33.1 Mbits/sec [ 5] 8.00-9.00 sec 2.84 MBytes 23.8 Mbits/sec [ 5] 9.00-10.00 sec 2.49 MBytes 20.9 Mbits/sec [ 5] 10.00-10.20 sec 906 KBytes 36.3 Mbits/sec

[ ID] Interval Transfer Bandwidth [ 5] 0.00-10.20 sec 48.0 MBytes 39.5 Mbits/sec sender

[ 5] 0.00-10.20 sec 47.9 MBytes 39.4 Mbits/sec receiver

Server listening on 5201(5Ghz)

Accepted connection from 192.168.10.7, port 51983 [ 5] local 192.168.10.10 port 5201 connected to 192.168.10.7 port 51984 [ ID] Interval Transfer Bandwidth [ 5] 0.00-1.00 sec 3.18 MBytes 26.7 Mbits/sec [ 5] 1.00-2.00 sec 4.56 MBytes 38.2 Mbits/sec [ 5] 2.00-3.00 sec 4.79 MBytes 40.2 Mbits/sec [ 5] 3.00-4.00 sec 4.78 MBytes 40.1 Mbits/sec [ 5] 4.00-5.00 sec 4.51 MBytes 37.9 Mbits/sec [ 5] 5.00-6.00 sec 4.57 MBytes 38.3 Mbits/sec [ 5] 6.00-7.00 sec 4.60 MBytes 38.6 Mbits/sec [ 5] 7.00-8.00 sec 4.56 MBytes 38.2 Mbits/sec [ 5] 8.00-9.00 sec 4.77 MBytes 40.0 Mbits/sec [ 5] 9.00-10.00 sec 4.65 MBytes 39.0 Mbits/sec [ 5] 10.00-10.20 sec 1.01 MBytes 41.5 Mbits/sec

[ ID] Interval Transfer Bandwidth [ 5] 0.00-10.20 sec 46.0 MBytes 37.8 Mbits/sec sender [ 5] 0.00-10.20 sec 46.0 MBytes 37.8 Mbits/sec receiver

Really BAD!

Chadster766 commented 8 years ago

Yes the driver still errors on the ampdu check without the chadster patch.

I saw the same iperf results. You will be surprised if your run the same test on the 5Ghz but with the "-P 6" switch added onto the iperf command.

mystica555 commented 8 years ago

I've actually gone back to using my crap old TP-Link TL-WR702N in lieu of the wifi on the wrt1200ac. Its that bad.

Anyone want a wrt1200ac? I'll sell it to you for just enough to buy myself a WiTi board...

MIke

On Fri, Mar 25, 2016 at 3:45 PM, jbsky notifications@github.com wrote:

With new driver, ampdu still return an error code.

Mar 25 13:58:00 WRT1900AC hostapd: wlan1: STA 00:cd:fe:8f:95:55 IEEE 802.11: authenticated Mar 25 13:58:00 WRT1900AC hostapd: wlan1: STA 00:cd:fe:8f:95:55 IEEE 802.11: associated (aid 3) Mar 25 13:58:00 WRT1900AC hostapd: wlan1: STA 00:cd:fe:8f:95:55 RADIUS: starting accounting session C02D3097-00000002 Mar 25 13:58:00 WRT1900AC hostapd: wlan1: STA 00:cd:fe:8f:95:55 WPA: pairwise key handshake completed (RSN) Mar 25 13:58:02 WRT1900AC kernel: [10135.436016] ieee80211 phy1: check ba result error 1 Mar 25 13:58:02 WRT1900AC kernel: [10135.441198] ieee80211 phy1: ampdu start error code: -22 Mar 25 13:58:02 WRT1900AC kernel: [10135.485993] ieee80211 phy1: check ba result error 1 Mar 25 13:58:02 WRT1900AC kernel: [10135.491012] ieee80211 phy1: ampdu start error code: -22 Mar 25 13:58:02 WRT1900AC kernel: [10135.536001] ieee80211 phy1: check ba result error 1 Mar 25 13:58:02 WRT1900AC kernel: [10135.540972] ieee80211 phy1: ampdu start error code: -22

Iperf from Windows 7 with Intel AC 7260 to WR1900AC v1 Accepted connection from 192.168.10.7, port 51980 [ 5] local 192.168.10.10 port 5201 connected to 192.168.10.7 port 51981 [ ID] Interval Transfer Bandwidth [ 5] 0.00-1.00 sec 4.29 MBytes 36.0 Mbits/sec [ 5] 1.00-2.00 sec 5.61 MBytes 47.0 Mbits/sec [ 5] 2.00-3.00 sec 5.57 MBytes 46.7 Mbits/sec [ 5] 3.00-4.00 sec 5.54 MBytes 46.5 Mbits/sec [ 5] 4.00-5.00 sec 5.58 MBytes 46.8 Mbits/sec [ 5] 5.00-6.00 sec 5.64 MBytes 47.3 Mbits/sec [ 5] 6.00-7.00 sec 5.54 MBytes 46.5 Mbits/sec [ 5] 7.00-8.00 sec 3.95 MBytes 33.1 Mbits/sec [ 5] 8.00-9.00 sec 2.84 MBytes 23.8 Mbits/sec [ 5] 9.00-10.00 sec 2.49 MBytes 20.9 Mbits/sec

[ 5] 10.00-10.20 sec 906 KBytes 36.3 Mbits/sec

[ ID] Interval Transfer Bandwidth [ 5] 0.00-10.20 sec 48.0 MBytes 39.5 Mbits/sec sender [ 5] 0.00-10.20 sec 47.9 MBytes 39.4 Mbits/sec receiver Server listening on 5201

Accepted connection from 192.168.10.7, port 51983 [ 5] local 192.168.10.10 port 5201 connected to 192.168.10.7 port 51984 [ ID] Interval Transfer Bandwidth [ 5] 0.00-1.00 sec 3.18 MBytes 26.7 Mbits/sec [ 5] 1.00-2.00 sec 4.56 MBytes 38.2 Mbits/sec [ 5] 2.00-3.00 sec 4.79 MBytes 40.2 Mbits/sec [ 5] 3.00-4.00 sec 4.78 MBytes 40.1 Mbits/sec [ 5] 4.00-5.00 sec 4.51 MBytes 37.9 Mbits/sec [ 5] 5.00-6.00 sec 4.57 MBytes 38.3 Mbits/sec [ 5] 6.00-7.00 sec 4.60 MBytes 38.6 Mbits/sec [ 5] 7.00-8.00 sec 4.56 MBytes 38.2 Mbits/sec [ 5] 8.00-9.00 sec 4.77 MBytes 40.0 Mbits/sec [ 5] 9.00-10.00 sec 4.65 MBytes 39.0 Mbits/sec

[ 5] 10.00-10.20 sec 1.01 MBytes 41.5 Mbits/sec

[ ID] Interval Transfer Bandwidth [ 5] 0.00-10.20 sec 46.0 MBytes 37.8 Mbits/sec sender [ 5] 0.00-10.20 sec 46.0 MBytes 37.8 Mbits/sec receiver

Really BAD!

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/kaloz/mwlwifi/issues/41#issuecomment-201527781

jbsky commented 8 years ago

@Chadster766 Nothing change,

Connecting to host 192.168.10.10, port 5201 [ 4] local 192.168.10.7 port 54973 connected to 192.168.10.10 port 5201 [ 6] local 192.168.10.7 port 54974 connected to 192.168.10.10 port 5201 [ 8] local 192.168.10.7 port 54975 connected to 192.168.10.10 port 5201 [ 10] local 192.168.10.7 port 54976 connected to 192.168.10.10 port 5201 [ 12] local 192.168.10.7 port 54977 connected to 192.168.10.10 port 5201 [ 14] local 192.168.10.7 port 54978 connected to 192.168.10.10 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 1.38 MBytes 11.5 Mbits/sec
[ 6] 0.00-1.00 sec 1.38 MBytes 11.5 Mbits/sec
[ 8] 0.00-1.00 sec 1.25 MBytes 10.5 Mbits/sec
[ 10] 0.00-1.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 12] 0.00-1.00 sec 256 KBytes 2.10 Mbits/sec
[ 14] 0.00-1.00 sec 1.25 MBytes 10.5 Mbits/sec
[SUM] 0.00-1.00 sec 6.62 MBytes 55.6 Mbits/sec

[ 4] 1.00-2.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 6] 1.00-2.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 8] 1.00-2.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 10] 1.00-2.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 12] 1.00-2.00 sec 128 KBytes 1.05 Mbits/sec
[ 14] 1.00-2.00 sec 1.12 MBytes 9.44 Mbits/sec
[SUM] 1.00-2.00 sec 5.75 MBytes 48.2 Mbits/sec

[ 4] 2.00-3.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 6] 2.00-3.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 8] 2.00-3.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 10] 2.00-3.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 12] 2.00-3.00 sec 256 KBytes 2.10 Mbits/sec
[ 14] 2.00-3.00 sec 1.00 MBytes 8.39 Mbits/sec
[SUM] 2.00-3.00 sec 5.50 MBytes 46.1 Mbits/sec

[ 4] 3.00-4.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 6] 3.00-4.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 8] 3.00-4.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 10] 3.00-4.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 12] 3.00-4.00 sec 384 KBytes 3.15 Mbits/sec
[ 14] 3.00-4.00 sec 1.12 MBytes 9.44 Mbits/sec
[SUM] 3.00-4.00 sec 6.00 MBytes 50.3 Mbits/sec

[ 4] 4.00-5.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 6] 4.00-5.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 8] 4.00-5.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 10] 4.00-5.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 12] 4.00-5.00 sec 384 KBytes 3.15 Mbits/sec
[ 14] 4.00-5.00 sec 1.12 MBytes 9.44 Mbits/sec
[SUM] 4.00-5.00 sec 5.75 MBytes 48.2 Mbits/sec

[ 4] 5.00-6.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 6] 5.00-6.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 8] 5.00-6.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 10] 5.00-6.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 12] 5.00-6.00 sec 640 KBytes 5.24 Mbits/sec
[ 14] 5.00-6.00 sec 1.00 MBytes 8.39 Mbits/sec
[SUM] 5.00-6.00 sec 5.88 MBytes 49.3 Mbits/sec

[ 4] 6.00-7.00 sec 1.12 MBytes 9.44 Mbits/sec
[ 6] 6.00-7.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 8] 6.00-7.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 10] 6.00-7.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 12] 6.00-7.00 sec 640 KBytes 5.24 Mbits/sec
[ 14] 6.00-7.00 sec 1.12 MBytes 9.44 Mbits/sec
[SUM] 6.00-7.00 sec 5.88 MBytes 49.3 Mbits/sec

[ 4] 7.00-8.00 sec 896 KBytes 7.34 Mbits/sec
[ 6] 7.00-8.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 8] 7.00-8.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 10] 7.00-8.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 12] 7.00-8.00 sec 768 KBytes 6.29 Mbits/sec
[ 14] 7.00-8.00 sec 896 KBytes 7.34 Mbits/sec
[SUM] 7.00-8.00 sec 5.50 MBytes 46.1 Mbits/sec

[ 4] 8.00-9.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 6] 8.00-9.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 8] 8.00-9.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 10] 8.00-9.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 12] 8.00-9.00 sec 768 KBytes 6.29 Mbits/sec
[ 14] 8.00-9.00 sec 1.00 MBytes 8.39 Mbits/sec
[SUM] 8.00-9.00 sec 5.75 MBytes 48.2 Mbits/sec

[ 4] 9.00-10.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 6] 9.00-10.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 8] 9.00-10.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 10] 9.00-10.00 sec 1.00 MBytes 8.39 Mbits/sec
[ 12] 9.00-10.00 sec 896 KBytes 7.34 Mbits/sec
[ 14] 9.00-10.00 sec 1.00 MBytes 8.39 Mbits/sec
[SUM] 9.00-10.00 sec 5.88 MBytes 49.3 Mbits/sec

[ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 10.8 MBytes 9.02 Mbits/sec sender [ 4] 0.00-10.00 sec 10.7 MBytes 8.96 Mbits/sec receiver [ 6] 0.00-10.00 sec 10.8 MBytes 9.02 Mbits/sec sender [ 6] 0.00-10.00 sec 10.7 MBytes 8.96 Mbits/sec receiver [ 8] 0.00-10.00 sec 10.8 MBytes 9.02 Mbits/sec sender [ 8] 0.00-10.00 sec 10.7 MBytes 8.95 Mbits/sec receiver [ 10] 0.00-10.00 sec 10.6 MBytes 8.91 Mbits/sec sender [ 10] 0.00-10.00 sec 10.6 MBytes 8.88 Mbits/sec receiver [ 12] 0.00-10.00 sec 5.00 MBytes 4.19 Mbits/sec sender [ 12] 0.00-10.00 sec 4.89 MBytes 4.10 Mbits/sec receiver [ 14] 0.00-10.00 sec 10.6 MBytes 8.91 Mbits/sec sender [ 14] 0.00-10.00 sec 10.6 MBytes 8.86 Mbits/sec receiver [SUM] 0.00-10.00 sec 58.5 MBytes 49.1 Mbits/sec sender [SUM] 0.00-10.00 sec 58.1 MBytes 48.7 Mbits/sec receiver

iperf Done.

I prefer previous release in term of performance, but this release seems to bring a bit stability (less lag). It's just an impression

Chadster766 commented 8 years ago

Example: iperf3 -c 192.168.200.3 -B 192.168.200.11 -P 6

5Ghz Results: [SUM] 0.00-10.00 sec 283 MBytes 237 Mbits/sec sender [SUM] 0.00-10.00 sec 283 MBytes 237 Mbits/sec receiver

mystica555 commented 8 years ago

My 5ghz results are limited to a Galaxy Note 3, LG G3, and XboxOne.

None of these devices is a 2x2 device; none of these devices on the wrt1200ac can surpass 15mbit on 5ghz. My internet is '40meg' from Centurylink; real TCP speed ~36.5 Megabit. With my tplink, on 2.4ghz, forcing 40mhz channel (ch8) it's able to shove the full 36.5 to any device in my house.. In 2.4ghz.

How much / what specifically did your driver patch fix, compared to whats currently in OpenWRT Trunk? I'll take the time to try and compile it myself if I can get some concrete indication that doing so will guarantee me similarly good performance on my wifi with the wrt1200ac.

Thanks,

Mike

On Fri, Mar 25, 2016 at 4:23 PM, Chad McCue notifications@github.com wrote:

Example: iperf3 -c 192.168.200.3 -B 192.168.200.11 -P 6

5Ghz Results: [SUM] 0.00-10.00 sec 283 MBytes 237 Mbits/sec sender [SUM] 0.00-10.00 sec 283 MBytes 237 Mbits/sec receiver

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/kaloz/mwlwifi/issues/41#issuecomment-201550151

mystica555 commented 8 years ago

On Fri, Mar 25, 2016 at 4:29 PM, Mike Hodson mystica@gmail.com wrote:

How much / what specifically did your driver patch fix, compared to whats currently in

(and on the subject of OpenWRT, WTF did they do that a recent sysupgrade decided to barf upon the ubifs partition layout and cause a temporary brick til I make my way out of my house and grab a working TTL<>usbserial adapter; my old Sparkfun FTDIchip based one exhibits a brief light of power then deadness thereafter once plugged into the USB cable end)

Chadster766 commented 8 years ago

Honestly I don't know if my driver patch actually fixed anything but I did have good stability with it. Currently I'm testing without the patch to evaluate the driver version.

I see the same performance you do. The results are different only because the "-P 6" uses six streams and combines there total throughput.

yuhhaurlin commented 8 years ago
  1. The new driver fixs Tx throughput becomes lower after runing for a while and multicat udp out od order (also running for a while).
  2. For this problem, please check new firmware, and give me clear test setup.
mystica555 commented 8 years ago

yuhhaurlin: My issue is that tx is -never- fast; and I always go by single-stream speed because I expect the full capacity of my internet to be faithfully sent to 1 device at any single time, or CSMA/CA does its job and reliably separates the multiple concurrent devices into reasonably good ability to share said 36.5mbit.

There is nothing "on the lan" of importance except a printer; so the wifi is very much 'how fast can my internet be'.

There has still been the continuing issue of "my device is connected but no traffic can pass" with the Note 3. This is a Murata wifi chip if memory serves; I'll have to check ARP and see what comes out of an OUI database.. It's the roommate's primary device and is used far more often than either the xboxes or the 2.4ghz Intel chip wifi from her Dell laptop.

If this device fails, repeatedly, I get yelled at :) "FIX IT, Mister IT department!"

On Fri, Mar 25, 2016 at 4:43 PM, yuhhaurlin notifications@github.com wrote:

  1. The new driver fixs Tx throughput becomes lower after runing for a while and multicat udp out od order (also running for a while).
  2. For this problem, please check new firmware, and give me clear test setup.

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/kaloz/mwlwifi/issues/41#issuecomment-201560952

yuhhaurlin commented 8 years ago

Can you try the new firmware?

yuhhaurlin commented 8 years ago

BTW, what is the throughput number with stock firmware?

mystica555 commented 8 years ago

I just realized I flashed my Caiman with Cobra firmware (and filed an openwrt bug to have actual router names included in filenames to prevent this C-similarity next time)

So I need to purchase a TTL<>USB converter to unbrick the filesystem screwup.

I'll let you know approximately monday or tuesday next week once I've completed this.

On Fri, Mar 25, 2016 at 5:00 PM, yuhhaurlin notifications@github.com wrote:

BTW, what is the throughput number with stock firmware?

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/kaloz/mwlwifi/issues/41#issuecomment-201568742

yuhhaurlin commented 8 years ago

http://www.dd-wrt.com/phpBB2/viewtopic.php?t=300267

wongsyrone commented 8 years ago

.17 on WRT1900ac v1 just keeping power on about 1d 7h 2m, the same issue still presents. [108863.611277] ieee80211 phy0: check ba result error 1 [108863.616390] ieee80211 phy0: ampdu start error code: -22 [108863.651262] ieee80211 phy0: check ba result error 1 [108863.656365] ieee80211 phy0: ampdu start error code: -22 [108863.751298] ieee80211 phy0: check ba result error 1 [108863.756414] ieee80211 phy0: ampdu start error code: -22 [108863.841286] ieee80211 phy0: check ba result error 1 [108863.846803] ieee80211 phy0: ampdu start error code: -22 [108863.891286] ieee80211 phy0: check ba result error 1 [108863.896461] ieee80211 phy0: ampdu start error code: -22 [108863.941264] ieee80211 phy0: check ba result error 1 [108863.946365] ieee80211 phy0: ampdu start error code: -22 [108863.981265] ieee80211 phy0: check ba result error 1 [108863.986384] ieee80211 phy0: ampdu start error code: -22 [108864.091423] ieee80211 phy0: check ba result error 1 [108864.096529] ieee80211 phy0: ampdu start error code: -22 [108864.131248] ieee80211 phy0: check ba result error 1 [108864.136327] ieee80211 phy0: ampdu start error code: -22 [108864.171267] ieee80211 phy0: check ba result error 1 [108864.176342] ieee80211 phy0: ampdu start error code: -22 [108864.721273] ieee80211 phy0: check ba result error 1 [108864.726342] ieee80211 phy0: ampdu start error code: -22

yuhhaurlin commented 8 years ago

Does these messages affect normal operation?

wongsyrone commented 8 years ago

Wifi came down and up again and it seems no impact on performance until now.

yuhhaurlin commented 8 years ago

Thanks.

yuhhaurlin commented 8 years ago

If these messages won't affect normal operation and performance, I will close it.

NemoAlex commented 8 years ago

With all due respect, I think we should figure out why this error occurred and do our best to make it right. Shall we?

yuhhaurlin commented 8 years ago

Firmware needs time to destroy previous BA session, it is possible to display this kind of messages. However if BA can be established finally, we can treat it as some kind of warning messages.

johnnysl commented 8 years ago

Ipad 2 still causes these errors on 5GHZ, and as said numerous times, further communication is then no longer possible, and i need to disconnect and reconnect to get wifi going again. not sure if that are 2 issues or 1 issue, but they are surely related.

johnnysl commented 8 years ago

Would it be possible to add the mac-acdres of the client causing the alert? Just to be sure that the connectivity issue i sometimes see is or is not related to the BA error?

bmork commented 8 years ago

johnnysl notifications@github.com writes:

Would it be possible to add the mac-acdres of the client causing the alert? Just to be sure that the connectivity issue i sometimes see is or is not related to the BA error?

@johnnysl You can try something like this: https://github.com/bmork/mwlwifi/commit/bmork-check-ba-logging

But the correct thing to do is more likely to drop the logging altogether (or better: demote it to debug level). I'm convinced @yuhhaurlin is right. This is not a symptom of a real problem. It is merely a temporary failure to enable A-MPDU. It does not break anything and it will automatically resolve itself after a while. There is a theoretical performance impact, but the error occurs too rarely for that to be any more noticable than e.g random radio noise.

As it is now, these log messages are harmful because users will tend to think they are related to any problems they are having, and focus only on this unrelated addba failure instead of debugging the real problem.

So my vote is in favour of demoting this message to debug level.

yuhhaurlin commented 8 years ago

I will change it to debug level with mac address later. Thanks.

johnnysl commented 8 years ago

Just trying to figure out why my ipad2 sometimes had a "frozen" wifi connection. Wih which i mean that it has good wifi connection, but no data traffic is possible, until disconnect/connect. Logs only show the BA error, so it is human to connect the two, even though it might not be related at all.

Thanks for adding the mac and dropping it to debug level, that should help me trace it.