<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <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#c21">Comment # 21</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 <a class="email" href="mailto:andy.nicholas@shield.ai" title="Andy Nicholas <andy.nicholas@shield.ai>"> Andy Nicholas</a> <pre>Created <a href="attachment.cgi?id=143954" name="attach_143954" title="GPU hang #9 after coarse power gating disabled, machine .36">attachment 143954</a> <a href="attachment.cgi?id=143954&action=edit" title="GPU hang #9 after coarse power gating disabled, machine .36">[details]</a> GPU hang #9 after coarse power gating disabled, machine .36 Ok, I will try the fc6 disable suggestion shortly. Will take a few hours to run and cause trouble. This is a hang from the 2nd compute stick which hung after 257 transcode iterations using the same source MJPEG movie. We have 2 compute sticks which seem to reliably show these problems. One is in San Diego at my work. The other is here in San Jose, Bay Area with me. We made a CloneZilla image of the compute stick to see if it would hang and it did after about 650 iterations (e.g., 650 minutes). I am told that CloneZilla can only really restore to device of similar size, so if you had an m5 compute stick (STK2mv64cc) we could put the 5GB image on a server for you. There's nothing confidential from shield. It's a stock 18.04 image with my home-made MJPEG movie. If necessary we can Fedex a compute stick which demonstrates the problem.</pre> </div> <hr> You are receiving this mail because: <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>