[Bug 107769] [CI][DRMTIP] igt at gem_persistent_relocs@forked-faulting-reloc-thrashing - fail - Failed assertion: test == 0xdeadbeef

[bugzilla-daemon at freedesktop.org]

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

Chris Wilson <chris at chris-wilson.co.uk> changed:

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

--- Comment #9 from Chris Wilson <chris at chris-wilson.co.uk> ---
More fingers crossed, worksforme at least,

commit 06348d3086a3b34f2db6c7692b4327fb7fc0b6c7 (HEAD -> drm-intel-next-queued,
drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Tue Sep 4 07:38:02 2018 +0100

    drm/i915/ringbuffer: Move double invalidate to after pd flush

    Continuing the fun of trying to find exactly the delay that is
    sufficient to ensure that the page directory is fully loaded between
    context switches, move the extra flush added in commit 70b73f9ac113
    ("drm/i915/ringbuffer: Delay after invalidating gen6+ xcs") to just
    after we flush the pd. Entirely based on the empirical data of running
    failing tests in a loop until we survive a day (before the mtbf is 10-30
    minutes).

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107769
    References: 70b73f9ac113 ("drm/i915/ringbuffer: Delay after invalidating
gen6+ xcs")
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Acked-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20180904063802.13880-1-chris@chris-wilson.co.uk

Let's see what test case remains troublesome after that!

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