[Bug 111858] [ICL] IGT tests kms_ccs and kms_frontbuffer_tracking fail on latest drm-tip kernel

[bugzilla-daemon at freedesktop.org]

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

--- Comment #4 from Lakshmi <lakshminarayana.vudum at intel.com> ---
(In reply to HeYue from comment #0)
> Created attachment 145585 [details]
> kms_frontbuffer_tracking
> 
> On Ubuntu 16.04 on ICL-U D0 board, replace kernel to 5.3.0-rc8: git clone
> https://github.com/freedesktop/drm-tip
> Then
> git clone https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> Build igt test tool.
> Then run the igt test on console terminal as root
> ./kms_ccs
> IGT-Version: 1.24-g924e5c5 (x86_64) (Linux: 5.3.0-rc8 x86_64)
> Subtest pipe-A-crc-primary-basic: CRASH (0.004s)
> Starting subtest: pipe-A-crc-primary-rotation-180
> Subtest pipe-A-crc-primary-rotation-180: CRASH (0.004s)
> Starting subtest: pipe-A-crc-sprite-planes-basic
> Starting subtest: pipe-B-crc-primary-basic
> Subtest pipe-B-crc-primary-basic: CRASH (0.001s)
> Starting subtest: pipe-B-crc-primary-rotation-180
> Subtest pipe-B-crc-primary-rotation-180: CRASH (0.001s)
> The 4 tests are crash.
> 
In our CI system on ICL, igt at kms_ccs@* were never failed as crash. 

> Run the ./ kms_frontbuffer_tracking, there are error:
> Stack trace:
>   #0 /home/hdr/igt-gpu-tools/lib/igt_core.c:1696 __igt_fail_assert()
>   #1 /home/hdr/igt-gpu-tools/tests/kms_frontbuffer_tracking.c:1274
> __real_main3273()
>   #2 /home/hdr/igt-gpu-tools/tests/kms_frontbuffer_tracking.c:3273 main()
>   #3 ../csu/libc-start.c:325 __libc_start_main()
>   #4 [_start+0x29]
>   #5 [<unknown>+0x0]
> And all subtest fail.

Regarding kms_frontbuffer_tracking fail, I couldn't see the logs for this
failure, that would be helpful to know if there are any open issues already.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee 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/20190930/1b82d20b/attachment.html>