<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption with refreshrates >73Hz when DPM changing VRAM clock"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105300#c15">Comment # 15</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption with refreshrates >73Hz when DPM changing VRAM clock"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105300">bug 105300</a>
from <span class="vcard"><a class="email" href="mailto:tempel.julian@gmail.com" title="tempel.julian@gmail.com">tempel.julian@gmail.com</a>
</span></b>
<pre>Issue still exists with current 4.21-wip kernel.
As a workaround, it's enough to force the highest VRAM clock state (Forcing
higher clocks on the GPU itself is not necessary.):
echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_level
echo "2" > /sys/class/drm/card0/device/pp_dpm_mclk
Odd side note: It doesn't help to overclock the lower VRAM pstates to the same
clocks and voltages as the highest one.</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>