From: Kalle Valo <kvalo@kernel.org>
To: Richard Weinberger <richard@nod.at>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
ath11k <ath11k@lists.infradead.org>
Subject: Re: Resume from hibernation fails due to ath11k_pci
Date: Mon, 13 Feb 2023 14:33:53 +0200 [thread overview]
Message-ID: <87pmadvj66.fsf@kernel.org> (raw)
In-Reply-To: <370539199.123516.1676291073661.JavaMail.zimbra@nod.at> (Richard Weinberger's message of "Mon, 13 Feb 2023 13:24:33 +0100 (CET)")
Richard Weinberger <richard@nod.at> writes:
> ----- Ursprüngliche Mail -----
>> Von: "kvalo" <kvalo@kernel.org>
>> Richard Weinberger <richard@nod.at> writes:
>>
>>> On my shiny new Lenovo T14s resume from hibernation always fails, and crashes
>>> the kernel.
>>> Looks like ath11k_pci is unable to resume the device.
>>> This happens also with Linus' tree as of today.
>>
>> Unfortunately a known issue in ath11k but no fix available:
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=214649
>
> So the device is unable to operate after entering ACPI S4.
>
> Is this a bug in the Linux ath11k driver itself or more likely a
> firmware chip issue? I didn't verify whether resume works on Windows
> though.
IIRC the issue is that ath11k expects the firmware to be running during
suspend. And this was because shutting down the firmware for suspend
caused problems in the MHI subsystem during resume. To fix this I
suspect we need changes both in ath11k and in the MHI subsystem, so not
easy.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2023-02-13 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 22:12 Resume from hibernation fails due to ath11k_pci Richard Weinberger
2023-02-13 11:58 ` Kalle Valo
2023-02-13 12:24 ` Richard Weinberger
2023-02-13 12:33 ` Kalle Valo [this message]
2023-02-13 13:15 ` Richard Weinberger
2023-02-13 18:19 ` Kalle Valo
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=87pmadvj66.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=richard@nod.at \
/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;
as well as URLs for NNTP newsgroup(s).