Results for igt@gem_exec_schedule@deep-blt

shard-apl7

IGT-Version: 1.24-g828d2e6c0 (x86_64) (Linux: 5.4.0-rc7-CI-CI_DRM_7341+ x86_64)

IGT-Version: 1.24-g828d2e6c0 (x86_64) (Linux: 5.4.0-rc7-CI-CI_DRM_7341+ x86_64)
Using Execlists submission
Has kernel scheduler
 - With priority sorting
 - With preemption enabled
 - With HW semaphores enabled
Test requirement not met in function __real_main1671, file ../tests/i915/gem_exec_schedule.c:1736:
Test requirement: gem_ring_has_physical_engine(fd, eb_ring(e))
Test requirement not met in function __real_main1671, file ../tests/i915/gem_exec_schedule.c:1736:
Test requirement: gem_ring_has_physical_engine(fd, eb_ring(e))
Starting subtest: deep-blt
Using 2046 requests (prio range 2046)
First deptree: 8 requests [10.497s]
Second deptree: 0 requests [10.497s]
Stack trace:
  #0 ../lib/igt_core.c:1716 __igt_fail_assert()
  #1 [vgem_fence_signal+0x44]
  #2 ../lib/igt_dummyload.c:541 igt_cork_unplug()
  #3 ../tests/i915/gem_exec_schedule.c:207 unplug_show_queue()
  #4 ../tests/i915/gem_exec_schedule.c:1271 deep()
  #5 ../tests/i915/gem_exec_schedule.c:1802 __real_main1671()
  #6 ../tests/i915/gem_exec_schedule.c:1671 main()
  #7 ../csu/libc-start.c:344 __libc_start_main()
  #8 [_start+0x2a]
Subtest deep-blt: FAIL (12.907s)
Test requirement not met in function __real_main1671, file ../tests/i915/gem_exec_schedule.c:1829:
Test requirement: gem_ring_has_physical_engine(fd, eb_ring(e))
Test requirement not met in function __real_main1671, file ../tests/i915/gem_exec_schedule.c:1829:
Test requirement: gem_ring_has_physical_engine(fd, eb_ring(e))

Starting subtest: deep-blt
(gem_exec_schedule:4633) igt_vgem-CRITICAL: Test assertion failure function vgem_fence_signal, file ../lib/igt_vgem.c:193:
(gem_exec_schedule:4633) igt_vgem-CRITICAL: Failed assertion: __vgem_fence_signal(fd, fence) == 0
(gem_exec_schedule:4633) igt_vgem-CRITICAL: error: -110 != 0
Subtest deep-blt failed.
**** DEBUG ****
(gem_exec_schedule:4633) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: vgem_has_fences(cork->vgem.device)
(gem_exec_schedule:4633) igt_debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0'
(gem_exec_schedule:4633) INFO: Using 2046 requests (prio range 2046)
(gem_exec_schedule:4633) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: vgem_has_fences(cork->vgem.device)
(gem_exec_schedule:4633) INFO: First deptree: 8 requests [10.497s]
(gem_exec_schedule:4633) INFO: Second deptree: 0 requests [10.497s]
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_schedule:4633) igt_vgem-CRITICAL: Test assertion failure function vgem_fence_signal, file ../lib/igt_vgem.c:193:
(gem_exec_schedule:4633) igt_vgem-CRITICAL: Failed assertion: __vgem_fence_signal(fd, fence) == 0
(gem_exec_schedule:4633) igt_vgem-CRITICAL: error: -110 != 0
(gem_exec_schedule:4633) igt_core-INFO: Stack trace:
(gem_exec_schedule:4633) igt_core-INFO:   #0 ../lib/igt_core.c:1716 __igt_fail_assert()
(gem_exec_schedule:4633) igt_core-INFO:   #1 [vgem_fence_signal+0x44]
(gem_exec_schedule:4633) igt_core-INFO:   #2 ../lib/igt_dummyload.c:541 igt_cork_unplug()
(gem_exec_schedule:4633) igt_core-INFO:   #3 ../tests/i915/gem_exec_schedule.c:207 unplug_show_queue()
(gem_exec_schedule:4633) igt_core-INFO:   #4 ../tests/i915/gem_exec_schedule.c:1271 deep()
(gem_exec_schedule:4633) igt_core-INFO:   #5 ../tests/i915/gem_exec_schedule.c:1802 __real_main1671()
(gem_exec_schedule:4633) igt_core-INFO:   #6 ../tests/i915/gem_exec_schedule.c:1671 main()
(gem_exec_schedule:4633) igt_core-INFO:   #7 ../csu/libc-start.c:344 __libc_start_main()
(gem_exec_schedule:4633) igt_core-INFO:   #8 [_start+0x2a]
****  END  ****
Subtest deep-blt: FAIL (12.907s)

<6> [1278.648586] Console: switching to colour dummy device 80x25
<6> [1278.648774] [IGT] gem_exec_schedule: executing
<5> [1278.658840] Setting dangerous option reset - tainting kernel
<5> [1278.676841] Setting dangerous option reset - tainting kernel
<5> [1278.677585] Setting dangerous option reset - tainting kernel
<5> [1278.696263] Setting dangerous option reset - tainting kernel
<5> [1278.697266] Setting dangerous option reset - tainting kernel
<5> [1278.717647] Setting dangerous option reset - tainting kernel
<5> [1278.718548] Setting dangerous option reset - tainting kernel
<6> [1278.728713] [IGT] gem_exec_schedule: starting subtest deep-blt
<5> [1291.647240] Setting dangerous option reset - tainting kernel
<5> [1291.648340] Setting dangerous option reset - tainting kernel
<6> [1291.914251] [IGT] gem_exec_schedule: exiting, ret=98
<5> [1291.914875] Setting dangerous option reset - tainting kernel
<6> [1292.155397] Console: switching to colour frame buffer device 240x67