<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - GPU fault detected: 146 / VM_CONTEXT1_PROTECTION_FAULT / ring gfx timeout"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107152#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - GPU fault detected: 146 / VM_CONTEXT1_PROTECTION_FAULT / ring gfx timeout"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107152">bug 107152</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>Indeed, I found my theory confirmed by many experiments: If I use a script like
<span class="quote">> #!/bin/bash
> cd /sys/class/drm/card0/device
> echo manual >power_dpm_force_performance_level
> # low
> echo 0 >pp_dpm_mclk
> echo 0 >pp_dpm_sclk
> # medium
> #echo 1 >pp_dpm_mclk
> #echo 1 >pp_dpm_sclk
> # high
> #echo 1 >pp_dpm_mclk
> #echo 6 >pp_dpm_sclk</span >
to enforce just any performance level, then the crashes do not occur anymore -
also with the "low frame rate video test".
So it seems that the transition from one "dpm" performance level to another,
with a certain probability, causes these crashes. And the more often the
transitions occur, the sooner one will experience them.
The dynamic power management issue can now be pursued with the original bug
report <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> for the
vm_update_mode=0 case - there is probably not much sense in keeping this bug
report open just because errors also occur with wm_update_mode=3, just less
often.</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>