[Bug 104284] [IGT] some gem_exec_fence Failed assertion: __gem_execbuf(fd, execbuf) == 0

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=104284

--- Comment #15 from Hector Velazquez <hector.franciscox.velazquez.suriano at intel.com> ---
This test was failing on GLK QA 

Tests List:

igt at gem_exec_fence@parallel-blt
igt at gem_exec_fence@parallel-render
igt at gem_exec_fence@parallel-vebox

IGT-Version: 1.21-g94bd67c (x86_64) (Linux: 4.15.0-drm-tip-ww6-commit-078873d+
x86_64)

======================================
        output sample
======================================
. . .
**** DEBUG ****
(gem_exec_fence:1443) DEBUG: Test requirement passed: has_submit_fence(i915)
(gem_exec_fence:1443) drmtest-DEBUG: Test requirement passed: !(fd<0)
(gem_exec_fence:1443) drmtest-DEBUG: Test requirement passed:
is_i915_device(fd) && has_known_intel_chipset(fd)
(gem_exec_fence:1443) igt-debugfs-DEBUG: Opening debugfs directory
'/sys/kernel/debug/dri/0'
(gem_exec_fence:1443) ioctl-wrappers-DEBUG: Test requirement passed: err == 0
(gem_exec_fence:1443) ioctl-wrappers-DEBUG: Test requirement passed:
gem_has_ring(fd, ring)
(gem_exec_fence:1443) igt-dummyload-DEBUG: Test requirement passed: nengine
(gem_exec_fence:1443) ioctl-wrappers-CRITICAL: Test assertion failure function
gem_execbuf, file ioctl_wrappers.c:605:
(gem_exec_fence:1443) ioctl-wrappers-CRITICAL: Failed assertion:
__gem_execbuf(fd, execbuf) == 0
(gem_exec_fence:1443) ioctl-wrappers-CRITICAL: error: -22 != 0
(gem_exec_fence:1443) igt-core-INFO: Stack trace:
(gem_exec_fence:1443) igt-core-INFO:   #0 [__igt_fail_assert+0x101]
(gem_exec_fence:1443) igt-core-INFO:   #1 [gem_execbuf+0x44]
(gem_exec_fence:1443) igt-core-INFO:   #2 [__real_main1452+0x2791]
(gem_exec_fence:1443) igt-core-INFO:   #3 [main+0x23]
(gem_exec_fence:1443) igt-core-INFO:   #4 [__libc_start_main+0xf0]
(gem_exec_fence:1443) igt-core-INFO:   #5 [_start+0x29]
(gem_exec_fence:1443) igt-core-INFO:   #6 [<unknown>+0x29]
****  END  ****
. . .

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180209/d722f45c/attachment.html>