Bug 111858

Summary:

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

Product:

DRI

Reporter:

HeYue <yue.he>

Component:

DRM/Intel

Assignee:

Intel GFX Bugs mailing list <intel-gfx-bugs>

Status:

CLOSED INVALID

QA Contact:

Intel GFX Bugs mailing list <intel-gfx-bugs>

Severity:

major

Priority:

not set

CC:

intel-gfx-bugs

Version:

unspecified

Hardware:

x86-64 (AMD64)

OS:

Linux (All)

Whiteboard:

Triaged

i915 platform:

ICL

i915 features:

display/Other

Attachments:

Description	Flags
kms_frontbuffer_tracking	none
kms_ccs	none
gem_basic	none

Description HeYue 2019-09-30 01:55:55 UTC

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.

Run the gem_basic, the subtests of gem_basic are all pass.

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.

Comment 1 HeYue 2019-09-30 01:56:39 UTC

Created attachment 145586 [details]
kms_ccs

Comment 2 HeYue 2019-09-30 01:57:03 UTC

Created attachment 145587 [details]
gem_basic

Comment 3 HeYue 2019-09-30 02:00:11 UTC

ICL D0 is Gen 11.

Comment 4 Lakshmi 2019-09-30 08:27:59 UTC

(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@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.

Comment 5 Jani Saarinen 2019-11-04 09:06:32 UTC

Reporter, is this still valid bug? 
I see from CI https://intel-gfx-ci.01.org/tree/drm-tip/index.html?testfilter=kms_ccs&hosts=icl

frontbuffer tracking propably 103167?

Comment 6 HeYue 2019-11-05 01:31:09 UTC

hi, not valid anymore. will close it.
Thanks!

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.