<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [bisected] Systems hangs on resume from S3 sleep due to "Match actual state during S3 resume" commit"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103277#c10">Comment # 10</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [bisected] Systems hangs on resume from S3 sleep due to "Match actual state during S3 resume" commit"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103277">bug 103277</a>
from <span class="vcard"><a class="email" href="mailto:Jerry.Zuo@amd.com" title="Jerry Zuo <Jerry.Zuo@amd.com>"> <span class="fn">Jerry Zuo</span></a>
</span></b>
<pre>(In reply to dwagner from <a href="show_bug.cgi?id=103277#c9">comment #9</a>)
<span class="quote">> Bad news: Tried amd-staging-drm-next as of commit
> 367a3d2bdc27fd1d23be9ea75cec34b52297184d, which does include the commit
> <a href="https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-drm">https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-drm</a>-
> next&id=c2a899da6d8c0658c6f8493cb6b5ca4e890a15b7 referenced by Alex above,
> but the result is still the same as in the original description of this bug
> report.
>
> I tested "echo "mem" >/sys/power/state" both without starting X and from an
> Xterm, in both cases no picture comes up at resume from S3, and the computer
> does not react on input.
>
> The test scenario Jerry Zuo described above does not mention whether the
> display was connected via DP or HDMI - could this be of relevance for
> reproduction?</span >
I tested on HDMI in 4K display. I'll check the commit on drm-next.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>