Results for igt@gem_exec_schedule@pi-ringfull-blt

shard-glk2

IGT-Version: 1.23-g78619fde (x86_64) (Linux: 4.19.0-g84df9525b0c2-linus-v4.19 x86_64)

Using Execlists submission
Has kernel scheduler
 - With priority sorting
 - With preemption enabled
Test requirement not met in function __real_main1194, file ../tests/gem_exec_schedule.c:1248:
Test requirement: gem_ring_has_physical_engine(fd, e->exec_id | e->flags)
Test requirement not met in function __real_main1194, file ../tests/gem_exec_schedule.c:1248:
Test requirement: gem_ring_has_physical_engine(fd, e->exec_id | e->flags)
Test requirement not met in function __real_main1194, file ../tests/gem_exec_schedule.c:1344:
Test requirement: gem_ring_has_physical_engine(fd, e->exec_id | e->flags)
Test requirement not met in function __real_main1194, file ../tests/gem_exec_schedule.c:1344:
Test requirement: gem_ring_has_physical_engine(fd, e->exec_id | e->flags)
Starting subtest: pi-ringfull-blt
Stack trace:
  #0 ../lib/igt_core.c:1467 __igt_fail_assert()
  #1 ../tests/gem_exec_schedule.c:1185 test_pi_ringfull()
  #2 ../tests/gem_exec_schedule.c:1348 __real_main1194()
  #3 ../tests/gem_exec_schedule.c:1194 main()
  #4 ../csu/libc-start.c:344 __libc_start_main()
  #5 [_start+0x2a]
Subtest pi-ringfull-blt: FAIL (0.180s)

Starting subtest: pi-ringfull-blt
(gem_exec_schedule:987) CRITICAL: Test assertion failure function test_pi_ringfull, file ../tests/gem_exec_schedule.c:1183:
(gem_exec_schedule:987) CRITICAL: Failed assertion: result[2]
(gem_exec_schedule:987) CRITICAL: Last errno: 4, Interrupted system call
(gem_exec_schedule:987) CRITICAL: High priority child unable to submit within 10ms
Subtest pi-ringfull-blt failed.
**** DEBUG ****
(gem_exec_schedule:987) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_exec_schedule:987) igt_dummyload-DEBUG: Test requirement passed: vgem_has_fences(cork->vgem.device)
(gem_exec_schedule:987) DEBUG: Filled low-priority ring with 181 batches
(gem_exec_schedule:987) DEBUG: LP parent executing
(gem_exec_schedule:987) CRITICAL: Test assertion failure function test_pi_ringfull, file ../tests/gem_exec_schedule.c:1183:
(gem_exec_schedule:987) CRITICAL: Failed assertion: result[2]
(gem_exec_schedule:987) CRITICAL: Last errno: 4, Interrupted system call
(gem_exec_schedule:987) CRITICAL: High priority child unable to submit within 10ms
(gem_exec_schedule:987) igt_core-INFO: Stack trace:
(gem_exec_schedule:987) igt_core-INFO:   #0 ../lib/igt_core.c:1467 __igt_fail_assert()
(gem_exec_schedule:987) igt_core-INFO:   #1 ../tests/gem_exec_schedule.c:1185 test_pi_ringfull()
(gem_exec_schedule:987) igt_core-INFO:   #2 ../tests/gem_exec_schedule.c:1348 __real_main1194()
(gem_exec_schedule:987) igt_core-INFO:   #3 ../tests/gem_exec_schedule.c:1194 main()
(gem_exec_schedule:987) igt_core-INFO:   #4 ../csu/libc-start.c:344 __libc_start_main()
(gem_exec_schedule:987) igt_core-INFO:   #5 [_start+0x2a]
****  END  ****
Subtest pi-ringfull-blt: FAIL (0.180s)

<6> [148.590652] Console: switching to colour dummy device 80x25
<6> [148.590755] [IGT] gem_exec_schedule: executing
<5> [148.597566] Setting dangerous option reset - tainting kernel
<5> [148.608501] Setting dangerous option reset - tainting kernel
<5> [148.609135] Setting dangerous option reset - tainting kernel
<5> [148.620953] Setting dangerous option reset - tainting kernel
<5> [148.621692] Setting dangerous option reset - tainting kernel
<5> [148.633788] Setting dangerous option reset - tainting kernel
<5> [148.634331] Setting dangerous option reset - tainting kernel
<5> [148.644763] Setting dangerous option reset - tainting kernel
<5> [148.645475] Setting dangerous option reset - tainting kernel
<6> [148.652111] [IGT] gem_exec_schedule: starting subtest pi-ringfull-blt
<7> [148.654882] [drm:vgem_gem_dumb_create [vgem]] Created object of size 1
<6> [148.838808] [IGT] gem_exec_schedule: exiting, ret=99
<4> [159.138448] asynchronous wait on fence vgem:unbound:1 timed out
<6> [159.189574] Console: switching to colour frame buffer device 240x67