[Bug 104538] [IGT] kms_cursor_legacy --r *2x* execution stops on next test after FAIL

[bugzilla-daemon at freedesktop.org]

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

--- Comment #4 from Hector Velazquez <hector.franciscox.velazquez.suriano at intel.com> ---
This test has failed on GLK QA
same result of the comment 3 

Tests List:

igt at kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic

IGT-Version: 1.21-g37bd27f (x86_64) (Linux:
4.16.0-rc1-drm-intel-qa-ww7-commit-28dc2a5+ x86_64)

======================================
        output sample
======================================
. . .
(kms_cursor_legacy:12480) CRITICAL: Test assertion failure function
two_screens_flip_vs_cursor, file kms_cursor_legacy.c:1013:
(kms_cursor_legacy:12480) CRITICAL: Failed assertion: vblank_matches
(kms_cursor_legacy:12480) CRITICAL: Last errno: 16, Device or resource busy
(kms_cursor_legacy:12480) CRITICAL: During modeset at least 1 page flip needs
to match!
(kms_cursor_legacy:12480) igt-core-INFO: Stack trace:
(kms_cursor_legacy:12480) igt-core-INFO:   #0 [__igt_fail_assert+0x101]
(kms_cursor_legacy:12480) igt-core-INFO:   #1
[two_screens_flip_vs_cursor+0x8ce]
(kms_cursor_legacy:12480) igt-core-INFO:   #2 [__real_main1369+0xbee]
(kms_cursor_legacy:12480) igt-core-INFO:   #3 [main+0x27]
(kms_cursor_legacy:12480) igt-core-INFO:   #4 [__libc_start_main+0xf1]
(kms_cursor_legacy:12480) igt-core-INFO:   #5 [_start+0x2a]
(kms_cursor_legacy:12480) igt-core-INFO:   #6 [<unknown>+0x2a]
****  END  ****
Stack trace:
  #0 [__igt_fail_assert+0x101]
  #1 [two_screens_flip_vs_cursor+0x8ce]
  #2 [__real_main1369+0xbee]
  #3 [main+0x27]
  #4 [__libc_start_main+0xf1]
  #5 [_start+0x2a]
  #6 [<unknown>+0x2a]
Subtest 2x-nonblocking-modeset-vs-cursor-atomic: FAIL (1.328s)
. . .

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