From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: jjohnson@kernel.org
Cc: ath11k@lists.infradead.org, ath12k@lists.infradead.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
Subject: [PATCH 0/5] wifi: ath12k: fixes to improve MLO station stability
Date: Mon, 27 Jul 2026 18:27:43 +0200 [thread overview]
Message-ID: <20260727162748.963275-1-jtornosm@redhat.com> (raw)
This series improves firmware crash recovery and connection stability
for MLO (Wi-Fi 7) stations on ath12k. Both work correctly for non-MLO
(Wi-Fi 6) stations, where the driver handles the full teardown and
reconnect cycle without issues and maintains stable connections. This
series brings MLO to the same level.
Without these fixes, a firmware crash during an active MLO connection
results in kernel warnings, NULL pointer dereferences, 20+ second
recovery delays, and periodic disconnections both after recovery and
during normal operation under heavy traffic.
Patches 1-3 fix firmware crash recovery:
Patch 1 moves the RECOVERY flag clear to reconfig_complete and adds
CRASH_FLUSH guards to prevent operations on dead firmware.
Patch 2 prevents scans during recovery to avoid NULL dereferences.
Patch 3 fixes ML peer ID desync between host and firmware by syncing
the peer ID from firmware's actual value.
Patches 4-5 fix MLO beacon miss handling:
Patch 4 fixes beacon_iter to iterate all MLO links instead of only
deflink for BSSID matching and connection_loss_work
cancellation.
Patch 5 complements patch 4 by skipping connection_loss_work for MLO
entirely, since its cancellation mechanism is unreliable and
the mac80211 probe triggered by ieee80211_beacon_loss() is
sufficient to detect real AP unreachability, as done by other
MLO-capable drivers such as mt76 and rtw89.
Tested on WCN7850 with MLO (Wi-Fi 7).
Firmware crashes were observed to occur spontaneously during normal
MLO operation with intense traffic testing, though rarely.
The debugfs simulate_fw_crash interface was used for systematic testing
and reproduction during active MLO connections with traffic.
Note: I will have limited availability from mid-August to
mid-September. I will address any review feedback before then
or promptly after returning.
Jose Ignacio Tornos Martinez (5):
wifi: ath12k: fix MLO station firmware crash recovery
wifi: ath12k: prevent scan during firmware recovery
wifi: ath12k: fix MLO dp_peer ID desync with firmware
wifi: ath12k: fix MLO beacon handling using per-link addressing
wifi: ath12k: skip connection_loss_work for MLO beacon miss
next reply other threads:[~2026-07-27 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 16:27 Jose Ignacio Tornos Martinez [this message]
2026-07-27 16:27 ` [PATCH 1/5] wifi: ath12k: fix MLO station firmware crash recovery Jose Ignacio Tornos Martinez
2026-07-27 16:27 ` [PATCH 2/5] wifi: ath12k: prevent scan during firmware recovery Jose Ignacio Tornos Martinez
2026-07-27 16:27 ` [PATCH 3/5] wifi: ath12k: fix MLO dp_peer ID desync with firmware Jose Ignacio Tornos Martinez
2026-07-27 16:27 ` [PATCH 4/5] wifi: ath12k: fix MLO beacon handling using per-link addressing Jose Ignacio Tornos Martinez
2026-07-27 16:27 ` [PATCH 5/5] wifi: ath12k: skip connection_loss_work for MLO beacon miss Jose Ignacio Tornos Martinez
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=20260727162748.963275-1-jtornosm@redhat.com \
--to=jtornosm@redhat.com \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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