From: Ben Greear <greearb@candelatech.com>
To: Sebastian Gottschall <s.gottschall@newmedia-net.de>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: Problem with 9984 in routed mode with 512b frames.
Date: Wed, 15 May 2019 05:20:20 -0700 [thread overview]
Message-ID: <10ed4e39-4364-c8ef-2b38-15ea7672ad94@candelatech.com> (raw)
In-Reply-To: <daaad6d3-cf60-4ddc-af20-279a0cbbbe0c@newmedia-net.de>
On 05/14/2019 09:26 PM, Sebastian Gottschall wrote:
> can you send me a detailed instruction for testing this on my devices? so which commands have been used for generating the traffic etc. (iperf3?)
I am using our own traffic generator, but I imagine iperf3 should work fine too.
I am testing on x86-64 and so forth. Maybe you can test with UDP small-packet load on your platform
in routed mode (ie, external iperf generator through your AP) and see if you see issues?
From debugging yesterday, I see a lot of tx-hang notifications in the firmware, and
I also believe I saw it trying to transmit with a 0 rate-indx, which is 11Mbps CCK,
which is invalid for 5Ghz. I'll be debugging that more today. I don't know if stock
firmware fails for the same reasons, but the symptom looked the same.
Thanks,
Ben
>
> Sebastian
>
> Am 15.05.2019 um 03:52 schrieb Ben Greear:
>> Hello,
>>
>> I found a strange issue and curious if someone has seen similar.
>>
>> I made an AP where the AP interface acts as a routed interface. I generate
>> traffic through another interface in the router. When sending 300Mbps of 512 byte
>> UDP payloads, in the downstream direction, and with the station being a 1x1 /AC device,
>> then the AP NIC appears to mostly lock up within about 1 minute. I still see beacons, but no
>> data frames. In some cases, I reproduced with very slow speed traffic as well.
>>
>> I tried using a mostly un-modified firmware (ie, similar to upstream QCA), as well as my
>> hacked upon firmware, and all act similarly. I'm using the 4.20 kernel, but at least for now,
>> it does not appear to be a kernel issue.
>>
>> If I use larger MTU sized frames, or have a 2x2 station instead of 1x1 then it is much harder
>> to reproduce (and maybe cannot be reproduced). Also, when generating traffic directly on
>> the AP device instead of using the routed interface as a traffic source, it is harder to
>> reproduce.
>>
>> Thanks,
>> Ben
>>
>
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2019-05-15 12:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 1:52 Problem with 9984 in routed mode with 512b frames Ben Greear
2019-05-15 4:26 ` Sebastian Gottschall
2019-05-15 12:20 ` Ben Greear [this message]
2019-05-15 12:26 ` Sebastian Gottschall
2019-05-15 13:00 ` Ben Greear
2019-05-16 19:40 ` Ben Greear
2019-05-16 19:55 ` Adrian Chadd
2019-05-16 20:09 ` Ben Greear
2019-05-16 20:16 ` Adrian Chadd
2019-05-16 20:20 ` Ben Greear
2019-05-16 20:35 ` Adrian Chadd
2019-05-17 4:21 ` Sebastian Gottschall
2019-05-17 11:48 ` Ben Greear
2019-05-17 15:05 ` Sebastian Gottschall
2019-05-17 15:47 ` Adrian Chadd
2019-05-17 16:00 ` Ben Greear
2019-05-17 16:12 ` Adrian Chadd
2019-05-20 16:59 ` Sebastian Gottschall
2019-05-20 19:25 ` Adrian Chadd
2019-05-20 19:54 ` Ben Greear
2019-05-20 16:58 ` 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=10ed4e39-4364-c8ef-2b38-15ea7672ad94@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=s.gottschall@newmedia-net.de \
/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