<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - R290X stuck at 100% GPU load / full core clock on non-x86 machines"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96964#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - R290X stuck at 100% GPU load / full core clock on non-x86 machines"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96964">bug 96964</a>
from <span class="vcard"><a class="email" href="mailto:kb9vqf@pearsoncomputing.net" title="Timothy Pearson <kb9vqf@pearsoncomputing.net>"> <span class="fn">Timothy Pearson</span></a>
</span></b>
<pre>(In reply to John Bridgman from <a href="show_bug.cgi?id=96964#c5">comment #5</a>)
<span class="quote">> At the risk of sending things off in the wrong direction, my first thought
> is some kind of funky data caching thing when reading GRBM_STATUS using
> POWER hardware.
>
> If bit 31 were always 1 and the other bits were behaving normally then the
> idea of being stuck at 100% load would make more sense, but bit 31 stuck at
> 1 and all the rest stuck at 0 seems really odd.</span >
If it were a data caching issue, how would the GPU crash / soft reset fix it?</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>