From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Ben Greear <greearb@candelatech.com>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>
Subject: Re: ath9k will not tx packets sometimes.
Date: Mon, 29 Jan 2018 22:47:25 +0100 [thread overview]
Message-ID: <87d11stk0i.fsf@toke.dk> (raw)
In-Reply-To: <f021a32c-6f12-1cfe-970f-eae7dd334416@candelatech.com>
Ben Greear <greearb@candelatech.com> writes:
> On 01/27/2018 05:11 AM, Toke H=C3=B8iland-J=C3=B8rgensen wrote:
>> Ben Greear <greearb@candelatech.com> writes:
>>
>>> I'm doing a test with 200 virtual stations on each of 6 ath9k radios.
>>>
>>> When I configure stations for DHCP, I see cases where stations on a par=
ticular
>>> radio will not transmit anything sometimes. I see no 'XMIT' logs that =
show indication of
>>> frames being received in the driver from the upper stack, but if I use =
'tshark' on
>>> a station interface, it shows frames being 'transmitted'.
>>>
>>> I do, however, see this, which looks like it might show
>>> an issue. It looks like whatever 'aqm' is, it has an ever expanding nu=
mber
>>> of backlog packets:
>>
>> The aqm is the intermediate queues in mac80211. So this indicates that
>> the driver is not pulling packets for transmission.
>>
>> With that many stations, I wonder whether it is due to the airtime
>> fairness scheduler throttling the station? What is the contents of
>> debug/ieee80211/wiphy2/netdev\:sta30194/stations/00\:0e\:8e\:69\:b8\:f7/=
airtime
>> while the station is not transmitting? And is it all stations on that
>> particular radio, or only some of them?
>
> Here is the output of airtime and aqm on a hung station:
>
> # cat /debug/ieee80211/wiphy0/netdev\:sta10057/stations/00\:0e\:8e\:50\:7=
4\:8a/airtime
> RX: 83706 us
> TX: 4202 us
> Deficit: VO: 198 us VI: 300 us BE: -8306 us BK: 300 us
Right. This looks like incoming traffic is depleting the airtime quantum
faster than it can be replenished by the scheduler, which means that the
station gets completely starved.
Could you try turning off the airtime scheduler?
echo 0 > /sys/kernel/debug/ieee80211/wiphy0/ath9k/airtime_flags
and see if the problem goes away.
If it does, please check if the problem persists when setting
airtime_flags to 1 (which means only include TX airtime).
-Toke
next prev parent reply other threads:[~2018-01-29 21:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 22:53 ath9k will not tx packets sometimes Ben Greear
2018-01-27 13:11 ` Toke Høiland-Jørgensen
2018-01-29 21:34 ` Ben Greear
2018-01-29 21:47 ` Toke Høiland-Jørgensen [this message]
2018-01-29 21:54 ` Ben Greear
2018-01-29 22:35 ` Toke Høiland-Jørgensen
2018-01-29 23:00 ` Ben Greear
2018-01-30 12:07 ` Toke Høiland-Jørgensen
2018-01-30 17:32 ` Ben Greear
2018-01-30 18:55 ` Toke Høiland-Jørgensen
2018-01-30 20:09 ` Sebastian Gottschall
2018-01-31 11:50 ` Toke Høiland-Jørgensen
2018-01-31 13:37 ` Sebastian Gottschall
2018-01-31 13:46 ` Toke Høiland-Jørgensen
2018-01-31 14:52 ` Sebastian Gottschall
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=87d11stk0i.fsf@toke.dk \
--to=toke@toke.dk \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).