<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><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> changed
<a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI] igt@gem_exec_reloc@basic-wc-(gtt|cpu)* - fail - Failed assertion: reloc.presumed_offset == offset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106099">bug 106099</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>FIXED
</td>
<td>---
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>RESOLVED
</td>
<td>REOPENED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI] igt@gem_exec_reloc@basic-wc-(gtt|cpu)* - fail - Failed assertion: reloc.presumed_offset == offset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106099#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [CI] igt@gem_exec_reloc@basic-wc-(gtt|cpu)* - fail - Failed assertion: reloc.presumed_offset == offset"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106099">bug 106099</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=106099#c7">comment #7</a>)
<span class="quote">> Fingers crossed, but
>
> commit fddcd00a49e9122a3579247151e9cb3ce5a1a36e
> Author: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> Date: Mon Sep 3 09:33:35 2018 +0100
>
> drm/i915: Force the slow path after a user-write error
>
> If we fail to write the user relocation back when it is changed, force
> ourselves to take the slow relocation path where we can handle faults in
> the write path. There is still an element of dubiousness as having
> patched up the batch to use the correct offset, it no longer matches the
> presumed_offset in the relocation, so a second pass may miss any changes
> in layout.
>
> Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>>
> Reviewed-by: Joonas Lahtinen <<a href="mailto:joonas.lahtinen@linux.intel.com">joonas.lahtinen@linux.intel.com</a>>
> Link:
> <a href="https://patchwork.freedesktop.org/patch/msgid/20180903083337.13134-3">https://patchwork.freedesktop.org/patch/msgid/20180903083337.13134-3</a>-
> <a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>
>
> seems a more than likely suspect.</span >
This still happened days later:
<a href="https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_108/fi-gdg-551/igt@gem_exec_reloc@basic-wc-cpu-noreloc.html">https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_108/fi-gdg-551/igt@gem_exec_reloc@basic-wc-cpu-noreloc.html</a></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 the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>