Ci_DRM_3278 APL- and GLK-shards, igt@gem_exec_schedule@wide-render (gem_exec_schedule:3475) igt-vgem-CRITICAL: Test assertion failure function vgem_fence_signal, file igt_vgem.c:193: (gem_exec_schedule:3475) igt-vgem-CRITICAL: Failed assertion: __vgem_fence_signal(fd, fence) == 0 (gem_exec_schedule:3475) igt-vgem-CRITICAL: error: -110 != 0 Subtest wide-render failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3278/shard-apl3/igt@gem_exec_schedule@wide-render.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3278/shard-glkb2/igt@gem_exec_schedule@wide-render.html
All 3 machines show a dramatic slow down for that single test run, unrelated to the kernel changes. That's highly suspicious that something in the build/run environment was changed. kbl: IGT-Version: 1.20-ge5f7fac9 (x86_64) (Linux: 4.14.0-rc6-CI-CI_DRM_3277+ x86_64) Using Execlists submission Has kernel scheduler - With priority sorting - With preemption enabled Submitted 9 requests over 4096 contexts in 5698.4ms -> IGT-Version: 1.20-g3a52d8c2 (x86_64) (Linux: 4.14.0-rc6-CI-CI_DRM_3278+ x86_64) Using Execlists submission Has kernel scheduler - With priority sorting - With preemption enabled Submitted 1 requests over 4096 contexts in 11570.8ms (Run after: Submitted 9 requests over 4096 contexts in 5675.9ms) bxt: IGT-Version: 1.20-ge5f7fac9 (x86_64) (Linux: 4.14.0-rc6-CI-CI_DRM_3277+ x86_64) Using Execlists submission Has kernel scheduler - With priority sorting - With preemption enabled Submitted 2 requests over 4096 contexts in 7771.1ms -> IGT-Version: 1.20-g3a52d8c2 (x86_64) (Linux: 4.14.0-rc6-CI-CI_DRM_3278+ x86_64) Using Execlists submission Has kernel scheduler - With priority sorting - With preemption enabled Submitted 1 requests over 4096 contexts in 11570.8ms (Run after: Submitted 2 requests over 4096 contexts in 7760.5m) glk: IGT-Version: 1.20-ge5f7fac9 (x86_64) (Linux: 4.14.0-rc6-CI-CI_DRM_3277+ x86_64) Using Execlists submission Has kernel scheduler - With priority sorting - With preemption enabled Submitted 4 requests over 4096 contexts in 6377.1ms -> IGT-Version: 1.20-g3a52d8c2 (x86_64) (Linux: 4.14.0-rc6-CI-CI_DRM_3278+ x86_64) Using Execlists submission Has kernel scheduler - With priority sorting - With preemption enabled Submitted 1 requests over 4096 contexts in 13258.6ms (Run after: Submitted 4 requests over 4096 contexts in 6381.2ms)
New sub-test: CI_DRM_3311 shard-glkb1 igt@gem_exec_schedule@wide-bsd (gem_exec_schedule:9837) igt-vgem-CRITICAL: Test assertion failure function vgem_fence_signal, file igt_vgem.c:193: (gem_exec_schedule:9837) igt-vgem-CRITICAL: Failed assertion: __vgem_fence_signal(fd, fence) == 0 (gem_exec_schedule:9837) igt-vgem-CRITICAL: error: -110 != 0 Subtest wide-bsd failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3311/shard-glkb1/igt@gem_exec_schedule@wide-bsd.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3318/shard-kbl4/igt@gem_exec_schedule@reorder-wide-bsd1.html (gem_exec_schedule:2037) igt-vgem-CRITICAL: Test assertion failure function vgem_fence_signal, file igt_vgem.c:193: (gem_exec_schedule:2037) igt-vgem-CRITICAL: Failed assertion: __vgem_fence_signal(fd, fence) == 0 (gem_exec_schedule:2037) igt-vgem-CRITICAL: error: -110 != 0 Subtest reorder-wide-bsd1 failed.
This issue is no longer reproducible, I will close and archive
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.