<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI] igt@gem_eio@in-flight-suspend - incomplete - GEM_BUG_ON(buf[2 * head + 1] != port->context_id)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106702#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI] igt@gem_eio@in-flight-suspend - incomplete - GEM_BUG_ON(buf[2 * head + 1] != port->context_id)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106702">bug 106702</a>
from <span class="vcard"><a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> <span class="fn">Martin Peres</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=106702#c2">comment #2</a>)
<span class="quote">> (In reply to Martin Peres from <a href="show_bug.cgi?id=106702#c1">comment #1</a>)
> > This looks like a regression introduced in drmtip_51, so bumping the
> > priority as Linux 4.17 is about to be released.
>
> tip is targetting 4.18. </span >
Sure, but the problem may be found in linus' tip and introduced here as a
backmerge. If you can tell me that this is not the case, then we can lower the
priority.
<span class="quote">> Iiuc, the trace can only be generated by gem_eio as
> it requires both simulating a suspend with TEST_DEVICES and disabling the
> GPU reset. It should be fixed by
> <a href="https://patchwork.freedesktop.org/patch/225442/">https://patchwork.freedesktop.org/patch/225442/</a> and if my reckoning is
> correct, we could have hit this since
>
> commit ac697ae8013a7c7301174c9c3b02a92fe418b7ea
> Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> Date: Thu Mar 15 15:10:15 2018 +0000
>
> drm/i915: Stop engines when declaring the machine wedged</span >
Thanks! Let's see :)</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>