<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#c28">Comment # 28</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 Chris Wilson from <a href="show_bug.cgi?id=110394#c26">comment #26</a>) > The other step would be to disable rc6 only and keep the powergate in > gen9_enable_rc6() -- to confirm which of the two is the risk. To be clear - I believe this is the state of Shield's testing, all of which use the same drm-tip kernel from 3 weeks ago, all of which are transcoding from MJPEG --> H264: (1) Only disable RC6, no other changes == no GPU issues (2) Only disable coarse power-gating [in gen9_enable_rc6()], no other changes == GPU hangs. (3) No changes to drm-tip kernel == GPU hangs. I'm guessing that there's something that RC6 allows which can cause the transcoder GPU hangs to occur, but whatever that is, it's not related to coarse power gating. I will proceed with placing both changes (RC6 disable + Coarse power gating disable) into a kernel. I'm expecting the GPU not to hang/crash.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>