[Bug 106509] [CI][IGT][GLK] igt at kms_cursor_legacy@2x-(long)-nonblocking-modeset-vs-cursor-atomic

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Nov 27 20:03:39 UTC 2019


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

--- Comment #3 from ashutosh.dixit at intel.com ---
Still happening intermittently:

https://intel-gfx-ci.01.org/tree/drm-tip/igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic.html

Error seen here:

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7410/shard-glk4/igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic.html

Trace as follows:

IGT-Version: 1.24-g360b11e51 (x86_64) (Linux: 5.4.0-rc8-CI-CI_DRM_7410+ x86_64)
Test requirement not met in function __real_main1364, file
../tests/kms_cursor_legacy.c:1383:
Test requirement: !(n >= display.n_pipes)
Starting subtest: 2x-nonblocking-modeset-vs-cursor-atomic
Stack trace:
  #0 ../lib/igt_core.c:1830 __igt_fail_assert()
  #1 [igt_display_commit_atomic+0x44]
  #2 ../tests/kms_cursor_legacy.c:930 two_screens_flip_vs_cursor()
  #3 ../tests/kms_cursor_legacy.c:1442 __real_main1364()
  #4 ../tests/kms_cursor_legacy.c:1364 main()
  #5 ../csu/libc-start.c:344 __libc_start_main()
  #6 [_start+0x2a]
Subtest 2x-nonblocking-modeset-vs-cursor-atomic: FAIL (0.294s)

Starting subtest: 2x-nonblocking-modeset-vs-cursor-atomic
(kms_cursor_legacy:2161) igt_kms-CRITICAL: Test assertion failure function
igt_display_commit_atomic, file ../lib/igt_kms.c:3543:
(kms_cursor_legacy:2161) igt_kms-CRITICAL: Failed assertion: ret == 0
(kms_cursor_legacy:2161) igt_kms-CRITICAL: Last errno: 16, Device or resource
busy
(kms_cursor_legacy:2161) igt_kms-CRITICAL: error: -16 != 0
Subtest 2x-nonblocking-modeset-vs-cursor-atomic failed.

#assessment

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


More information about the intel-gfx-bugs mailing list