<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [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#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [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:jb5sgc1n.nya@20mm.eu" title="dwagner <jb5sgc1n.nya@20mm.eu>"> <span class="fn">dwagner</span></a>
</span></b>
<pre>(In reply to <a href="mailto:mikita.lipski@amd.com">mikita.lipski@amd.com</a> from <a href="show_bug.cgi?id=103277#c19">comment #19</a>)
<span class="quote">> I have attempted to reproduce an issue, but didn't succeed.
> We have used an identical hardware setup with a reference rx460 card and
> couldn't reproduce a hang on various kernel versions.</span >
Strange. If I didn't keep an older amd-staging-drm-next kernel from October
2017 in use where S3 resumes work every time, I would doubt my hardware - but
the way it is the only possible cause is a kernel change sine then.
<span class="quote">> There is still a possibility that some kernel config options might be
> causing an issue.
> If its possible, could you please provide kernel configuration so the
> testing environment is identical.</span >
Sure, will attach my .config (as used with the current drm-next-4.17-wip) after
this comment.
<span class="quote">> Also does the issue reproduce reproduce if you disable DC? (amdgpu.dc=0 in
> GRUB menu)</span >
Tested with today's drm-next-4.17-wip git: With "amdgpu.dc=0" on the kernel
command line, resume from S3 works fine for me, both from the console (before
starting X11) and when running X11.
(But of course, no 4k/60Hz video and no HDMI audio with amdgpu.dc=0, so that is
not really an option for actual use.)
So the resume-from-S3 failures are definitely caused by something in the DC
code that changed since early October 2017.</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>