[Bug 73696] [915gm TearFree] slow, screen corruption due to EDEADLK (fence starvation)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Jan 21 13:36:34 PST 2014


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

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

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

--- Comment #23 from Chris Wilson <chris at chris-wilson.co.uk> ---
commit 4983005fd5eaa7594a830f35f91d7d4d983548ca
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Mon Jan 20 10:17:36 2014 +0000

    drm/i915: Wait for completion of pending flips when starved of fences

    On older generations (gen2, gen3) the GPU requires fences for many
    operations, such as blits. The display hardware also requires fences for
    scanouts and this leads to a situation where an arbitrary number of
    fences may be pinned by old scanouts following a pageflip but before we
    have executed the unpin workqueue. This is unpredictable by userspace
    and leads to random EDEADLK when submitting an otherwise benign
    execbuffer. However, we can detect when we have an outstanding flip and
    so cause userspace to wait upon their completion before finally
    declaring that the system is starved of fences. This is really no worse
    than forcing the GPU to stall waiting for older execbuffer to retire and
    release their fences before we can reallocate them for the next
    execbuffer.

    v2: move the test for a pending fb unpin to a common routine for
    later reuse during eviction

    Reported-and-tested-by: dimon at gmx.net
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=73696
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Reviewed-by: Jon Bloomfield <jon.bloomfield at intel.com>
    Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>

-- 
You are receiving this mail because:
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: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140121/113ed317/attachment.html>


More information about the intel-gfx-bugs mailing list