<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#c8">Comment # 8</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:john.bridgman@amd.com" title="John Bridgman <john.bridgman@amd.com>"> <span class="fn">John Bridgman</span></a>
</span></b>
<pre>Hold on, there is additional info on radeon IRC log (and in OP's head :)) which
is not yet in the ticket:
<span class="quote">>radeontop output of stuck card:
>gpu 100.00%, ee 0.00%, vgt 0.00%, ta 0.00%, sx 0.00%, sh 0.00%, spi 0.00%, sc 0.00%, pa 0.00%, db 0.00%, cb 0.00%</span >
The above is only when no load on the card... when running a 3D app the gpu bit
stays stuck at 1 (100%) but other bits behave normally.
I think that pretty much eliminates the caching idea.</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>