Created attachment 131390 [details] dmesg.log The following test cases are failing on BXT with the following configuration : ================================================== igt@gem_exec_reloc@readonly-29 igt@gem_exec_reloc@readonly-25 igt@gem_exec_reloc@readonly-20 igt@gem_exec_reloc@mmap-31 igt@gem_exec_reloc@mmap-32 igt@gem_exec_reloc@cpu-32 igt@gem_exec_reloc@wc-32 igt@gem_exec_reloc@wc-31 igt@gem_exec_reloc@readonly-28 igt@gem_exec_reloc@readonly-26 igt@gem_exec_reloc@readonly-27 igt@gem_exec_reloc@readonly-24 igt@gem_exec_reloc@readonly-22 igt@gem_exec_reloc@readonly-23 igt@gem_exec_reloc@readonly-21 igt@gem_exec_reloc@readonly-31 igt@gem_exec_reloc@readonly-32 igt@gem_exec_reloc@readonly-16 igt@gem_exec_reloc@readonly-13 igt@gem_exec_reloc@readonly-18 igt@gem_exec_reloc@gtt-32 igt@gem_exec_reloc@readonly-17 igt@gem_exec_reloc@readonly-15 igt@gem_exec_reloc@readonly-14 igt@gem_exec_reloc@readonly-12 igt@gem_exec_reloc@readonly-19 igt@gem_exec_reloc@readonly-30 igt@gem_exec_reloc@gtt-31 igt@gem_exec_reloc@cpu-31 test case output e.g : ====================================== IGT-Version: 1.18-g93215b0 (x86_64) (Linux: 4.12.0-rc1-drm-tip-ww20-commit-713f8ec+ x86_64) (gem_exec_reloc:1328) drmtest-DEBUG: Test requirement passed: !(fd<0) (gem_exec_reloc:1328) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0' (gem_exec_reloc:1328) drmtest-DEBUG: Test requirement passed: drmSetMaster(fd) == 0 (gem_exec_reloc:1328) drmtest-DEBUG: Test requirement passed: is_i915_device(fd) && has_known_intel_chipset(fd) (gem_exec_reloc:1328) ioctl-wrappers-DEBUG: Test requirement passed: err == 0 (gem_exec_reloc:1328) ioctl-wrappers-DEBUG: Test requirement passed: has_ban_period || has_bannable (gem_exec_reloc:1328) igt-gt-DEBUG: Test requirement passed: has_gpu_reset(fd) (gem_exec_reloc:1328) igt-core-DEBUG: Starting subtest: readonly-28 (gem_exec_reloc:1328) intel-os-DEBUG: Checking 2 surfaces of size 268,435,456 bytes (total 536,875,008) against RAM (gem_exec_reloc:1328) drmtest-DEBUG: Test requirement passed: !(fd<0) (gem_exec_reloc:1328) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0' (gem_exec_reloc:1328) intel-os-DEBUG: Test requirement passed: __intel_check_memory(count, size, mode, &required, &total) (gem_exec_reloc:1328) igt-core-DEBUG: Test requirement passed: !igt_run_in_simulation() (gem_exec_reloc:1328) ioctl-wrappers-CRITICAL: Test assertion failure function gem_execbuf, file ioctl_wrappers.c:624: (gem_exec_reloc:1328) ioctl-wrappers-CRITICAL: Failed assertion: __gem_execbuf(fd, execbuf) == 0 (gem_exec_reloc:1328) ioctl-wrappers-CRITICAL: error: -14 != 0 Stack trace: #0 [__igt_fail_assert+0x101] #1 [gem_execbuf+0x44] #2 [from_mmap+0x174] #3 [__real_main654+0xbb8] #4 [main+0x33] #5 [__libc_start_main+0xf1] #6 [_start+0x29] #7 [<unknown>+0x29] Subtest readonly-28 failed. **** DEBUG **** (gem_exec_reloc:1328) intel-os-DEBUG: Checking 2 surfaces of size 268,435,456 bytes (total 536,875,008) against RAM (gem_exec_reloc:1328) drmtest-DEBUG: Test requirement passed: !(fd<0) (gem_exec_reloc:1328) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0' (gem_exec_reloc:1328) intel-os-DEBUG: Test requirement passed: __intel_check_memory(count, size, mode, &required, &total) (gem_exec_reloc:1328) igt-core-DEBUG: Test requirement passed: !igt_run_in_simulation() (gem_exec_reloc:1328) ioctl-wrappers-CRITICAL: Test assertion failure function gem_execbuf, file ioctl_wrappers.c:624: (gem_exec_reloc:1328) ioctl-wrappers-CRITICAL: Failed assertion: __gem_execbuf(fd, execbuf) == 0 (gem_exec_reloc:1328) ioctl-wrappers-CRITICAL: error: -14 != 0 **** END **** Subtest readonly-28: FAIL (0.954s) (gem_exec_reloc:1328) igt-core-DEBUG: Exiting with status code 99 (gem_exec_reloc:1328) igt-debugfs-DEBUG: Opening debugfs directory '/sys/kernel/debug/dri/0' ====================================== Software ====================================== kernel version : 4.12.0-rc1-drm-tip-ww20-commit-713f8ec+ architecture : x86_64 os version : Ubuntu 16.10 os codename : yakkety kernel driver : i915 bios revision : 5.6 bios release date : 03/10/2017 ksc : 16.0 ====================================== Graphic drivers ====================================== Component: drm tag: libdrm-2.4.80-11-ga2fa2e0 commit: a2fa2e08692483cf9f4d06caa6e0f0add59e3343 Component: cairo tag: 1.15.4-21-g9d44136 commit: 9d44136ef8e2a1ad2c6631beb4bbdaeed7a2dad8 Component: intel-gpu-tools tag: intel-gpu-tools-1.18-173-g93215b0 commit: 93215b00db06ba568c34a6cad194f4749bbfbc9d Component: piglit tag: piglit-v1 commit: 7352f4a98a23eae1201bfc4a0121d9c3a969d23f ====================================== Hardware ====================================== motherboard model : NUC6CAYS motherboard id : NUC6CAYB form factor : Desktop manufacturer : Intelcorporation cpu family : Celeron cpu family id : 6 cpu information : Intel(R) Celeron(R) CPU J3455 @ 1.50GHz gpu card : Intel Corporation Device 5a85 (rev 0b) (prog-if 00 [VGA controller]) memory ram : 15.54 GB cpu thread : 4 cpu core : 4 cpu model : 92 cpu stepping : 9 signature : Type 0, Family 6, Model 92, Stepping 9 current cd clock frequency : 384000 kHz maximum cd clock frequency : 624000 kHz displays connected : DP-1 DP-2 ====================================== Firmware ====================================== dmc fw loaded : yes dmc version : 1.7 guc fw loaded : NONE guc version wanted : 0.0 guc version found : 0.0
commit 2889caa9232109afc8881f29a2205abeb5709d0c Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Fri Jun 16 15:05:19 2017 +0100 drm/i915: Eliminate lots of iterations over the execobjects array
Could you please test this again to confirm is fixed. Thank you.
with latest kernel commit this issue is not reproducible on APL commit 21d74e215ad650f0e8e30de609bd65601f0aa11d Author: Daniel Vetter <daniel.vetter@ffwll.ch> AuthorDate: Mon Jun 26 11:12:55 2017 +0200 Commit: Daniel Vetter <daniel.vetter@ffwll.ch> CommitDate: Mon Jun 26 11:12:55 2017 +0200 drm-tip: 2017y-06m-26d-09h-12m-14s UTC integration manifest
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.