[Bug 106099] [CI] igt at gem_exec_reloc@basic-wc-(gtt|cpu)* - fail - Failed assertion: reloc.presumed_offset == offset

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Sep 20 17:29:31 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=106099

Martin Peres <martin.peres at free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |---
             Status|RESOLVED                    |REOPENED

--- Comment #8 from Martin Peres <martin.peres at free.fr> ---
(In reply to Chris Wilson from comment #7)
> Fingers crossed, but
> 
> commit fddcd00a49e9122a3579247151e9cb3ce5a1a36e
> Author: Chris Wilson <chris at chris-wilson.co.uk>
> 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 <chris at chris-wilson.co.uk>
>     Reviewed-by: Joonas Lahtinen <joonas.lahtinen at linux.intel.com>
>     Link:
> https://patchwork.freedesktop.org/patch/msgid/20180903083337.13134-3-
> chris at chris-wilson.co.uk
> 
> seems a more than likely suspect.

This still happened days later:
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_108/fi-gdg-551/igt@gem_exec_reloc@basic-wc-cpu-noreloc.html

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180920/783eeac8/attachment.html>


More information about the intel-gfx-bugs mailing list