<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><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">103277</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[bisected] Systems hangs on resume from S3 sleep due to "Match actual state during S3 resume" commit
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>DRI git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>blocker
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/AMDgpu
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>jb5sgc1n.nya@20mm.eu
</td>
</tr></table>
<p>
<div>
<pre>After I updated my kernel to
<a href="https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next">https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next</a> as of
today (latest commit at this time:
1c630e83443a0f271c192ecfa0d94023661a0000) I noticed that my computer would no
longer wake up from S3 sleep - power LED goes on, but apart from that no
display and no reaction to any input (other than Num-Lock still switchable).
The difference to the ~2 weeks older kernel was 100% reproducable by just
doing:
- boot to console (no start of X11 required) and login as root
- echo "mem" >/sys/power/state
- wait till power LED blinks
- press some key to wake up the system
- observe no display output and no reaction to anything
GPU is a RX 460, CPU a Ryzen R7 1800X, board Asus X370 Pro, connected is one 4k
display via HDMI 2.0.
I bisected the git commits, and the one that causes the bug is:
<span class="quote">> 7ae4acd21e9e264afb079e23d43bcf2238c7dbea
> drm/amd/display: Match actual state during S3 resume.</span >
After this, I went back to the current HEAD of amd-staging-drm-next and
(manually) reverted only commit 7ae4acd21e9e264afb079e23d43bcf2238c7dbea, and
this indeed results in a kernel that works fine with regards to resuming from
S3 sleep.
There are no noteworthy "dmesg"-emissions that accompany going to S3 sleep, but
the dmesg-output that I can collect ends slightly before the system actually
sleeps, so wether anything is emitted upon the wake-up attempt, I have no way
to know.</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>