https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3624/shard-snb6/igt@gem_pwrite_snooped.html (gem_pwrite_snooped:1718) intel-batchbuffer-CRITICAL: Test assertion failure function intel_batchbuffer_flush_on_ring, file intel_batchbuffer.c:184: (gem_pwrite_snooped:1718) intel-batchbuffer-CRITICAL: Failed assertion: (drm_intel_gem_bo_context_exec(batch->bo, ctx, used, ring)) == 0 (gem_pwrite_snooped:1718) intel-batchbuffer-CRITICAL: Last errno: 5, Input/output error Test gem_pwrite_snooped failed.
It is possible that this issue: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3624/shard-snb6/igt@drv_hangman@error-state-capture-blt.html see bug 104058. that was run before igt@gem_pwrite_snooped is related.
Just a follow-on result of the driver wedging itself earlier.
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4160/shard-glkb2/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-indfb-draw-render.html (kms_frontbuffer_tracking:2022) intel_batchbuffer-CRITICAL: Test assertion failure function intel_batchbuffer_flush_on_ring, file ../lib/intel_batchbuffer.c:184: (kms_frontbuffer_tracking:2022) intel_batchbuffer-CRITICAL: Failed assertion: (drm_intel_gem_bo_context_exec(batch->bo, ctx, used, ring)) == 0 (kms_frontbuffer_tracking:2022) intel_batchbuffer-CRITICAL: Last errno: 5, Input/output error Test kms_frontbuffer_tracking failed.
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4160/shard-glkb2/igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing.html (gem_persistent_relocs:1794) intel_batchbuffer-CRITICAL: Test assertion failure function intel_batchbuffer_flush_on_ring, file ../lib/intel_batchbuffer.c:184: (gem_persistent_relocs:1794) intel_batchbuffer-CRITICAL: Failed assertion: (drm_intel_gem_bo_context_exec(batch->bo, ctx, used, ring)) == 0 (gem_persistent_relocs:1794) intel_batchbuffer-CRITICAL: Last errno: 5, Input/output error Subtest forked-interruptible-faulting-reloc-thrashing failed.
Last seen IGT_4160: 2018-01-20 / 266 runs ago
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.