From: James Prestwood <prestwoj@gmail.com>
To: shunsuke@nagashi.ma, Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
linux-kernel@vger.kernel.org, David Heidelberg <david@ixit.cz>,
Fabricio Akio <fabricioakio@gmail.com>
Subject: Re: [PATCH ath-next 3/3] wifi: ath10k: bring down a station vdev that never came up
Date: Mon, 19 Oct 2026 06:12:11 -0700 [thread overview]
Message-ID: <61207966-c403-441d-9019-583702833a7f@gmail.com> (raw)
In-Reply-To: <20261016-ath10k-series-v1-send-v1-3-c847697b3558@nagashi.ma>
Hi Shunsuke,
On 10/15/26 5:17 PM, Shunsuke Nagashima via B4 Relay wrote:
> From: Shunsuke Nagashima <shunsuke@nagashi.ma>
>
> When a connection attempt fails before the station vdev is brought up
> (authentication timeout, SAE failure, association rejected, or an Auth
> burst the AP never acknowledged), mac80211 removes the AP station and
> unassigns the channel context. ath10k deletes the peer and sends
> WMI_VDEV_STOP, but no WMI_VDEV_DOWN: for a station vdev that never came
> up, the down would only come from ath10k_bss_disassoc(), which a failed
> connection attempt never reaches.
>
> On WCN3990 firmware WLAN.HL.2.0.c10-00459 and c10-00236, the Auth frames
> of the next attempt on the same vdev are then not transmitted
> (management tx completion status "discard") until about 20 s after the
> first Auth frame of the failed attempt. In sniffer captures, 241 such
> holds ended 19.94-20.03 s after that frame. Some lasted longer (in one
> overnight run, 29 of 226 had not ended when the cycle ended), for
> example when user space gave up on the attempt during the hold. Probe
> requests still go out. The state belongs to the vdev: an attempt to
> another network (another BSS on the same AP) on the same vdev was held
> too (2 of 2), and re-creating the vdev cleared it (2 of 2). This happens
> on WPA2 networks as well as WPA3. An older firmware build,
> WLAN.HL.2.0-01387, did not hold the frames (0 of 7 reconnects after
> status 30).
This seems similar to an issue we see on the QCA6174's. I don't see a 20
second delay, but sometimes after an auth/assoc timeout we get a spam of
failed connections with NL80211_TIMEOUT_UNSPECIFIED. I've mentioned this
quite some time ago [1]. Do you think it has any relation to whats being
fixed here?
Thanks,
James
[1]
https://lore.kernel.org/linux-wireless/441e9883-1efc-498b-ba33-6a4f12443f3b@gmail.com/
prev parent reply other threads:[~2026-10-19 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 0:17 [PATCH ath-next 0/3] wifi: ath10k: WCN3990 station fixes for PMF and failed connections Shunsuke Nagashima via B4 Relay
2026-10-16 0:17 ` [PATCH ath-next 1/3] wifi: ath10k: set the PMF peer flag on WCN3990 Shunsuke Nagashima via B4 Relay
2026-10-16 0:17 ` [PATCH ath-next 2/3] wifi: ath10k: skip disassociation down for a station vdev that is not up Shunsuke Nagashima via B4 Relay
2026-10-16 0:17 ` [PATCH ath-next 3/3] wifi: ath10k: bring down a station vdev that never came up Shunsuke Nagashima via B4 Relay
2026-10-19 13:12 ` James Prestwood [this message]
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=61207966-c403-441d-9019-583702833a7f@gmail.com \
--to=prestwoj@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=david@ixit.cz \
--cc=fabricioakio@gmail.com \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=shunsuke@nagashi.ma \
/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
all inboxes | Powered by JetHome®