From: Joonhoe Kim <26rote@gmail.com>
To: Yingying Tang <yingying.tang@oss.qualcomm.com>
Cc: Joonhoe Kim <26rote@gmail.com>,
ath12k@lists.infradead.org, linux-wireless@vger.kernel.org,
yintang@qti.qualcomm.com,
Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
Jeff Johnson <jjohnson@kernel.org>
Subject: Re: [PATCH ath-next] Revert "wifi: ath12k: add panic handler"
Date: Sun, 4 Oct 2026 18:34:56 +0900 [thread overview]
Message-ID: <20261004093456.74263-1-26rote@gmail.com> (raw)
In-Reply-To: <20260612032332.2278338-1-yingying.tang@oss.qualcomm.com>
On Thu, Jun 11, 2026 at 08:23:32PM -0700, Yingying Tang wrote:
> ath12k_core_panic_handler() is invoked via atomic_notifier_call_chain(),
> which runs inside an RCU read-side critical section.
I hit this on a WCN7860 (hw2.0, PCI) in a Lenovo Legion Tab Y700 Gen 5
(Kaanapali), v7.3-rc4 plus board patches. Here the panic never got past
the notifier:
SMP: stopping secondary CPUs
Voluntary context switch within RCU read-side critical section!
schedule_timeout
__mhi_device_get_sync
ath12k_wifi7_pci_bus_wake_up
ath12k_pci_read32
ath12k_pci_sw_reset
ath12k_pci_panic_handler
atomic_notifier_call_chain
vpanic
A hung_task panic stayed hung until a forced restart, and a sysrq crash
only ended in a reset after about 50 s.
With the handler removed, a sysrq crash reboots normally, and after the
reboot WCN7860 is enumerated again (PCIe Gen3 x2 link up) and Wi-Fi
works.
Tested-by: Joonhoe Kim <26rote@gmail.com>
On Baochen's question, the handler came in with 809055628bce, so:
Fixes: 809055628bce ("wifi: ath12k: add panic handler")
next prev parent reply other threads:[~2026-10-04 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 3:23 [PATCH ath-next] Revert "wifi: ath12k: add panic handler" Yingying Tang
2026-06-29 2:10 ` Baochen Qiang
2026-10-04 9:34 ` Joonhoe Kim [this message]
2026-10-05 15:04 ` Jeff Johnson
2026-10-05 18:13 ` Jeff Johnson
2026-10-06 12:02 ` Rameshkumar Sundaram
2026-10-06 13:44 ` Jeff Johnson
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=20261004093456.74263-1-26rote@gmail.com \
--to=26rote@gmail.com \
--cc=ath12k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=yingying.tang@oss.qualcomm.com \
--cc=yintang@qti.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