From: Burke Cates <burke.cates@gmail.com>
To: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>
Cc: jjohnson@kernel.org, ath12k@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH ath-next] wifi: ath12k: fix MLO 4-way handshake timeout on QCC2072
Date: Thu, 29 Oct 2026 21:19:01 -0700 [thread overview]
Message-ID: <20261030041902.2740757-1-burke.cates@gmail.com> (raw)
In-Reply-To: <20260815014329.3748059-1-miaoqing.pan@oss.qualcomm.com>
On Sat, Aug 15, 2026 at 09:43:29AM +0800, Miaoqing Pan wrote:
> This is observed on QCC2072 where EAPOL M3 uses the MLD address,
>
> deauthenticated (Reason: 15=4WAY_HANDSHAKE_TIMEOUT)
I hit this on an ASUS Zenbook A16 (UX3607OA, Snapdragon X2 Elite)
with the on-board QCC2072: Wi-Fi 7 MLO SSIDs (SAE, PMF required; one
6 GHz-only, one 2.4+5+6 GHz) failed with reason 15 whatever the
association link, with M3 dropped by mac80211. Non-MLO WPA2-PSK on
5 GHz was fine.
With this patch, applied as posted, both MLO SSIDs connect. I tested
on v7.3-rc5 and again on v7.3, each plus out-of-tree Glymur
platform/board patches; on v7.3 the tri-band SSID connected as MLO
(on its 6 GHz link) and rejoined MLO after s2idle resume. That tree
also carries your separate dp_peer fix (8b6b871332b5, "Fix failure to
create ath12k_dp_peer on MLO reconnect"). I haven't tried the rebase
onto ath/main that Jeff asked for.
Tested-on: QCC2072 hw1.0 PCI WLAN.COL.1.0.c2-00277-QCACOLSWPL_V1_TO_SILICONZ-1
Tested-by: Burke Cates <burke.cates@gmail.com> # ASUS Zenbook A16 (UX3607OA)
AI coding assistants helped run these tests and draft this reply; the
results are from the hardware runs.
Thanks,
Burke
prev parent reply other threads:[~2026-10-30 4:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 1:43 Miaoqing Pan
2026-09-24 18:05 ` Jeff Johnson
2026-10-30 4:19 ` Burke Cates [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=20261030041902.2740757-1-burke.cates@gmail.com \
--to=burke.cates@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miaoqing.pan@oss.qualcomm.com \
/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®