From: Christopher Griffin via B4 Relay <devnull+christophergriffin05.gmail.com@kernel.org>
To: Jeff Johnson <jjohnson@kernel.org>, Kalle Valo <kvalo@kernel.org>,
Hari Chandrakanthan <quic_haric@quicinc.com>,
Venkateswara Naralasetty <quic_vnaralas@quicinc.com>,
Pradeep Kumar Chitrapu <quic_pradeepc@quicinc.com>,
Anilkumar Kolli <quic_akolli@quicinc.com>,
Loic Poulain <loic.poulain@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
linux-kernel@vger.kernel.org,
Maharaja Kennadyrajan <quic_mkenna@quicinc.com>,
John Crispin <john@phrozen.org>,
Govindaraj Saminathan <quic_gsamin@quicinc.com>,
ath10k@lists.infradead.org, Wen Gong <quic_wgong@quicinc.com>,
Christopher Griffin <christophergriffin05@gmail.com>
Subject: [PATCH 0/3] wifi: ath10k/ath11k: firmware recovery deadlock and stale scan timeouts
Date: Thu, 05 Nov 2026 12:11:35 -0600 [thread overview]
Message-ID: <20261105-ath-recovery-scan-timeout-v1-0-99a70d89e114@gmail.com> (raw)
On an Arista C-360 (IPQ8074 with two QCN9074), a QCN9074 firmware crash
was never recovered. Patch 1 removes a conf_mutex deadlock between
ath11k_mac_op_start() and the restart work, which makes every recovery
time out when CONFIG_ATH11K_SPECTRAL is set.
The same crash left a scan timeout pending for a scan that had failed to
start, and it fired on freed memory after the driver was bound again.
Patch 2 stops arming it, and patch 3 does the same in ath10k, which has
the same code.
Tested on an Arista C-360 with the series applied to the ath11k of
OpenWrt's backports-7.2: before patch 1, two simulated asserts of the
QCN9074 firmware both ended in "Hardware became unavailable during
restart"; with it, two of two recovered in about 3 s. Patches 2
and 3 are compile-tested only (W=1); no scan failed to start in these
runs.
---
Christopher Griffin (3):
wifi: ath11k: don't hold conf_mutex while waiting for recovery
wifi: ath11k: don't arm the scan timeout for a scan that did not start
wifi: ath10k: don't arm the scan timeout for a scan that did not start
drivers/net/wireless/ath/ath10k/mac.c | 1 +
drivers/net/wireless/ath/ath11k/mac.c | 6 ++++++
2 files changed, 7 insertions(+)
---
base-commit: 5c8eab13e391aaabd5a1ad58f3ee4bb10ce7573e
change-id: 20261105-ath-recovery-scan-timeout-57a3b3dd7a6f
Best regards,
--
Christopher Griffin <christophergriffin05@gmail.com>
next reply other threads:[~2026-11-05 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 18:11 Christopher Griffin via B4 Relay [this message]
2026-11-05 18:11 ` [PATCH 1/3] wifi: ath11k: don't hold conf_mutex while waiting for recovery Christopher Griffin via B4 Relay
2026-11-05 18:11 ` [PATCH 2/3] wifi: ath11k: don't arm the scan timeout for a scan that did not start Christopher Griffin via B4 Relay
2026-11-05 18:11 ` [PATCH 3/3] wifi: ath10k: " Christopher Griffin via B4 Relay
2026-11-05 20:53 ` Loic Poulain
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=20261105-ath-recovery-scan-timeout-v1-0-99a70d89e114@gmail.com \
--to=devnull+christophergriffin05.gmail.com@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=ath11k@lists.infradead.org \
--cc=christophergriffin05@gmail.com \
--cc=jjohnson@kernel.org \
--cc=john@phrozen.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=quic_akolli@quicinc.com \
--cc=quic_gsamin@quicinc.com \
--cc=quic_haric@quicinc.com \
--cc=quic_mkenna@quicinc.com \
--cc=quic_pradeepc@quicinc.com \
--cc=quic_vnaralas@quicinc.com \
--cc=quic_wgong@quicinc.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®