From: Burke Cates <burke.cates@gmail.com>
To: baochen.qiang@oss.qualcomm.com
Cc: Miaoqing Pan <miaoqing.pan@oss.qualcomm.com>,
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: Mon, 2 Nov 2026 20:04:34 -0800 [thread overview]
Message-ID: <20261103040434.3387789-1-burke.cates@gmail.com> (raw)
In-Reply-To: <492ece60-a670-48f4-a808-f09394b3db95@oss.qualcomm.com>
On Mon, Nov 02, 2026 at 04:02:56PM +0800, Baochen Qiang wrote:
> Hi Burke, can you please try if below series can fix your issue as well?
>
> https://lore.kernel.org/all/20261102-ath12k-logical-link-id-v4-0-f4c7807c299b@oss.qualcomm.com/
Yes, it fixes it here too. I took Miaoqing's patch out and applied
v4 1-11 instead, on v7.4-rc1 plus three ath12k commits from ath.git
(c752394249f8 and 02121aa4a012 from ath-next, 1e678e37ff13 from
ath-current) and out-of-tree Glymur platform/board patches; the tree
also carries Miaoqing's dp_peer reconnect fix (8b6b871332b5). All 11
applied as posted.
On the tri-band MLO SSID that failed with reason 15 (SAE, PMF
required, 2.4+5+6 GHz):
- 12 of 12 connect/disconnect cycles completed the 4-way handshake and
came up as MLO with three links (2.4 and 6 GHz active), ping OK each
time; no reason 15 in 23 handshakes over the session
- 5 of 5 rejoins after s2idle resume
- non-MLO WPA2 on 5 GHz still fine
This firmware sends the PEER_EXTENDED event (two per association), so
the host allocation path in 8/11 was not exercised. I'll send a
Tested-by on the cover letter.
Tested-on: QCC2072 hw1.0 PCI WLAN.COL.1.0.c2-00277-QCACOLSWPL_V1_TO_SILICONZ-1
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-11-03 4:04 UTC|newest]
Thread overview: 5+ 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
2026-11-02 8:02 ` Baochen Qiang
2026-11-03 4:04 ` 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=20261103040434.3387789-1-burke.cates@gmail.com \
--to=burke.cates@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--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®