<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Skylake GPU HANG while gstreamer H264 vaapi encoding from MJPEG vaapi decode on drm-tip"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110394#c24">Comment # 24</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Skylake GPU HANG while gstreamer H264 vaapi encoding from MJPEG vaapi decode on drm-tip"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110394">bug 110394</a>
from <span class="vcard"><a class="email" href="mailto:andy.nicholas@shield.ai" title="Andy Nicholas <andy.nicholas@shield.ai>"> <span class="fn">Andy Nicholas</span></a>
</span></b>
<pre>(In reply to Andy Nicholas from <a href="show_bug.cgi?id=110394#c23">comment #23</a>)
<span class="quote">> Ok, I ran the kernel with the patch to disable RC6 on 8x compute sticks
> running the same kernel and same user-mode libraries. As per the previous
> tests, the minimum and maximum frequency was locked at 500 Mhz.
>
> We observed zero crashes or warnings emitted into the dmesg log (or anywhere
> else). None of the compute sticks locked-up or otherwise misbehaved.
>
> This was our expectation, and after running the transcode loop more than
> 28,000 times (3500x8) this continues to the the case.</span >
Any previous test crashed around 1050 times at most, and often much sooner, so
I believe having all the compute sticks survive to 3500 iterations is
statistically significant.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>