Bug 105457 - [CI] igt@gem_ctx_isolation@rcs0-reset - fail - Test assertion failure function compare_regs - 113 registers mistached between dirty 33333333 context
Summary: [CI] igt@gem_ctx_isolation@rcs0-reset - fail - Test assertion failure functio...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-12 12:25 UTC by Marta Löfstedt
Modified: 2018-03-28 05:47 UTC (History)
1 user (show)

See Also:
i915 platform: CFL
i915 features: GEM/Other


Attachments

Comment 1 Chris Wilson 2018-03-27 21:52:02 UTC
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>
Comment 2 Marta Löfstedt 2018-03-28 05:47:47 UTC
I will close this, the machine has been re-named to fi-cfl-s3 so I can't get data showing that the fix worked.


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.