From: Ben Greear <greearb@candelatech.com>
To: Adrian Chadd <adrian@freebsd.org>,
Sebastian Gottschall <s.gottschall@newmedia-net.de>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Problem with 9984 in routed mode with 512b frames.
Date: Mon, 20 May 2019 12:54:16 -0700 [thread overview]
Message-ID: <41a3c98c-4cea-3d85-cc70-d153d18dc672@candelatech.com> (raw)
In-Reply-To: <CAJ-VmonsmNVhzge5jiOVhJn13B8oWEop8zr=Xk+dgYZDTaGU+Q@mail.gmail.com>
On 5/20/19 12:25 PM, Adrian Chadd wrote:
> On Mon, 20 May 2019 at 09:59, Sebastian Gottschall
> <s.gottschall@newmedia-net.de> wrote:
>
>
>> the curious thing is still that the fallback code applies only for 2.4
>> ghz so it would never have affected 802.11ac
>
> Hm, does RC fall back to 11na or 11a rates when doing 11ac? (in 5G
> mode.) It's good to know fixing that would fix it in 2.4GHz operation
> but yeah, I wonder about RC in 5G.
It appears the rate-ctrl tries to fall to CCK 2Mbps or 1Mbps and skips a/g rates. /n
rates are a subset of VHT, so those are used as part of normal VHT rate-ctrl.
I have no explanation for why I saw the tx-hang in stock-ish firmware, which indeed
should not have tried to use any a/g rates in 5Ghz. The high-level failure looked exactly like
what I eventually debugged as falling back to /a rates in my firmware, for what that
is worth.
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-20 19:54 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
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 [this message]
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=41a3c98c-4cea-3d85-cc70-d153d18dc672@candelatech.com \
--to=greearb@candelatech.com \
--cc=adrian@freebsd.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.