From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: gary.chang@realtek.com, Yan-Hsuan Chuang <tony0620emma@gmail.com>
Cc: regressions@lists.linux.dev, linux-wireless@vger.kernel.org,
Kalle Valo <kvalo@kernel.org>, Paul Gover <pmw.gover@yahoo.co.uk>,
stable@vger.kernel.org
Subject: Re: Resume after suspend broken, reboots instead on kernel 6.1 onwards x86_64 RTW88
Date: Thu, 16 Feb 2023 15:18:53 +0100 [thread overview]
Message-ID: <7e02467e-84d7-55d9-9edb-bb8107434a29@leemhuis.info> (raw)
In-Reply-To: <10a47408-3019-403d-97b1-c9f36e52e130@leemhuis.info>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 10.02.23 13:24, Linux kernel regression tracking (Thorsten Leemhuis)
wrote:
> On 09.02.23 20:59, Paul Gover wrote:
>> Suspend/Resume was working OK on kernel 6.0.13, broken since 6.1.1
>> (I've not tried kernels between those, except in the bisect below.)
>> All subsequent 6,1 kernels exhibit the same behaviour.
>>
>> Suspend works OK, but on Resume, there's a flicker, and then it reboots.
>> Sometimes the screen gets restored to its contents at the time of suspend. but
>> less than a second later, it starts rebooting.
>> To reproduce, simply boot, suspend, and resume.
>>
>> Git bisect blames RTW88
>> commit 6bf3a083407b5d404d70efc3a5ac75b472e5efa9
>
> TWIMC, that's "wifi: rtw88: add flag check before enter or leave IPS"
>
>> I'll attach bisect log, dmesg and configs to the bug I've opened
>> https://bugzilla.kernel.org/show_bug.cgi?id=217016
#regzbot monitor:
https://lore.kernel.org/linux-wireless/20230216053633.20366-1-pkshih@realtek.com/T/#u
#regzbot fix: wifi: rtw88: use RTW_FLAG_POWERON flag to prevent to power
on/off twice
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2023-02-16 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3739412.kQq0lBPeGt.ref@ryzen>
[not found] ` <3739412.kQq0lBPeGt@ryzen>
2023-02-10 12:24 ` Resume after suspend broken, reboots instead on kernel 6.1 onwards x86_64 RTW88 Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-16 14:18 ` Linux regression tracking #update (Thorsten Leemhuis) [this message]
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=7e02467e-84d7-55d9-9edb-bb8107434a29@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=gary.chang@realtek.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pmw.gover@yahoo.co.uk \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tony0620emma@gmail.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;
as well as URLs for NNTP newsgroup(s).