<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [HSW gt1] GPU HANG: ecode 0:0x87d3bffa on ctx load" href="https://bugs.freedesktop.org/show_bug.cgi?id=83677#c132">Comment # 132</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [HSW gt1] GPU HANG: ecode 0:0x87d3bffa on ctx load" href="https://bugs.freedesktop.org/show_bug.cgi?id=83677">bug 83677</a> from <a class="email" href="mailto:myfoolishgames@gmail.com" title="dhead666 <myfoolishgames@gmail.com>"> dhead666</a> <pre>The huge patch that ported to 3.17.4 by Hugh Greenberg is working very well for me. After a day of work with the system I didn't experience any freezes or hangs with Chromium or at all. I only kept the kernel parameter i915.modeset=1. I did experienced a rare slowdown of Chromium with a segfault in journald, I didn't saw such segfault before. kernel: WebCore: Worker[15893]: segfault at fbadbeef ip 00007f75abde2e25 sp 00007f758d175190 error 6 in chromium[7f75a993d000+5b6f000 What changed from upstream kernel is that with upstream: * when no kernel parameter used (except i915.modeset=1) Chromium would hangs and would force me to kill it. * when using the parameters: i915.modeset=1 i915.semaphores=0 i915.use_mmio_flip=1 i915.enable_ppgtt=1 drm.vblankoffdelay=1, instead of hanging, Chromium would slow down the system to almost a halt, Kodi would also triger such slowdowns (in much higher rate than with the patch), it seems like i915.semaphores=0 is the one making the difference between hang to slowdown. I didn't gave much attention to testing vaapi, but it does seem works fine.</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> </ul> </body> </html>