From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Takashi Iwai <tiwai@suse.de>,
Chris Lew <christopher.lew@oss.qualcomm.com>
Cc: Deepak Kumar Singh <deepak.singh@oss.qualcomm.com>,
Pranav Mahesh Phansalkar <pranav.phansalkar@oss.qualcomm.com>,
netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [REGRESSION] ath12k suspend/resume breakage on 7.3-rc2
Date: Sun, 13 Sep 2026 11:03:57 +0200 [thread overview]
Message-ID: <2741f995-dca0-4645-848c-34752d62574f@leemhuis.info> (raw)
In-Reply-To: <878q55sfxo.wl-tiwai@suse.de>
On 9/13/26 10:39, Takashi Iwai wrote:
> On Sun, 13 Sep 2026 10:35:27 +0200,
> Takashi Iwai wrote:
>>
>> on 7.3-rc2, the suspend/resume of ath12k WiFi on Lenovo Thinkpad T14s
>> Gen6 AMD model is broken. Upon suspend, the network isn't recovered,
>> and the desktop got eventually frozen.
>>
>> The git bisect pointed to the commit
>> 544d85de4dc22c01badfd8cefa59829ce35c4858
>> net: qrtr: Send HELLO message on endpoint register
>>
>> and reverting this fixed the problem.
>>
>> Below is the (stripped) dmesg output after the resume showing the
>> problem.
>>
>> As far as I understand, the problem seems to be the change of the code
>> flow: ath12k uses mhi_power_down_keep_dev() during suspend, so the
>> qcom_mhi_qrtr_remove() and *_probe() won't be called. This makes the
>> driver endlessly waiting for the HELLO handshake upon resume with the
>> commit above.
>
> ... and below is a quick fix I tested. It seems working so far.
Not my area of expertise, as you know, but have you see this fix for the
culprit? Or is your problem a different one?
net: qrtr: resend HELLO on MHI resume
https://lore.kernel.org/all/20260909055846.16539-1-daniel@quora.org/
Ciao, Thorsten
next prev parent reply other threads:[~2026-09-13 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 8:35 [REGRESSION] ath12k suspend/resume breakage on 7.3-rc2 Takashi Iwai
2026-09-13 8:39 ` Takashi Iwai
2026-09-13 9:03 ` Thorsten Leemhuis [this message]
2026-09-14 6:22 ` Takashi Iwai
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=2741f995-dca0-4645-848c-34752d62574f@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=christopher.lew@oss.qualcomm.com \
--cc=deepak.singh@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pranav.phansalkar@oss.qualcomm.com \
--cc=regressions@lists.linux.dev \
--cc=tiwai@suse.de \
/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