[Bug 83647] [all Bisected]igt/gem_persistent_relocs and igt/gem_reloc_vs_gpu some subcases timeout

[bugzilla-daemon at freedesktop.org]

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

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

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

--- Comment #3 from Chris Wilson <chris at chris-wilson.co.uk> ---
I still have no idea how this is the first time it showed up, but

commit ab4a7b96c7c9980f306730eee7667639d6221ef2
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Tue Sep 9 11:16:08 2014 +0100

    drm/i915: Objects on the unbound list may still have an active reference

    Due to the lazy retirement semantics, even though we have unbound an
    object, it may still hold onto an active reference. So in the debug code,
    play safe.

    v2: Export i915_gem_shrink() rather than opencoding it.

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>

should be the last fix we ever need for drop_caches (tm)!

And I think

commit ace110dfad1b9ac2c724e1c1251c0faa8a408fa1
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Tue Sep 9 07:02:43 2014 +0100

    drm/i915: Drop any active reference before unbinding

    Before we process the final unbind on an object and move it to the
    unbound list, it is semantically cleaner if there are no more active
    references to the object. (An active reference would imply that it was
    still being accessed by the GPU after it became inaccessible.) The
    caveat is that all callsites must be prepared for the object to
    disappeared during the unbind - i.e. they must hold their own reference.

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>

is the root cause.

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