From: "Limonciello, Mario" <Mario.Limonciello@amd.com>
To: "casteyde.christian@free.fr" <casteyde.christian@free.fr>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Thorsten Leemhuis <regressions@leemhuis.info>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
Kai-Heng Feng <kai.heng.feng@canonical.com>
Subject: RE: [REGRESSION] Laptop with Ryzen 4600H fails to resume video since 5.17.4 (works 5.17.3)
Date: Thu, 19 May 2022 18:07:31 +0000 [thread overview]
Message-ID: <MN0PR12MB6101D7AB5BC33430A8492E0AE2D09@MN0PR12MB6101.namprd12.prod.outlook.com> (raw)
In-Reply-To: <MN0PR12MB6101FA3FF375A961E67AE89CE2D09@MN0PR12MB6101.namprd12.prod.outlook.com>
[Public]
>
> In addition to my other ask somewhere in this thread for increased
> debugging
> output to find your "real" problem, please give a try of this combo:
>
> 1) 5.18-rc7
> 2) Patch turning off reset on dGPUs in s2idle
> 3) The below patch
>
> This patch should do pretty much the same thing, try to recover your GPU
> when
> it's in this bad state. Now it happens somewhere more sustainable and
> sensible:
> on the resume path. I think this might get you a functional display rather
> than that
> "black screen" from the failed suspend cycle. It's still papering over your real
> issue
> of whatever caused the failed suspend.
>
I noticed the reset doesn't redo the HW init, that's still another needed step.
So here's a proper link to the patch you can apply as an mbox:
https://patchwork.freedesktop.org/patch/486836/
This is untested.
next prev parent reply other threads:[~2022-05-19 18:07 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 14:41 [REGRESSION] Laptop with Ryzen 4600H fails to resume video since 5.17.4 (works 5.17.3) Christian Casteyde
2022-05-14 15:12 ` Thorsten Leemhuis
2022-05-14 17:34 ` Christian Casteyde
2022-05-16 2:47 ` Kai-Heng Feng
2022-05-16 3:06 ` Mario Limonciello
2022-05-16 17:23 ` Christian Casteyde
2022-05-17 2:03 ` Kai-Heng Feng
2022-05-17 6:36 ` Christian Casteyde
2022-05-17 6:58 ` Kai-Heng Feng
2022-05-17 17:37 ` casteyde.christian
2022-05-18 5:52 ` Thorsten Leemhuis
2022-05-18 5:54 ` Kai-Heng Feng
2022-05-18 6:37 ` Thorsten Leemhuis
2022-05-18 20:15 ` Limonciello, Mario
2022-05-23 13:02 ` Christian Casteyde
2022-05-23 14:00 ` Limonciello, Mario
2022-05-23 17:03 ` Christian Casteyde
2022-05-23 22:01 ` Limonciello, Mario
2022-05-24 20:54 ` Christian Casteyde
2022-05-25 7:29 ` Thorsten Leemhuis
2022-05-17 17:38 ` casteyde.christian
2022-05-17 18:13 ` Limonciello, Mario
2022-05-18 11:02 ` casteyde.christian
2022-05-19 17:31 ` Limonciello, Mario
2022-05-19 18:07 ` Limonciello, Mario [this message]
2022-05-18 2:08 ` Kai-Heng Feng
2022-05-18 2:19 ` Mario Limonciello
2022-05-18 7:15 ` Christian Casteyde
2022-05-18 10:53 ` casteyde.christian
2022-05-27 9:51 ` [REGRESSION] Laptop with Ryzen 4600H fails to resume video since 5.17.4 (works 5.17.3) #forregzbot Thorsten Leemhuis
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=MN0PR12MB6101D7AB5BC33430A8492E0AE2D09@MN0PR12MB6101.namprd12.prod.outlook.com \
--to=mario.limonciello@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=casteyde.christian@free.fr \
--cc=gregkh@linuxfoundation.org \
--cc=kai.heng.feng@canonical.com \
--cc=regressions@leemhuis.info \
--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 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).