From: 김광민 <gwondori@nimbus.kr>
To: ath10k@lists.infradead.org
Cc: 강경완 <bigskang@nimbus.kr>
Subject: All '0' in agg_status
Date: Tue, 17 Jan 2017 20:30:22 +0900 (KST) [thread overview]
Message-ID: <388374faef47fee11e7866ad71211bc@cvweb09.wmail.nhnsystem.com> (raw)
In-Reply-To: <65667ea2aa7e867acb684cb64c1d07@cvweb11.wmail.nhnsystem.com>
[-- Attachment #1.1: Type: text/plain, Size: 3566 bytes --]
Very rarely, I experience the problem that packets are serious dropped even though all wireless states(iwconfig, iw wlan0 info, fw_stats, etc.) are OK.
This problem occurs only after the AP and station are badly(?) connected, and once the connection is established normally, this problem does not occur on the good connection. And once this problem occurred, it won't be fixed by itself until the AP and the station are reconnected.
I have investigated and I have found two differences between the good connection and the bad connection.
The one is the error messages on dmesg,
<...>
[ 2826.432784] wlan0: Limiting TX power to 21 (24 - 3) dBm as advertised by 04:f0:21:20:38:09
[ 2827.296925] wlan0: Rx A-MPDU request on 04:f0:21:20:38:09 tid 0 result 0
[ 2827.297483] wlan0: Rx BA session stop requested for 04:f0:21:20:38:09 tid 0 recipient reason: 0 <--- from this line
[ 2827.297578] wlan0: Rx A-MPDU request on 04:f0:21:20:38:09 tid 0 result 0
[ 2827.298694] wlan0: Rx BA session stop requested for 04:f0:21:20:38:09 tid 0 recipient reason: 0
[ 2829.074439] wlan0: Rx A-MPDU request on 04:f0:21:20:38:09 tid 6 result 0 <-- to this line
<...>
The another difference is in "agg_status" file on Station side (/sys/kernel/debug/ieee80211/phy0/netdev:wlan0/stations/XX:XX:XX:XX:XX:XX/agg_status).
As my investigation, the file of the AP side always have one or two '1' at the second column. And the file of the station side without problem also have one or two '1'. But, there is no '1' in the file on the station where the problem occurred.
#more /sys/kernel/debug/ieee80211/phy0/netdev\:wlan0/stations/*/agg_status
next dialog_token: 0x1
TID RX DTKN SSN TX DTKN pending
00 0 0x00 0x000 0 0x00 000
01 0 0x00 0x000 0 0x00 000
02 0 0x00 0x000 0 0x00 000
03 0 0x00 0x000 0 0x00 000
04 0 0x00 0x000 0 0x00 000
05 0 0x00 0x000 0 0x00 000
06 0 0x00 0x000 0 0x00 000
07 0 0x00 0x000 0 0x00 000
08 0 0x00 0x000 0 0x00 000
09 0 0x00 0x000 0 0x00 000
10 0 0x00 0x000 0 0x00 000
11 0 0x00 0x000 0 0x00 000
12 0 0x00 0x000 0 0x00 000
13 0 0x00 0x000 0 0x00 000
14 0 0x00 0x000 0 0x00 000
15 0 0x00 0x000 0 0x00 000
Could you tell me what I have to do?
Should one more '1' exist at the second columns of "agg_status"? In other words, is it problem if there is no '1' in the second column of agg_status?
If you know how to fix this, please let me know that.
---------------
Kim Kwang Min
Mobile +82 010-5521-6393
Mail gwondori@nimbus.kr
[-- Attachment #2: Type: text/plain, Size: 146 bytes --]
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next parent reply other threads:[~2017-01-17 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65667ea2aa7e867acb684cb64c1d07@cvweb11.wmail.nhnsystem.com>
2017-01-17 11:30 ` 김광민 [this message]
2017-01-18 7:40 All '0' in agg_status Adrian Chadd
[not found] ` <328523ea1b53d27f8a72b776481c15dc@cvweb05.wmail.nhnsystem.com>
2017-01-19 10:26 ` Kwang Min Kim
2017-02-14 8:26 ` Kwang Min Kim
2017-02-14 15:09 ` Valo, Kalle
2017-02-15 10:36 ` Kwang Min Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=388374faef47fee11e7866ad71211bc@cvweb09.wmail.nhnsystem.com \
--to=gwondori@nimbus.kr \
--cc=ath10k@lists.infradead.org \
--cc=bigskang@nimbus.kr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox