From: Oliver Schmidt <oliver@luced.de>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux AMDGPU <amd-gfx@lists.freedesktop.org>
Cc: Wayne Lin <wayne.lin@amd.com>, Stylon Wang <stylon.wang@amd.com>,
Daniel Wheeler <daniel.wheeler@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Fwd: Thinkpad X13 AMD: Problems with external monitor wake up after suspend
Date: Fri, 1 Dec 2023 20:05:52 +0100 [thread overview]
Message-ID: <12db0c2e-a1b7-f8f9-278e-8aefe5619c1f@luced.de> (raw)
In-Reply-To: <da0efb19-c883-40c8-b284-7eb7f4d3640b@leemhuis.info>
On 01.12.23 12:37, Thorsten Leemhuis wrote:
> Maybe one of the developers among the recipients has a idea. Oliver, but
> if none of them replies any time soon, it would be best if you'd check
> if 6.6 (and/or 6.7-rc) is affected as well; and if reverting it there
> fixes it, too.
OK, I checked it: compiled a 6.6.3 kernel and got the same suspend-resume
problem as with the 6.1.57 and 6.1.64 kernels. I also was able to revert the
changes of commit ec5fa9 "drm/amd/display: Adjust the MST resume flow" in the
6.6.3 kernel and the problem was solved as in the 6.1.x kernels (however it
seems that resuming with the 6.6 kernel needs a little more time until the
monitor gets signal).
Best regards,
Oliver
next prev parent reply other threads:[~2023-12-01 19:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 0:30 Fwd: Thinkpad X13 AMD: Problems with external monitor wake up after suspend Bagas Sanjaya
2023-12-01 11:37 ` Thorsten Leemhuis
2023-12-01 19:05 ` Oliver Schmidt [this message]
2023-12-15 11:22 ` Linux regression tracking #update (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=12db0c2e-a1b7-f8f9-278e-8aefe5619c1f@luced.de \
--to=oliver@luced.de \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bagasdotme@gmail.com \
--cc=daniel.wheeler@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=stylon.wang@amd.com \
--cc=wayne.lin@amd.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).