Looks like you got it right. The period you traced doesn't seem to cover
any of the block ack session timeouts, but I do see this:
[ 225.269777] wlan0: release an RX reorder frame due to timeout on earlier frames
[ 243.869220] wlan0: unexpected AddBA Req from 1c:c6:3c:1f:50:68 on tid 0
[ 243.869233] wlan0: Rx BA session stop requested for 1c:c6:3c:1f:50:68 tid 0 recipient reason: 32
[ 243.869250] wlan0: Rx A-MPDU request on tid 0 result 0
[ 252.254013] brcmsmac bcma0:0: brcms_c_ampdu_dotxstatus_complete: Pkt tx suppressed, illegal channel possibly 13
<snip repeated messages>
[ 259.798966] wlan0: release an RX reorder frame due to timeout on earlier frames
<snip repeated messages>
[ 265.193640] wlan0: unexpected AddBA Req from 1c:c6:3c:1f:50:68 on tid 0
[ 265.193648] wlan0: Rx BA session stop requested for 1c:c6:3c:1f:50:68 tid 0 recipient reason: 32
[ 265.193663] wlan0: Rx A-MPDU request on tid 0 result 0
Does something in this time frame correspond to your loss in
connectivity? The number of packets being sent and received varies some
throughout the trace but generally stays pretty low. It never completely
stops though.
I am currently not able to reproduce a complete loss of connectivity.
I fear it is a heisenbug. After turning the tracing off I was able to
reproduce it very easily.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
