<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><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> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Manual setting of pp_dpm_sclk resets after monitor off/on (rx 480)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107141">bug 107141</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Priority</td>
<td>medium
</td>
<td>high
</td>
</tr>
<tr>
<td style="text-align:right;">Severity</td>
<td>normal
</td>
<td>major
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Manual setting of pp_dpm_sclk resets after monitor off/on (rx 480)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107141#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Manual setting of pp_dpm_sclk resets after monitor off/on (rx 480)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107141">bug 107141</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>I can confirm this bug - and it is worse than reported. And due to other bugs,
it is not just a cosmetic annoyance.
The report only talks of "monitor off/on", but the
power_dpm_force_performance_level setting is also disregarded after any output
mode change with "xrandr --output XXX --mode YYY", and after any switch between
the console display and X11 (if the console uses another mode, which is
likely).
Also, changing power_dpm_force_performance_level to "manual" is currently the
only method to work around the long standing (1 year) crash bug reported in
<a class="bz_bug_link
bz_status_NEW "
title="NEW - System crashes after "[drm] IP block:gmc_v8_0 is hung!" / [drm] IP block:sdma_v3_0 is hung!"
href="show_bug.cgi?id=102322">https://bugs.freedesktop.org/show_bug.cgi?id=102322</a>
But with amdgpu assuming "automatic" behaviour instead of "manual" after each
output mode change, it is difficult to keep a system stable using this
work-around.
BTW: This is bug is still present in current amd-staging-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>