[Bug 103502] GPU HANG: ecode 3:0:0x7c9bf89c, in Xorg [781], reason: Hang on rcs0, action: reset

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Oct 30 10:09:54 UTC 2017


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

--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
Hmm, tiling alarm bells for i915gm:

Active (rcs0) [14]:
    00000000_0050b000    57344 3e 02 [ 36f00 00 00 00 00 ] 00 Y dirty uncache
...
0x00507034:      0x7d8e0001: 3DSTATE_BUFFER_INFO
0x00507038:      0x03600800:    color, tiling = Y, pitch=2048
0x0050703c:      0x0050b000:    address

Unease as we tend to assume these implicit fencing require the "unfenced"
alignment. Likely we reused an offset and failed to notice a change in
alignment constraints. Something like:

diff --git a/drivers/gpu/drm/i915/i915_gem_execbuffer.c
b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
index 3d7190764f10..7f53b4860428 100644
--- a/drivers/gpu/drm/i915/i915_gem_execbuffer.c
+++ b/drivers/gpu/drm/i915/i915_gem_execbuffer.c
@@ -331,6 +331,10 @@ eb_vma_misplaced(const struct drm_i915_gem_exec_object2
*entry,
        if (entry->alignment && !IS_ALIGNED(vma->node.start, entry->alignment))
                return true;

+       if (flags & __EXEC_OBJECT_NEEDS_MAP &&
+           !IS_ALIGNED(vma->node.start, vma->fence_alignment))
+               return true;
+
        if (flags & EXEC_OBJECT_PINNED &&
            vma->node.start != entry->offset)
                return true;

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


More information about the intel-gfx-bugs mailing list