From: Sergio Callegari <sergio.callegari@gmail.com>
To: Christian Heusel <christian@heusel.eu>
Cc: Greg KH <gregkh@linuxfoundation.org>,
stable@vger.kernel.org,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: Regression: mt7921e unable to change power state from d3cold to d0 - 6.12.x broken, past LTS 6.6.x works
Date: Sun, 30 Mar 2025 18:35:43 +0200 [thread overview]
Message-ID: <efde5e18-672f-484f-90c3-d23d673daa18@gmail.com> (raw)
In-Reply-To: <38658f1a-216b-470d-99a2-13d66f075c77@heusel.eu>
Hi Christian,
Thanks for your nice offer, details below:
On 20/03/2025 11:05, Christian Heusel wrote:
> Hey Sergio,
>
> On 25/03/20 08:49AM, Sergio Callegari wrote:
>> Might be able to test on the distro built kernels that basically trace the
>> releases and stable point releases. This should start helping bracketing the
>> problem a bit better as a starter. But it is going to take a lot of time,
>> since the issue happens when the machine fails to get out of hibernation,
>> that is not always, and obvioulsy I need to try avoiding this situation as
>> much as possible.
>
> Which linux distro are you using? If you're on Arch Linux I can provide
> you with prebuilt images for the bisection :)
I am on manjaro, where the kernel follows slightly different naming
conventions, but the arch kernels should be OK. So thank you very much
for the nice offer. The thing is possibly a bit premature, in that I
would like to identify first what is the kernel RC or point release
where the issue started to appear, because I have these kernels
available for my distro which makes things easier. Unfortunately, I am
still in the dark even wrt this.
The issue is nasty, because it only happens when you crash on restore
from hibernation, which is something that I am desperately trying to
avoid because this is my work machine and I really don't want to risk
data loss.
The big problem with this bug is that you remain with the impression
that your hardware is bricked. On the web I read that booting windows
immediately gives you back the wifi device on pcie, but I really cannot
say, as I have no windows to try. What I can say is that the 6.6 LTS
kernel also lets you recover the WIFI, while 6.12 LTS does not.
As a stopgap, would be great to know if there is anything that can be
done while on 6.12 to fully reset the pcie (or the pcie device, I still
don't know what is the culprit), so you don't need to boot an older kernel.
Thanks again,
Sergio
>
>>
>> Incidentally, the machine seems to hibernate-resume just fine. It is when I
>> suspend-then-hibernate that I get the failures.
>>
>> Before contacting the network driver authors, I just wanted to query whether
>> the issue is likely in it or in the power-management or pcie subsystems.
>>
>> Thanks,
>> Sergio
>
> Cheers,
> Chris
>
>>
>> On 20/03/2025 00:54, Greg KH wrote:
>>> On Wed, Mar 19, 2025 at 08:38:52PM +0100, Sergio Callegari wrote:
>>>> There is a nasty regression wrt mt7921e in the last LTS series (6.12). If
>>>> your computer crashes or fails to get out of hibernation, then at the next
>>>> boot the mt7921e wifi does not work, with dmesg reporting that it is unable
>>>> to change power state from d3cold to d0.
>>>>
>>>> The issue is nasty, because rebooting won't help.
>>>
>>> Can you do a 'git bisect' to track down the issue? Also, maybe letting
>>> the network driver authors know about this would be good.
>>>
>>> thanks,
>>>
>>> greg k-h
>>
>>
next prev parent reply other threads:[~2025-03-30 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 19:38 Regression: mt7921e unable to change power state from d3cold to d0 - 6.12.x broken, past LTS 6.6.x works Sergio Callegari
2025-03-19 23:54 ` Greg KH
2025-03-20 7:49 ` Sergio Callegari
2025-03-20 10:05 ` Christian Heusel
2025-03-30 16:35 ` Sergio Callegari [this message]
2025-04-14 9:09 ` Sergio Callegari
2025-03-30 17:04 ` Sergio Callegari
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=efde5e18-672f-484f-90c3-d23d673daa18@gmail.com \
--to=sergio.callegari@gmail.com \
--cc=christian@heusel.eu \
--cc=gregkh@linuxfoundation.org \
--cc=regressions@lists.linux.dev \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.