From: Ben Greear <greearb@candelatech.com>
To: Karthikeyan Periyasamy <periyasa@codeaurora.org>,
ath10k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Revert "ath10k: send (re)assoc peer command when NSS changed"
Date: Mon, 26 Feb 2018 07:56:46 -0800 [thread overview]
Message-ID: <aedd8281-ee1b-e5ae-2521-fd3a7a221dd6@candelatech.com> (raw)
In-Reply-To: <1519625792-12010-1-git-send-email-periyasa@codeaurora.org>
On 02/25/2018 10:16 PM, Karthikeyan Periyasamy wrote:
> This reverts commit 55884c045d31a29cf69db8332d1064a1b61dd159.
>
> When Ath10k is in AP mode and an unassociated STA sends a VHT action frame
> (Operating Mode Notification for the NSS change) periodically to AP this causes
> ath10k to call ath10k_station_assoc() which sends WMI_PEER_ASSOC_CMDID during
> NSS update. Over the time (with a certain client it can happen within 15 mins
> when there are over 500 of these VHT action frames) continuous calls of
> WMI_PEER_ASSOC_CMDID cause firmware to assert due to resource exhaust.
Can you share exactly which resource the firmware ran out of? It would seem to
be a FW bug if it is leaking, so maybe it can be fixed as well...
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:[~2018-02-26 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 6:16 [PATCH] Revert "ath10k: send (re)assoc peer command when NSS changed" Karthikeyan Periyasamy
2018-02-26 8:45 ` Adrian Chadd
2018-02-26 10:41 ` periyasa
2018-02-26 15:56 ` Ben Greear [this message]
2018-02-26 17:06 ` periyasa
2018-02-26 19:21 ` Adrian Chadd
2018-02-27 4:00 ` periyasa
2018-02-26 19:17 ` Peter Oh
2018-02-27 8:49 ` fixed bit rate 9Mbps set as 24Mbps in g mode(legacy) KAVITA MATHUR
2018-02-27 16:41 ` Ben Greear
2018-02-28 4:03 ` KAVITA MATHUR
2018-02-28 19:43 ` Ben Greear
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=aedd8281-ee1b-e5ae-2521-fd3a7a221dd6@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=periyasa@codeaurora.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