Bug 112287

Summary: [CI][RESUME]igt@gem_ctx_shared@exec-shared-gtt-render - fail - Failed assertion: *s == 0xc0ffee
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED MOVED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: minor    
Priority: medium CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: TGL i915 features: GEM/Other

Description Lakshmi 2019-11-14 16:48:20 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7325/re-tgl-u/igt@gem_ctx_shared@exec-shared-gtt-render.html
Starting subtest: exec-shared-gtt-render
(gem_ctx_shared:1962) CRITICAL: Test assertion failure function exec_shared_gtt, file ../tests/i915/gem_ctx_shared.c:272:
(gem_ctx_shared:1962) CRITICAL: Failed assertion: *s == 0xc0ffee
(gem_ctx_shared:1962) CRITICAL: error: 0x5000000 != 0xc0ffee
Subtest exec-shared-gtt-render failed.
Comment 1 CI Bug Log 2019-11-14 16:49:09 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@gem_ctx_shared@exec-shared-gtt-render - fail - Failed assertion: *s == 0xc0ffee
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7325/re-tgl-u/igt@gem_ctx_shared@exec-shared-gtt-render.html
Comment 2 Chris Wilson 2019-11-14 23:36:18 UTC
Worst case, our invalidation is not strong enough for the vm switch. Best case, this is just another tgl mystery fail.
Comment 3 Francesco Balestrieri 2019-11-27 08:12:31 UTC
Seen once so far.
Comment 4 Francesco Balestrieri 2019-11-27 08:13:34 UTC
Setting to NEEDINFO while waiting to see if it happens again.
Comment 5 Martin Peres 2019-11-29 19:47:55 UTC
-- 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/intel/issues/607.

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.