<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [regression] [bisected] i915 GPU HANG: ecode 7:1:0xfffffffe on Kernel 5.1.x and 5.2rc1 to 5.2rc6"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111014#c37">Comment # 37</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - [regression] [bisected] i915 GPU HANG: ecode 7:1:0xfffffffe on Kernel 5.1.x and 5.2rc1 to 5.2rc6"
href="https://bugs.freedesktop.org/show_bug.cgi?id=111014">bug 111014</a>
from <span class="vcard"><a class="email" href="mailto:digetx@gmail.com" title="Dmitry Osipenko <digetx@gmail.com>"> <span class="fn">Dmitry Osipenko</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=111014#c18">comment #18</a>)
<span class="quote">> See commit 928f8f42310f244501a7c70daac82c196112c190
> Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> Date: Fri Apr 19 12:17:47 2019 +0100
>
> drm/i915/ringbuffer: EMIT_INVALIDATE *before* switch context
>
> Despite what I think the prm recommends, commit f2253bd9859b
> ("drm/i915/ringbuffer: EMIT_INVALIDATE after switch context") turned out
> to be a huge mistake when enabling Ironlake contexts as the GPU would
> hang on either a MI_FLUSH or PIPE_CONTROL immediately following the
> MI_SET_CONTEXT of an active mesa context (more vanilla contexts, e.g.
> simple rendercopies with igt, do not suffer).</span >
This fixes super-annoying hangs on Ivy Bridge with v5.1.15. Thanks for the
pointer!</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<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>