https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-skl-guc/igt@gem_ctx_isolation@bcs0-reset.html (gem_ctx_isolation:2780) WARNING: Register 0x22200 (BCS_SWCTRL): A=00009ead B=00000000 ... (gem_ctx_isolation:2780) WARNING: Register 0x2267c (BCS_GPR[31]): A=deadbeef B=00000000 (gem_ctx_isolation:2780) CRITICAL: Test assertion failure function compare_regs, file ../tests/gem_ctx_isolation.c:441: (gem_ctx_isolation:2780) CRITICAL: Failed assertion: num_errors == 0 (gem_ctx_isolation:2780) CRITICAL: 33 registers mistached between dirty deadbeef context
Maybe should be duplicate on bug 105457.
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_7/fi-cfl-8700k/igt@gem_ctx_isolation@rcs0-reset.html (gem_ctx_isolation:1384) CRITICAL: Test assertion failure function compare_regs, file ../tests/gem_ctx_isolation.c:441: (gem_ctx_isolation:1384) CRITICAL: Failed assertion: num_errors == 0 (gem_ctx_isolation:1384) CRITICAL: 113 registers mistached between dirty deadbeef context
commit 0a393229479d61829a2f8671c1a46f533c76b385 (HEAD, upstream/master) Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Mar 27 14:44:30 2018 +0100 igt/gem_ctx_isolation: Reset a scratch context If we inject a reset into the target context, there is a risk that the register state is never saved back to memory. The exact interaction between reset, the context image and the precise timing of our execution are not well defined. Since we cannot ensure that the context image remains valid, force a context switch prior to the reset. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105270 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105457 Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105545 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
I will monitor this to hopefully close on coming drmtip runs.
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.