[Bug 111327] [CI][SHARDS] igt at gem_ctx_shared@exec-single-timeline-bsd2 - fail - Failed assertion: nop_sync(i915, ctx, engine, (1000*(1000*(1000)))) == 0

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Aug 8 15:14:11 UTC 2019


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
I think the issue here is related to

commit f1c4d157ab9b13c1228f3b8ad7747126785460d0 (HEAD -> drm-intel-next-queued,
drm-intel/for-linux-next, drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Thu Aug 8 12:06:12 2019 +0100

    drm/i915: Fix up the inverse mapping for default ctx->engines[]

    The order in which we store the engines inside default_engines() for the
    legacy ctx->engines[] has to match the legacy I915_EXEC_RING selector
    mapping in execbuf::user_map. If we present VCS2 as being the second
    instance of the video engine, legacy userspace calls that I915_EXEC_BSD2
    and so we need to insert it into the second video slot.

    v2: Record the legacy mapping (hopefully we can remove this need in the
    future)

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111328
    Fixes: 2edda80db3d0 ("drm/i915: Rename engines to match their user
interface")
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Reviewed-by: Mika Kuoppala <mika.kuoppala at linux.intel.com> #v1
    Reviewed-by: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20190808110612.23539-2-chris@chris-wilson.co.uk

but I'm not sure, as my understanding for the bug is that we oversubscribed to
an engine and blocked ourselves.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee 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/20190808/882ef69d/attachment.html>


More information about the intel-gfx-bugs mailing list