igt@gem_ctx_persistence@processes - fail - Failed assertion: wait_for_status(fence, reset_timeout_ms) == -5

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8189/shard-skl10/igt@gem_ctx_persistence@processes.html

Starting subtest: processes
(gem_ctx_persistence:1160) CRITICAL: Test assertion failure function test_processes, file ../tests/i915/gem_ctx_persistence.c:750:
(gem_ctx_persistence:1160) CRITICAL: Failed assertion: wait_for_status(fence, reset_timeout_ms) == -5
(gem_ctx_persistence:1160) CRITICAL: Last errno: 2, No such file or directory
(gem_ctx_persistence:1160) CRITICAL: error: -62 != -5
Subtest processes failed.

added feature: GEM platform: SKL labels

Similar issue #679 (closed).

Definitely worth starting afresh now that it appears reasonably clean again, and what remains is likely worrying.

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

New filters associated

• SKL: igt@gem_ctx_persistence@processes - fail - Failed assertion: wait_for_status(fence, reset_timeout_ms) == -5
  • https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8189/shard-skl10/igt@gem_ctx_persistence@processes.html

added platform: BXT label

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

New filters associated

• GEN9: igt@gem_ctx_persistence@.* - fail - Failed assertion: wait_for_status(fence[0], reset_timeout_ms) == -5
  • https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5539/shard-skl5/igt@gem_ctx_persistence@engines-mixed-process@vcs0.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8194/shard-apl7/igt@gem_ctx_persistence@legacy-engines-mixed-process@bsd.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_459/fi-apl-guc/igt@gem_ctx_persistence@legacy-engines-mixed-process@bsd.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17090/shard-kbl6/igt@gem_ctx_persistence@engines-mixed-process@rcs0.html

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

Description: SKGEN9 TGL: igt@gem_ctx_persistence@processes - fail - Failed assertion: wait_for_status(fence, reset_timeout_ms) == -5

Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["shard-kbl3", "fi-glk-1", "shard-glkb1", "shard-glkb3", "shard-apl6", "fi-skl-6770hq", "fi-skl-6260u", "shard-apl2", "shard-kbl5", "fi-bxt-j4205", "shard-kbl4", "shard-glkb6", "shard-glkb2", "shard-kbl7", "fi-skl-6700hq", "fi-skl-6600u", "shard-apl5", "shard-apl7", "fi-bxt-dsi", "shard-glkb4", "shard-apl8", "shard-apl1", "fi-glk-dsi", "fi-kbl-7500u", "shard-kbl6", "shard-apl4", "shard-glkb5", "shard-kbl1", "fi-kbl-7560u", "shard-apl3", "fi-skl-6700k2", "fi-kbl-r", "fi-kbl-7567u", "fi-cfl-s2", "fi-skl-gvtdvm", "shard-kbl2", "fi-skl-guc", "fi-cfl-8700k", "fi-cfl-u", "fi-cfl-s3", "fi-glk-j4005", "shard-apl", "shard-glk", "shard-kbl", "shard-glk1", "shard-glk3", "shard-glk4", "shard-glk5", "shard-glk2", "shard-glkb", "shard-glk8", "shard-glk6", "shard-glk7", "pig-skl-6600", "pig-glk-j4005", "pig-glk-j5005", "fi-cfl-guc", "fi-kbl-guc", "fi-cfl-u2", "pig-skl-6260u", "fi-whl-u", "fi-kbl-x1275", "shard-glk9", "fi-cfl-8109u", "fi-skl-iommu", "fi-kbl-8809g", "fi-skl-caroline", "fi-apl-nasher", "fi-kbl-soraka", "shard-skl", "shard-skl1", "shard-skl2", "shard-skl3", "shard-skl4", "shard-skl5", "shard-skl6", "shard-skl7", "shard-skl8", "shard-skl9", "shard-skl10", "fi-apl-guc", "fi-skl-lmem", "fi-cml-u", "re-cml-u", "fi-cml-u2", "fi-tgl-u", "fi-cml-h", "fi-cml-s", "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-apl0", "shard-glk0", "shard-kbl0", "shard-skl0", "shard-tglb0", "fi-tgl-y", "re-tgl-y", "shard-tglb9", "re-tgl-cham", "fi-tgl-guc", "re-tgl-u2", "fi-tgl-dsi", "ba-tgl-1"] OR machine_tag IS IN ["SKTGL", "GEN9"]) AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@gem_ctx_persistence@processes"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["fail"])) AND stderr ~= 'Failed assertion: wait_for_status\(fence, reset_timeout_ms\) == -5'

New failures caught by the filter:

• https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8195/shard-tglb2/igt@gem_ctx_persistence@processes.html
• https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_461/fi-kbl-guc/igt@gem_ctx_persistence@processes.html

added platform: GEN9 platform: KBL platform: TGL labels

added platform: ICL label

@ickle CI Buglog continues reporting it, e.g. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8262/shard-skl6/igt@gem_ctx_persistence@engines-mixed-process@rcs0.html

Is it still the same issue?

assigned to @baleboy

Suspected CPU scheduling delay, minor severity.

added priority::low severity::minor labels

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

Description: GEN9 ICL TGL: igt@gem_ctx_persistence@processes - fail - Failed assertion: wait_for_status(fence, reset_timeout_ms) == -5

Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["shard-kbl3", "fi-glk-1", "shard-glkb1", "shard-glkb3", "shard-apl6", "fi-skl-6770hq", "fi-skl-6260u", "shard-apl2", "shard-kbl5", "fi-bxt-j4205", "shard-kbl4", "shard-glkb6", "shard-glkb2", "shard-kbl7", "fi-skl-6700hq", "fi-skl-6600u", "shard-apl5", "shard-apl7", "fi-bxt-dsi", "shard-glkb4", "shard-apl8", "shard-apl1", "fi-glk-dsi", "fi-kbl-7500u", "shard-kbl6", "shard-apl4", "shard-glkb5", "shard-kbl1", "fi-kbl-7560u", "shard-apl3", "fi-skl-6700k2", "fi-kbl-r", "fi-kbl-7567u", "fi-cfl-s2", "fi-skl-gvtdvm", "shard-kbl2", "fi-skl-guc", "fi-cfl-8700k", "fi-cfl-u", "fi-cfl-s3", "fi-glk-j4005", "shard-apl", "shard-glk", "shard-kbl", "shard-glk1", "shard-glk3", "shard-glk4", "shard-glk5", "shard-glk2", "shard-glkb", "shard-glk8", "shard-glk6", "shard-glk7", "pig-skl-6600", "pig-glk-j4005", "pig-glk-j5005", "fi-cfl-guc", "fi-kbl-guc", "fi-cfl-u2", "pig-skl-6260u", "fi-whl-u", "fi-kbl-x1275", "shard-glk9", "fi-cfl-8109u", "fi-skl-iommu", "fi-kbl-8809g", "fi-icl-u", "fi-skl-caroline", "fi-apl-nasher", "fi-kbl-soraka", "shard-skl", "shard-skl1", "shard-skl2", "shard-skl3", "shard-skl4", "shard-skl5", "shard-skl6", "shard-skl7", "shard-skl8", "shard-skl9", "fi-icl-u2", "shard-skl10", "fi-apl-guc", "shard-iclb", "shard-iclb1", "shard-iclb2", "shard-iclb3", "shard-iclb4", "shard-iclb5", "shard-iclb6", "fi-icl-u3", "shard-iclb7", "fi-icl-y", "fi-skl-lmem", "shard-iclb8", "fi-icl-guc", "fi-icl-dsi", "re-icl-u", "fi-cml-u", "re-cml-u", "fi-cml-u2", "fi-icl-u4", "fi-tgl-u", "fi-cml-h", "fi-cml-s", "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-apl0", "shard-glk0", "shard-kbl0", "shard-skl0", "shard-tglb0", "fi-tgl-y", "re-tgl-y", "shard-tglb9", "re-tgl-cham", "fi-icl-1065g7", "fi-tgl-guc", "re-tgl-u2", "fi-tgl-dsi", "ba-tgl-1", "custom-tgl-joshikun"] OR machine_tag IS IN ["ICL", "TGL", "GEN9"]) AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@gem_ctx_persistence@processes"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["fail"])) AND stderr ~= 'Failed assertion: wait_for_status\(fence, reset_timeout_ms\) == -5'

New failures caught by the filter:

• https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_482/fi-icl-guc/igt@gem_ctx_persistence@processes.html

closed via commit igt-gpu-tools@726e0987

added platform: EHL label

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

Description: GEN9 ICL TGL: igt@gem_ctx_persistence@processes - fail - Failed assertion: wait_for_status(fence, reset_timeout_ms) == -5

Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["shard-kbl3", "fi-glk-1", "shard-glkb1", "shard-glkb3", "shard-apl6", "fi-skl-6770hq", "fi-skl-6260u", "shard-apl2", "shard-kbl5", "fi-bxt-j4205", "shard-kbl4", "shard-glkb6", "shard-glkb2", "shard-kbl7", "fi-skl-6700hq", "fi-skl-6600u", "shard-apl5", "shard-apl7", "fi-bxt-dsi", "shard-glkb4", "shard-apl8", "shard-apl1", "fi-glk-dsi", "fi-kbl-7500u", "shard-kbl6", "shard-apl4", "shard-glkb5", "shard-kbl1", "fi-kbl-7560u", "shard-apl3", "fi-skl-6700k2", "fi-kbl-r", "fi-kbl-7567u", "fi-cfl-s2", "fi-skl-gvtdvm", "shard-kbl2", "fi-skl-guc", "fi-cfl-8700k", "fi-cfl-u", "fi-cfl-s3", "fi-glk-j4005", "shard-apl", "shard-glk", "shard-kbl", "shard-glk1", "shard-glk3", "shard-glk4", "shard-glk5", "shard-glk2", "shard-glkb", "shard-glk8", "shard-glk6", "shard-glk7", "pig-skl-6600", "pig-glk-j4005", "pig-glk-j5005", "fi-cfl-guc", "fi-kbl-guc", "fi-cfl-u2", "pig-skl-6260u", "fi-whl-u", "fi-kbl-x1275", "shard-glk9", "fi-cfl-8109u", "fi-skl-iommu", "fi-kbl-8809g", "fi-icl-u", "fi-skl-caroline", "fi-apl-nasher", "fi-kbl-soraka", "shard-skl", "shard-skl1", "shard-skl2", "shard-skl3", "shard-skl4", "shard-skl5", "shard-skl6", "shard-skl7", "shard-skl8", "shard-skl9", "fi-icl-u2", "shard-skl10", "fi-apl-guc", "shard-iclb", "shard-iclb1", "shard-iclb2", "shard-iclb3", "shard-iclb4", "shard-iclb5", "shard-iclb6", "fi-icl-u3", "shard-iclb7", "fi-icl-y", "fi-skl-lmem", "shard-iclb8", "fi-icl-guc", "fi-icl-dsi", "re-icl-u", "fi-cml-u", "re-cml-u", "fi-cml-u2", "fi-icl-u4", "fi-tgl-u", "fi-cml-h", "fi-cml-s", "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-apl0", "shard-glk0", "shard-kbl0", "shard-skl0", "shard-tglb0", "fi-tgl-y", "re-tgl-y", "shard-tglb9", "re-tgl-cham", "fi-icl-1065g7", "fi-tgl-guc", "fi-ehl-1", "re-ehl-1", "re-tgl-u2", "fi-tgl-dsi", "ba-tgl-1", "re-ehl-cham", "custom-tgl-joshikun", "pig-icl-1065g7", "tgl-u-lpddr-ba", "re-tgl-u3"] OR machine_tag IS IN ["EHL", "ICL", "TGL", "GEN9"]) AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@gem_ctx_persistence@processes"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["fail"])) AND stderr ~= 'Failed assertion: wait_for_status\(fence, reset_timeout_ms\) == -5'

New failures caught by the filter:

• https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_514/fi-ehl-1/igt@gem_ctx_persistence@processes.html

mentioned in issue #2374 (closed)

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.