<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#c7">Comment # 7</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>(In reply to Andy Nicholas from <a href="show_bug.cgi?id=110394#c5">comment #5</a>) > Created <a href="attachment.cgi?id=143921" name="attach_143921" title="3rd GPU hang on same hardware using same test loop. Within 2 iterations.">attachment 143921</a> <a href="attachment.cgi?id=143921&action=edit" title="3rd GPU hang on same hardware using same test loop. Within 2 iterations.">[details]</a> > 3rd GPU hang on same hardware using same test loop. Within 2 iterations. > > This time my transcoder script seemed to have terminated... but actually > didn't -- it was just asleep, waiting. The transcoder script RESUMED RUNNING > after 14 minutes and completed the transcoding task. No further information > was emitted into the dmesg log. > > This is bad because our usage case can't tolerate a "hang" where the > transcoder does not emit anything for 14 minutes... or even a few > milliseconds. Btw, while the transcoder was "hung" I was able to login and use the kernel as normal using SSH so most of the kernel subsystems seemed to be performing normally. The GPU was definitely not functioning properly. Btw, This is using Ubuntu server so we do not have Xserver running.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>