<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Kernel panic when waking up after screen goes blank."
href="https://bugs.freedesktop.org/show_bug.cgi?id=105018#c32">Comment # 32</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Kernel panic when waking up after screen goes blank."
href="https://bugs.freedesktop.org/show_bug.cgi?id=105018">bug 105018</a>
from <span class="vcard"><a class="email" href="mailto:ragnaros39216@yandex.com" title="L.S.S. <ragnaros39216@yandex.com>"> <span class="fn">L.S.S.</span></a>
</span></b>
<pre>So it seems there definitely is a regression on 4.17 on this issue (the patches
are not required as the lines were already there in 4.17). This time it isn't a
kernel panic, but an "invalid opcode" error caused by dm_update_crtcs_state
that was called by amdgpu_dm_atomic_check.
The issue is not 100% reproducible, but still means going to standby with an
AMD GPU and DC is still dangerous and may result in losses of unsaved work.</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>