Result: fail
git-log-oneline run5 boot5 dmesg5 runtimes5
Detail | Value |
---|---|
Time | 0.12 seconds |
Hostname | shard-kbl3 |
Igt-Version | IGT-Version: 1.23-g78619fde (x86_64) (Linux: 4.19.0-g84df9525b0c2-linus-v4.19 x86_64) |
Out | 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: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.122s) |
Err | Starting subtest: pi-ringfull-blt (gem_exec_schedule:1021) CRITICAL: Test assertion failure function test_pi_ringfull, file ../tests/gem_exec_schedule.c:1183: (gem_exec_schedule:1021) CRITICAL: Failed assertion: result[2] (gem_exec_schedule:1021) CRITICAL: Last errno: 4, Interrupted system call (gem_exec_schedule:1021) CRITICAL: High priority child unable to submit within 10ms Subtest pi-ringfull-blt failed. **** DEBUG **** (gem_exec_schedule:1021) drmtest-DEBUG: Test requirement passed: !(fd<0) (gem_exec_schedule:1021) igt_dummyload-DEBUG: Test requirement passed: vgem_has_fences(cork->vgem.device) (gem_exec_schedule:1021) DEBUG: Filled low-priority ring with 181 batches (gem_exec_schedule:1021) DEBUG: LP parent executing (gem_exec_schedule:1021) CRITICAL: Test assertion failure function test_pi_ringfull, file ../tests/gem_exec_schedule.c:1183: (gem_exec_schedule:1021) CRITICAL: Failed assertion: result[2] (gem_exec_schedule:1021) CRITICAL: Last errno: 4, Interrupted system call (gem_exec_schedule:1021) CRITICAL: High priority child unable to submit within 10ms (gem_exec_schedule:1021) igt_core-INFO: Stack trace: (gem_exec_schedule:1021) igt_core-INFO: #0 ../lib/igt_core.c:1467 __igt_fail_assert() (gem_exec_schedule:1021) igt_core-INFO: #1 ../tests/gem_exec_schedule.c:1185 test_pi_ringfull() (gem_exec_schedule:1021) igt_core-INFO: #2 ../tests/gem_exec_schedule.c:1348 __real_main1194() (gem_exec_schedule:1021) igt_core-INFO: #3 ../tests/gem_exec_schedule.c:1194 main() (gem_exec_schedule:1021) igt_core-INFO: #4 ../csu/libc-start.c:344 __libc_start_main() (gem_exec_schedule:1021) igt_core-INFO: #5 [_start+0x2a] **** END **** Subtest pi-ringfull-blt: FAIL (0.122s) |
Dmesg | <6> [73.163618] Console: switching to colour dummy device 80x25 <6> [73.163677] [IGT] gem_exec_schedule: executing <5> [73.168579] Setting dangerous option reset - tainting kernel <5> [73.174860] Setting dangerous option reset - tainting kernel <5> [73.175113] Setting dangerous option reset - tainting kernel <5> [73.180806] Setting dangerous option reset - tainting kernel <5> [73.181057] Setting dangerous option reset - tainting kernel <5> [73.186729] Setting dangerous option reset - tainting kernel <5> [73.186976] Setting dangerous option reset - tainting kernel <5> [73.192607] Setting dangerous option reset - tainting kernel <5> [73.192852] Setting dangerous option reset - tainting kernel <5> [73.198669] Setting dangerous option reset - tainting kernel <5> [73.198916] Setting dangerous option reset - tainting kernel <6> [73.201954] [IGT] gem_exec_schedule: starting subtest pi-ringfull-blt <7> [73.202618] [drm:vgem_gem_dumb_create [vgem]] Created object of size 1 <6> [73.327338] [IGT] gem_exec_schedule: exiting, ret=99 <4> [83.572802] asynchronous wait on fence vgem:unbound:1 timed out <6> [83.642211] Console: switching to colour frame buffer device 240x67 |