<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Radeonsi on Grenada cards (r9 390) exceptionally unstable and poorly performing"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91880#c195">Comment # 195</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - Radeonsi on Grenada cards (r9 390) exceptionally unstable and poorly performing"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91880">bug 91880</a>
from <span class="vcard"><a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> <span class="fn">Alex Deucher</span></a>
</span></b>
<pre>(In reply to Sandeep from <a href="show_bug.cgi?id=91880#c194">comment #194</a>)
<span class="quote">> So, I had never used amdgpu.dc=1 and amdgpu.dpm=1 kernel parameters when
> testing earlier.
>
> I tried using them now, with the 4.16.7 kernel, and replayed the APItrace
> file. No crashes! Finally.
>
> Well, this is still a workaround, but atleast it works. I doubt it has
> anything to do with DC, although it's possible......</span >
setting dpm=1 uses the new powerplay code rather than the old dpm code for
power management on CI parts.</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>