| Summary: | [CI][SHARDS] igt@gem_ctx_isolation@vcs1-nonpriv - fail - igt@gem_ctx_isolation@vcs1-nonpriv - fail - Failed assertion: num_errors == 0, registers mistached between nonpriv read/writes | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Lakshmi <lakshminarayana.vudum> |
| Component: | IGT | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | high | CC: | intel-gfx-bugs |
| Version: | DRI git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | ICL, TGL | i915 features: | GEM/Other |
|
Description
Lakshmi
2019-08-08 08:28:59 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@gem_ctx_isolation@vcs1-nonpriv - fail - Failed assertion: num_errors == 0, registers mistached between nonpriv read/writes - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13897/shard-iclb2/igt@gem_ctx_isolation@vcs1-nonpriv.html - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_4714/shard-iclb2/igt@gem_ctx_isolation@vcs1-nonpriv.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6648/shard-iclb2/igt@gem_ctx_isolation@vcs1-nonpriv.html - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_4717/shard-iclb2/igt@gem_ctx_isolation@vcs1-nonpriv.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13905/shard-iclb2/igt@gem_ctx_isolation@vcs1-nonpriv.html - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13906/shard-iclb4/igt@gem_ctx_isolation@vcs1-nonpriv.html There are two problems here, the first being the uncertain mapping of BSD2 which will be fixed. However, the other is a bit more insidous in that we transparently map BSD2 onto vcs2 and here we are checking vcs1 CS_GPR which will also technically be in a foreign powerwell and foreign context. Related fix in commit f1c4d157ab9b13c1228f3b8ad7747126785460d0 (HEAD -> drm-intel-next-queued, drm-intel/for-linux-next, drm-intel/drm-intel-next-queued) Author: Chris Wilson <chris@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@chris-wilson.co.uk> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> #v1 Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190808110612.23539-2-chris@chris-wilson.co.uk commit d5b2a3a4f85ad135123db8fc97ccdbf893546330 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Aug 9 13:31:53 2019 +0100 drm/i915: Check for a second VCS engine more carefully Yup, this needs to engine->mmio_base aware. Or learn about relative addressing for gen11. A CI Bug Log filter associated to this bug has been updated:
{- ICL: igt@gem_ctx_isolation@vcs1-nonpriv - fail - Failed assertion: num_errors == 0, registers mistached between nonpriv read/writes -}
{+ ICL TGL: igt@gem_ctx_isolation@vcs1-nonpriv -*- fail - Failed assertion: num_errors == 0, registers mistached between nonpriv read/writes +}
New failures caught by the filter:
* https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5208/shard-iclb1/igt@gem_ctx_isolation@vcs1-nonpriv-switch.html
Nice to see this post here and thanks for sharing this to us. Keep sharing the new posts like this. see here https://reynardsnyc.com & https://www.uwgw.org Based on off-line discussion, it appears that this needs to be fixed in IGT. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/28. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.