Skip to content
Snippets Groups Projects
New look: Off

igt@gem_ctx_persistence@engines-mixed@vcs0 - fail - Failed assertion: wait_for_status(fence[2], reset_timeout_ms) == -5

    • Closed Issue created by LAKSHMINARAYANA VUDUM @l4kshmi

    https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8633/shard-skl3/igt@gem_ctx_persistence@engines-mixed@vcs0.html

    Starting dynamic subtest: vcs0
(gem_ctx_persistence:5513) CRITICAL: Test assertion failure function test_nonpersistent_mixed, file ../tests/i915/gem_ctx_persistence.c:260:
(gem_ctx_persistence:5513) CRITICAL: Failed assertion: wait_for_status(fence[2], reset_timeout_ms) == -5
(gem_ctx_persistence:5513) CRITICAL: error: -62 != -5
Dynamic subtest vcs0 failed.
    To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information

    Child items ...

    • Activity

    • LAKSHMINARAYANA VUDUM added feature: GEM platform: SKL labels

      added feature: GEM platform: SKL labels

    • CI Bug Log
      CI Bug Log @cibuglog ·
      Reporter

      The CI Bug Log issue associated to this bug has been updated by Lakshmi Vudum.

      New filters associated

    • Chris Wilson
      Chris Wilson @ickle ·
      Reporter

      Aside from it being the slow skl, there should be less issues with CPU scheduling in this test [albeit ksoftirqd to ruin the day]. Another one that wants engine info dumping.

    • CI Bug Log
      CI Bug Log @cibuglog ·
      Reporter

      A CI Bug Log filter associated to this bug has been updated by Lakshmi Vudum:

      Description: SKL: igt@gem_ctx_persistence@engines-mixed@vcs0* - fail - Failed assertion: wait_for_status(fence[2], reset_timeout_ms) == -5

      Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["shard-skl", "shard-skl1", "shard-skl2", "shard-skl3", "shard-skl4", "shard-skl5", "shard-skl6", "fi-skl-6770hq", "shard-skl7", "shard-skl8", "shard-skl9", "fi-skl-6260u", "shard-skl10", "fi-skl-lmem", "fi-skl-6700hq", "fi-skl-6600u", "fi-skl-6700k2", "fi-skl-gvtdvm", "fi-skl-guc", "fi-skl-iommu", "fi-skl-caroline"] OR machine_tag IS IN ["SKL"]) AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@gem_ctx_persistence@engines-mixed@vcs0", "igt@gem_ctx_persistence@legacy-engines-mixed@vebox", "igt@gem_ctx_persistence@legacy-engines-mixed@render", "igt@gem_ctx_persistence@legacy-engines-mixed@blt", "igt@gem_ctx_persistence@legacy-engines-mixed@bsd1", "igt@gem_ctx_persistence@legacy-engines-mixed@bsd", "igt@gem_ctx_persistence@legacy-engines-mixed@bsd2", "igt@gem_ctx_persistence@legacy-engines-mixed@default"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["fail"])) AND stderr ~= 'Failed assertion: wait_for_status\(fence\[2\], reset_timeout_ms\) == -5'

      No new failures caught with the new filter

    • LAKSHMINARAYANA VUDUM
      LAKSHMINARAYANA VUDUM @l4kshmi ·
      Author Reporter

      Also seen on TGL https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_532/fi-tgl-y/igt@gem_ctx_persistence@engines-mixed@vecs0.html

      Starting dynamic subtest: vecs0
(gem_ctx_persistence:3793) CRITICAL: Test assertion failure function test_nonpersistent_mixed, file ../tests/i915/gem_ctx_persistence.c:260:
(gem_ctx_persistence:3793) CRITICAL: Failed assertion: wait_for_status(fence[2], reset_timeout_ms) == -5
(gem_ctx_persistence:3793) CRITICAL: error: -62 != -5
Dynamic subtest vecs0 failed.
**** DEBUG ****
(gem_ctx_persistence:3793) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(gem_ctx_persistence:3793) DEBUG: Test requirement passed: gem_engine_property_printf(i915, name, ATTR, "%d", 50) > 0
(gem_ctx_persistence:3793) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_ctx_persistence:3793) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_ctx_persistence:3793) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_ctx_persistence:3793) CRITICAL: Test assertion failure function test_nonpersistent_mixed, file ../tests/i915/gem_ctx_persistence.c:260:
(gem_ctx_persistence:3793) CRITICAL: Failed assertion: wait_for_status(fence[2], reset_timeout_ms) == -5
(gem_ctx_persistence:3793) CRITICAL: error: -62 != -5
(gem_ctx_persistence:3793) igt_core-INFO: Stack trace:
(gem_ctx_persistence:3793) igt_core-INFO:   #0 ../lib/igt_core.c:1727 __igt_fail_assert()
(gem_ctx_persistence:3793) igt_core-INFO:   #1 [test_nonpersistent_mixed+0x17d]
(gem_ctx_persistence:3793) igt_core-INFO:   #2 ../tests/i915/gem_ctx_persistence.c:1092 do_test()
(gem_ctx_persistence:3793) igt_core-INFO:   #3 ../tests/i915/gem_ctx_persistence.c:1192 __real_main1107()
(gem_ctx_persistence:3793) igt_core-INFO:   #4 ../tests/i915/gem_ctx_persistence.c:1107 main()
(gem_ctx_persistence:3793) igt_core-INFO:   #5 ../csu/libc-start.c:344 __libc_start_main()
(gem_ctx_persistence:3793) igt_core-INFO:   #6 [_start+0x2a]
****  END  ****
Dynamic subtest vecs0: FAIL (0.287s)
Subtest engines-mixed: FAIL (0.532s)
````
On SKL issue only once CI_DRM_8633_full (2 weeks, 5 days old). Now seen on TGL as well.
@ickle Do you recommend to file a separate bug for TGL?
    • CI Bug Log
      CI Bug Log @cibuglog ·
      Reporter

      A CI Bug Log filter associated to this bug has been updated by Lakshmi Vudum:

      Description: SKL TGL: igt@gem_ctx_persistence@engines-mixed@* - fail - Failed assertion: wait_for_status(fence[2], reset_timeout_ms) == -5

      Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["shard-skl", "shard-skl1", "shard-skl2", "shard-skl3", "shard-skl4", "shard-skl5", "shard-skl6", "fi-skl-6770hq", "shard-skl7", "shard-skl8", "shard-skl9", "fi-skl-6260u", "shard-skl10", "fi-skl-lmem", "fi-skl-6700hq", "fi-skl-6600u", "fi-tgl-u", "re-tgl-u", "fi-tgl-u2", "shard-tglb1", "shard-tglb2", "shard-tglb3", "shard-tglb4", "shard-tglb5", "shard-tglb6", "re-tgl1-display", "re-tgl2-display", "shard-tglb7", "shard-tglb8", "shard-tglb0", "fi-tgl-y", "re-tgl-y", "fi-skl-6700k2", "re-tgl-cham", "shard-tglb9", "fi-tgl-guc", "fi-skl-gvtdvm", "fi-tgl-dsi", "re-tgl-u2", "ba-tgl-1", "fi-skl-guc", "custom-tgl-joshikun", "tgl-u-lpddr-ba", "re-tgl-u3", "fi-tgl-h", "fi-skl-iommu", "fi-skl-caroline"] OR machine_tag IS IN ["TGL", "SKL"]) AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@gem_ctx_persistence@engines-mixed@vcs1", "igt@gem_ctx_persistence@engines-mixed@vcs0", "igt@gem_ctx_persistence@legacy-engines-mixed@vebox", "igt@gem_ctx_persistence@legacy-engines-mixed@render", "igt@gem_ctx_persistence@engines-mixed@rcs0", "igt@gem_ctx_persistence@engines-mixed@bcs0", "igt@gem_ctx_persistence@legacy-engines-mixed@blt", "igt@gem_ctx_persistence@legacy-engines-mixed@bsd1", "igt@gem_ctx_persistence@legacy-engines-mixed@bsd", "igt@gem_ctx_persistence@legacy-engines-mixed@bsd2", "igt@gem_ctx_persistence@legacy-engines-mixed@default", "igt@gem_ctx_persistence@engines-mixed@vecs0"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["fail"])) AND stderr ~= 'Failed assertion: wait_for_status\(fence\[2\], reset_timeout_ms\) == -5'

      New failures caught by the filter:

    • LAKSHMINARAYANA VUDUM
      LAKSHMINARAYANA VUDUM @l4kshmi ·
      Author Reporter

      +TGL

    • LAKSHMINARAYANA VUDUM closed

      closed

    • LAKSHMINARAYANA VUDUM added platform: TGL label

      added platform: TGL label

    • CI Bug Log
      CI Bug Log @cibuglog ·
      Reporter

      A CI Bug Log filter associated to this bug has been updated by Lakshmi Vudum:

      Description: SKL TGL: igt@gem_ctx_persistence@engines-mixed@* - fail - Failed assertion: wait_for_status(fence[2], reset_timeout_ms) == -5

      Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["shard-skl", "shard-skl1", "shard-skl2", "shard-skl3", "shard-skl4", "shard-skl5", "shard-skl6", "fi-skl-6770hq", "shard-skl7", "shard-skl8", "shard-skl9", "fi-skl-6260u", "shard-skl10", "fi-skl-lmem", "fi-skl-6700hq", "fi-skl-6600u", "fi-skl-6700k2", "fi-skl-gvtdvm", "fi-skl-guc", "fi-skl-iommu", "fi-skl-caroline"] OR machine_tag IS IN ["TGL", "SKL"]) AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@gem_ctx_persistence@engines-mixed@vcs1", "igt@gem_ctx_persistence@engines-mixed@vcs0", "igt@gem_ctx_persistence@legacy-engines-mixed@vebox", "igt@gem_ctx_persistence@legacy-engines-mixed@render", "igt@gem_ctx_persistence@engines-mixed@rcs0", "igt@gem_ctx_persistence@engines-mixed@bcs0", "igt@gem_ctx_persistence@legacy-engines-mixed@blt", "igt@gem_ctx_persistence@legacy-engines-mixed@bsd1", "igt@gem_ctx_persistence@legacy-engines-mixed@bsd", "igt@gem_ctx_persistence@legacy-engines-mixed@bsd2", "igt@gem_ctx_persistence@legacy-engines-mixed@default", "igt@gem_ctx_persistence@engines-mixed@vecs0"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["fail"])) AND stderr ~= 'Failed assertion: wait_for_status\(fence\[2\], reset_timeout_ms\) == -5'

      No new failures caught with the new filter

    • CI Bug Log
      CI Bug Log @cibuglog ·
      Reporter

      The CI Bug Log issue associated to this bug has been archived.

      New failures matching the above filters will not be associated to this bug anymore.

    • Chris Wilson marked #3061 (closed) as a duplicate of this issue

      marked #3061 (closed) as a duplicate of this issue

    • Chris Wilson marked this issue as related to #3061 (closed)

      marked this issue as related to #3061 (closed)

    Please register or sign in to reply