* [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix bpc-switch tests on AMD hardware
@ 2021-02-19 17:27 Jeremy Cline
2021-02-19 18:27 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
` (6 more replies)
0 siblings, 7 replies; 22+ messages in thread
From: Jeremy Cline @ 2021-02-19 17:27 UTC (permalink / raw)
To: igt-dev
Kernel commit b836a274b797 ("drm/amdgpu/dc: Require primary plane to be
enabled whenever the CRTC is") causes the bpc-switch tests to fail,
since the primary plane fb is being removed, which leads to the next
atomic commit failing with -EINVAL.
This stops the removal of the primary plane fb before switching to 10
bits per component and the test now runs successfully.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
---
tests/kms_hdr.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/tests/kms_hdr.c b/tests/kms_hdr.c
index e9dd7f27..70a4b456 100644
--- a/tests/kms_hdr.c
+++ b/tests/kms_hdr.c
@@ -223,8 +223,6 @@ static void test_bpc_switch_on_output(data_t *data, igt_output_t *output,
data->h = afb.height;
}
- igt_plane_set_fb(data->primary, NULL);
-
/*
* i915 driver doesn't expose max bpc as debugfs entry,
* so limiting assert only for amd driver.
--
2.30.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply related [flat|nested] 22+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_hdr: Fix bpc-switch tests on AMD hardware
2021-02-19 17:27 [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
@ 2021-02-19 18:27 ` Patchwork
2021-02-19 19:35 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
` (5 subsequent siblings)
6 siblings, 0 replies; 22+ messages in thread
From: Patchwork @ 2021-02-19 18:27 UTC (permalink / raw)
To: Jeremy Cline; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 3052 bytes --]
== Series Details ==
Series: tests/kms_hdr: Fix bpc-switch tests on AMD hardware
URL : https://patchwork.freedesktop.org/series/87232/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9790 -> IGTPW_5540
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/index.html
Known issues
------------
Here are the changes found in IGTPW_5540 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@fbdev@read:
- fi-tgl-y: [PASS][1] -> [DMESG-WARN][2] ([i915#402]) +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/fi-tgl-y/igt@fbdev@read.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/fi-tgl-y/igt@fbdev@read.html
* igt@kms_chamelium@dp-crc-fast:
- fi-cml-u2: [PASS][3] -> [FAIL][4] ([i915#1372])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/fi-cml-u2/igt@kms_chamelium@dp-crc-fast.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/fi-cml-u2/igt@kms_chamelium@dp-crc-fast.html
#### Possible fixes ####
* igt@i915_selftest@live@blt:
- fi-snb-2600: [DMESG-FAIL][5] -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/fi-snb-2600/igt@i915_selftest@live@blt.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/fi-snb-2600/igt@i915_selftest@live@blt.html
* igt@prime_self_import@basic-with_one_bo_two_files:
- fi-tgl-y: [DMESG-WARN][7] ([i915#402]) -> [PASS][8] +2 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/fi-tgl-y/igt@prime_self_import@basic-with_one_bo_two_files.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/fi-tgl-y/igt@prime_self_import@basic-with_one_bo_two_files.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1208]: https://gitlab.freedesktop.org/drm/intel/issues/1208
[i915#1372]: https://gitlab.freedesktop.org/drm/intel/issues/1372
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
Participating hosts (46 -> 41)
------------------------------
Additional (1): fi-cml-drallion
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-dg1-1 fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_6009 -> IGTPW_5540
CI-20190529: 20190529
CI_DRM_9790: 69dc278989ce4d39a40a29cc678bcf0072e016e0 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5540: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/index.html
IGT_6009: a4dccf189b34a55338feec9927dac57c467c4100 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/index.html
[-- Attachment #1.2: Type: text/html, Size: 3621 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_hdr: Fix bpc-switch tests on AMD hardware
2021-02-19 17:27 [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
2021-02-19 18:27 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
@ 2021-02-19 19:35 ` Patchwork
2021-02-19 22:00 ` Jeremy Cline
2021-03-05 16:42 ` [igt-dev] [PATCH i-g-t v2 0/2] Fix up the HDR tests for AMD devices Jeremy Cline
` (4 subsequent siblings)
6 siblings, 1 reply; 22+ messages in thread
From: Patchwork @ 2021-02-19 19:35 UTC (permalink / raw)
To: Jeremy Cline; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 30269 bytes --]
== Series Details ==
Series: tests/kms_hdr: Fix bpc-switch tests on AMD hardware
URL : https://patchwork.freedesktop.org/series/87232/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9790_full -> IGTPW_5540_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_5540_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_5540_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_5540_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_hdr@bpc-switch:
- shard-hsw: NOTRUN -> [FAIL][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-hsw2/igt@kms_hdr@bpc-switch.html
* igt@kms_hdr@bpc-switch-dpms:
- shard-hsw: [PASS][2] -> [FAIL][3] +1 similar issue
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-hsw1/igt@kms_hdr@bpc-switch-dpms.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-hsw4/igt@kms_hdr@bpc-switch-dpms.html
#### Warnings ####
* igt@runner@aborted:
- shard-kbl: ([FAIL][4], [FAIL][5], [FAIL][6], [FAIL][7], [FAIL][8]) ([fdo#109271] / [i915#1814]) -> ([FAIL][9], [FAIL][10], [FAIL][11], [FAIL][12], [FAIL][13]) ([i915#1814] / [i915#2505] / [i915#3002] / [i915#602])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-kbl4/igt@runner@aborted.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-kbl1/igt@runner@aborted.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-kbl7/igt@runner@aborted.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-kbl7/igt@runner@aborted.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-kbl7/igt@runner@aborted.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl7/igt@runner@aborted.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl4/igt@runner@aborted.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl7/igt@runner@aborted.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl6/igt@runner@aborted.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl7/igt@runner@aborted.html
- shard-apl: ([FAIL][14], [FAIL][15], [FAIL][16]) ([i915#1814] / [i915#3002]) -> ([FAIL][17], [FAIL][18], [FAIL][19], [FAIL][20]) ([i915#3002])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-apl7/igt@runner@aborted.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-apl1/igt@runner@aborted.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-apl8/igt@runner@aborted.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl1/igt@runner@aborted.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl2/igt@runner@aborted.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl7/igt@runner@aborted.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl8/igt@runner@aborted.html
Known issues
------------
Here are the changes found in IGTPW_5540_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_create@create-massive:
- shard-kbl: NOTRUN -> [DMESG-WARN][21] ([i915#3002])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl6/igt@gem_create@create-massive.html
* igt@gem_ctx_persistence@engines-mixed-process:
- shard-snb: NOTRUN -> [SKIP][22] ([fdo#109271] / [i915#1099]) +2 similar issues
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-snb5/igt@gem_ctx_persistence@engines-mixed-process.html
* igt@gem_ctx_persistence@hostile:
- shard-hsw: NOTRUN -> [SKIP][23] ([fdo#109271] / [i915#1099]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-hsw7/igt@gem_ctx_persistence@hostile.html
* igt@gem_exec_fair@basic-deadline:
- shard-glk: NOTRUN -> [FAIL][24] ([i915#2846])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-glk4/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-kbl: NOTRUN -> [FAIL][25] ([i915#2842])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl7/igt@gem_exec_fair@basic-none-solo@rcs0.html
* igt@gem_exec_fair@basic-none@vcs0:
- shard-apl: [PASS][26] -> [FAIL][27] ([i915#2842])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-apl3/igt@gem_exec_fair@basic-none@vcs0.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl6/igt@gem_exec_fair@basic-none@vcs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [PASS][28] -> [FAIL][29] ([i915#2842])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-tglb3/igt@gem_exec_fair@basic-pace-share@rcs0.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb8/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_fair@basic-pace@bcs0:
- shard-tglb: NOTRUN -> [FAIL][30] ([i915#2842]) +2 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb2/igt@gem_exec_fair@basic-pace@bcs0.html
* igt@gem_exec_fair@basic-pace@vcs0:
- shard-iclb: NOTRUN -> [FAIL][31] ([i915#2842]) +3 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb3/igt@gem_exec_fair@basic-pace@vcs0.html
- shard-kbl: [PASS][32] -> [SKIP][33] ([fdo#109271])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-kbl4/igt@gem_exec_fair@basic-pace@vcs0.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl1/igt@gem_exec_fair@basic-pace@vcs0.html
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-glk: [PASS][34] -> [FAIL][35] ([i915#2842]) +2 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-glk9/igt@gem_exec_fair@basic-pace@vecs0.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-glk7/igt@gem_exec_fair@basic-pace@vecs0.html
* igt@gem_huc_copy@huc-copy:
- shard-apl: NOTRUN -> [SKIP][36] ([fdo#109271] / [i915#2190])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl8/igt@gem_huc_copy@huc-copy.html
* igt@gem_pread@exhaustion:
- shard-apl: NOTRUN -> [WARN][37] ([i915#2658])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl2/igt@gem_pread@exhaustion.html
- shard-kbl: NOTRUN -> [WARN][38] ([i915#2658])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl6/igt@gem_pread@exhaustion.html
* igt@gem_render_copy@linear-to-vebox-y-tiled:
- shard-iclb: NOTRUN -> [SKIP][39] ([i915#768])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb4/igt@gem_render_copy@linear-to-vebox-y-tiled.html
* igt@gem_userptr_blits@input-checking:
- shard-tglb: NOTRUN -> [DMESG-WARN][40] ([i915#3002])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb8/igt@gem_userptr_blits@input-checking.html
- shard-apl: NOTRUN -> [DMESG-WARN][41] ([i915#3002])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl7/igt@gem_userptr_blits@input-checking.html
- shard-glk: NOTRUN -> [DMESG-WARN][42] ([i915#3002])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-glk5/igt@gem_userptr_blits@input-checking.html
- shard-iclb: NOTRUN -> [DMESG-WARN][43] ([i915#3002])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb6/igt@gem_userptr_blits@input-checking.html
- shard-snb: NOTRUN -> [DMESG-WARN][44] ([i915#3002])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-snb5/igt@gem_userptr_blits@input-checking.html
* igt@gem_userptr_blits@process-exit-mmap-busy@wc:
- shard-apl: NOTRUN -> [SKIP][45] ([fdo#109271] / [i915#1699]) +3 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl1/igt@gem_userptr_blits@process-exit-mmap-busy@wc.html
* igt@gem_userptr_blits@process-exit-mmap@wc:
- shard-hsw: NOTRUN -> [SKIP][46] ([fdo#109271]) +80 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-hsw7/igt@gem_userptr_blits@process-exit-mmap@wc.html
* igt@gem_userptr_blits@vma-merge:
- shard-snb: NOTRUN -> [FAIL][47] ([i915#2724])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-snb2/igt@gem_userptr_blits@vma-merge.html
* igt@gen7_exec_parse@basic-rejected:
- shard-tglb: NOTRUN -> [SKIP][48] ([fdo#109289])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb8/igt@gen7_exec_parse@basic-rejected.html
- shard-iclb: NOTRUN -> [SKIP][49] ([fdo#109289])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb6/igt@gen7_exec_parse@basic-rejected.html
* igt@gen9_exec_parse@bb-secure:
- shard-tglb: NOTRUN -> [SKIP][50] ([fdo#112306])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb5/igt@gen9_exec_parse@bb-secure.html
- shard-iclb: NOTRUN -> [SKIP][51] ([fdo#112306])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb8/igt@gen9_exec_parse@bb-secure.html
* igt@i915_pm_backlight@fade_with_suspend:
- shard-hsw: NOTRUN -> [SKIP][52] ([fdo#109271] / [i915#3012])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-hsw4/igt@i915_pm_backlight@fade_with_suspend.html
* igt@i915_pm_rpm@modeset-non-lpsp-stress:
- shard-tglb: NOTRUN -> [SKIP][53] ([fdo#111644] / [i915#1397] / [i915#2411])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb5/igt@i915_pm_rpm@modeset-non-lpsp-stress.html
- shard-iclb: NOTRUN -> [SKIP][54] ([fdo#110892])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb1/igt@i915_pm_rpm@modeset-non-lpsp-stress.html
* igt@i915_query@query-topology-unsupported:
- shard-iclb: NOTRUN -> [SKIP][55] ([fdo#109302])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb5/igt@i915_query@query-topology-unsupported.html
- shard-tglb: NOTRUN -> [SKIP][56] ([fdo#109302])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb7/igt@i915_query@query-topology-unsupported.html
* igt@kms_async_flips@test-time-stamp:
- shard-tglb: [PASS][57] -> [FAIL][58] ([i915#2574])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-tglb1/igt@kms_async_flips@test-time-stamp.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb6/igt@kms_async_flips@test-time-stamp.html
* igt@kms_big_fb@x-tiled-32bpp-rotate-90:
- shard-tglb: NOTRUN -> [SKIP][59] ([fdo#111614]) +1 similar issue
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb5/igt@kms_big_fb@x-tiled-32bpp-rotate-90.html
* igt@kms_big_fb@y-tiled-64bpp-rotate-90:
- shard-iclb: NOTRUN -> [SKIP][60] ([fdo#110725] / [fdo#111614]) +1 similar issue
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb3/igt@kms_big_fb@y-tiled-64bpp-rotate-90.html
* igt@kms_big_fb@yf-tiled-32bpp-rotate-270:
- shard-tglb: NOTRUN -> [SKIP][61] ([fdo#111615])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb6/igt@kms_big_fb@yf-tiled-32bpp-rotate-270.html
* igt@kms_big_joiner@basic:
- shard-kbl: NOTRUN -> [SKIP][62] ([fdo#109271] / [i915#2705])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl7/igt@kms_big_joiner@basic.html
- shard-apl: NOTRUN -> [SKIP][63] ([fdo#109271] / [i915#2705])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl1/igt@kms_big_joiner@basic.html
* igt@kms_chamelium@common-hpd-after-suspend:
- shard-hsw: NOTRUN -> [SKIP][64] ([fdo#109271] / [fdo#111827]) +6 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-hsw7/igt@kms_chamelium@common-hpd-after-suspend.html
- shard-glk: NOTRUN -> [SKIP][65] ([fdo#109271] / [fdo#111827]) +4 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-glk9/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_chamelium@hdmi-edid-change-during-suspend:
- shard-apl: NOTRUN -> [SKIP][66] ([fdo#109271] / [fdo#111827]) +23 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl8/igt@kms_chamelium@hdmi-edid-change-during-suspend.html
* igt@kms_chamelium@hdmi-hpd-enable-disable-mode:
- shard-iclb: NOTRUN -> [SKIP][67] ([fdo#109284] / [fdo#111827]) +5 similar issues
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb4/igt@kms_chamelium@hdmi-hpd-enable-disable-mode.html
* igt@kms_chamelium@hdmi-hpd-storm:
- shard-kbl: NOTRUN -> [SKIP][68] ([fdo#109271] / [fdo#111827]) +19 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl1/igt@kms_chamelium@hdmi-hpd-storm.html
* igt@kms_color@pipe-c-ctm-0-25:
- shard-iclb: NOTRUN -> [FAIL][69] ([i915#1149] / [i915#315])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb7/igt@kms_color@pipe-c-ctm-0-25.html
- shard-tglb: NOTRUN -> [FAIL][70] ([i915#1149] / [i915#315])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb3/igt@kms_color@pipe-c-ctm-0-25.html
* igt@kms_color@pipe-d-ctm-green-to-red:
- shard-iclb: NOTRUN -> [SKIP][71] ([fdo#109278] / [i915#1149])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb7/igt@kms_color@pipe-d-ctm-green-to-red.html
* igt@kms_color_chamelium@pipe-b-ctm-0-5:
- shard-tglb: NOTRUN -> [SKIP][72] ([fdo#109284] / [fdo#111827]) +5 similar issues
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb5/igt@kms_color_chamelium@pipe-b-ctm-0-5.html
* igt@kms_color_chamelium@pipe-invalid-ctm-matrix-sizes:
- shard-snb: NOTRUN -> [SKIP][73] ([fdo#109271] / [fdo#111827]) +18 similar issues
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-snb2/igt@kms_color_chamelium@pipe-invalid-ctm-matrix-sizes.html
* igt@kms_content_protection@atomic:
- shard-kbl: NOTRUN -> [TIMEOUT][74] ([i915#1319])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl2/igt@kms_content_protection@atomic.html
* igt@kms_cursor_crc@pipe-a-cursor-512x512-rapid-movement:
- shard-iclb: NOTRUN -> [SKIP][75] ([fdo#109278] / [fdo#109279])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb4/igt@kms_cursor_crc@pipe-a-cursor-512x512-rapid-movement.html
- shard-tglb: NOTRUN -> [SKIP][76] ([fdo#109279])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb6/igt@kms_cursor_crc@pipe-a-cursor-512x512-rapid-movement.html
* igt@kms_cursor_edge_walk@pipe-d-128x128-right-edge:
- shard-snb: NOTRUN -> [SKIP][77] ([fdo#109271]) +293 similar issues
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-snb5/igt@kms_cursor_edge_walk@pipe-d-128x128-right-edge.html
* igt@kms_cursor_legacy@flip-vs-cursor-toggle:
- shard-tglb: NOTRUN -> [FAIL][78] ([i915#2346])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb6/igt@kms_cursor_legacy@flip-vs-cursor-toggle.html
* igt@kms_flip@2x-plain-flip-fb-recreate-interruptible:
- shard-iclb: NOTRUN -> [SKIP][79] ([fdo#109274]) +2 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb1/igt@kms_flip@2x-plain-flip-fb-recreate-interruptible.html
* igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
- shard-kbl: NOTRUN -> [DMESG-WARN][80] ([i915#180]) +2 similar issues
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl7/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html
* igt@kms_flip@flip-vs-suspend-interruptible@c-dp1:
- shard-apl: NOTRUN -> [DMESG-WARN][81] ([i915#180]) +1 similar issue
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl1/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html
* igt@kms_flip@flip-vs-suspend@a-dp1:
- shard-apl: [PASS][82] -> [DMESG-WARN][83] ([i915#180])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-apl7/igt@kms_flip@flip-vs-suspend@a-dp1.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl8/igt@kms_flip@flip-vs-suspend@a-dp1.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile:
- shard-kbl: NOTRUN -> [FAIL][84] ([i915#2641])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl1/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-blt:
- shard-glk: NOTRUN -> [FAIL][85] ([i915#49])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-glk6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-shrfb-msflip-blt:
- shard-glk: [PASS][86] -> [FAIL][87] ([i915#49])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-glk1/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-shrfb-msflip-blt.html
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-glk1/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-shrfb-msflip-blt.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-move:
- shard-iclb: NOTRUN -> [SKIP][88] ([fdo#109280]) +9 similar issues
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb3/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-move.html
* igt@kms_frontbuffer_tracking@fbcpsr-suspend:
- shard-glk: NOTRUN -> [SKIP][89] ([fdo#109271]) +23 similar issues
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-glk1/igt@kms_frontbuffer_tracking@fbcpsr-suspend.html
* igt@kms_frontbuffer_tracking@psr-2p-primscrn-spr-indfb-draw-mmap-gtt:
- shard-tglb: NOTRUN -> [SKIP][90] ([fdo#111825]) +12 similar issues
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb7/igt@kms_frontbuffer_tracking@psr-2p-primscrn-spr-indfb-draw-mmap-gtt.html
* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-wc:
- shard-kbl: NOTRUN -> [SKIP][91] ([fdo#109271]) +210 similar issues
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl2/igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-wc.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- shard-apl: NOTRUN -> [SKIP][92] ([fdo#109271] / [i915#533])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl8/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-7efc:
- shard-kbl: NOTRUN -> [FAIL][93] ([fdo#108145] / [i915#265]) +1 similar issue
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl1/igt@kms_plane_alpha_blend@pipe-a-alpha-7efc.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb:
- shard-apl: NOTRUN -> [FAIL][94] ([i915#265])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl2/igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb.html
- shard-kbl: NOTRUN -> [FAIL][95] ([i915#265])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl6/igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb.html
* igt@kms_plane_alpha_blend@pipe-b-constant-alpha-max:
- shard-apl: NOTRUN -> [FAIL][96] ([fdo#108145] / [i915#265]) +3 similar issues
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl1/igt@kms_plane_alpha_blend@pipe-b-constant-alpha-max.html
* igt@kms_plane_cursor@pipe-d-overlay-size-256:
- shard-hsw: NOTRUN -> [SKIP][97] ([fdo#109271] / [i915#533]) +12 similar issues
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-hsw7/igt@kms_plane_cursor@pipe-d-overlay-size-256.html
* igt@kms_plane_lowres@pipe-d-tiling-none:
- shard-iclb: NOTRUN -> [SKIP][98] ([fdo#109278]) +3 similar issues
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb4/igt@kms_plane_lowres@pipe-d-tiling-none.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4:
- shard-apl: NOTRUN -> [SKIP][99] ([fdo#109271] / [i915#658]) +3 similar issues
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl1/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5:
- shard-kbl: NOTRUN -> [SKIP][100] ([fdo#109271] / [i915#658]) +5 similar issues
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl4/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5.html
* igt@kms_psr@cursor_render:
- shard-hsw: NOTRUN -> [SKIP][101] ([fdo#109271] / [i915#1072]) +4 similar issues
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-hsw4/igt@kms_psr@cursor_render.html
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: NOTRUN -> [SKIP][102] ([fdo#109441]) +1 similar issue
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb8/igt@kms_psr@psr2_cursor_plane_move.html
* igt@kms_psr@psr2_cursor_render:
- shard-iclb: [PASS][103] -> [SKIP][104] ([fdo#109441]) +1 similar issue
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-iclb2/igt@kms_psr@psr2_cursor_render.html
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb3/igt@kms_psr@psr2_cursor_render.html
* igt@kms_vblank@pipe-b-ts-continuation-suspend:
- shard-kbl: [PASS][105] -> [DMESG-WARN][106] ([i915#180])
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-kbl6/igt@kms_vblank@pipe-b-ts-continuation-suspend.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl7/igt@kms_vblank@pipe-b-ts-continuation-suspend.html
* igt@kms_writeback@writeback-check-output:
- shard-apl: NOTRUN -> [SKIP][107] ([fdo#109271] / [i915#2437]) +2 similar issues
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl1/igt@kms_writeback@writeback-check-output.html
* igt@kms_writeback@writeback-pixel-formats:
- shard-glk: NOTRUN -> [SKIP][108] ([fdo#109271] / [i915#2437])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-glk3/igt@kms_writeback@writeback-pixel-formats.html
- shard-kbl: NOTRUN -> [SKIP][109] ([fdo#109271] / [i915#2437]) +1 similar issue
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl4/igt@kms_writeback@writeback-pixel-formats.html
- shard-iclb: NOTRUN -> [SKIP][110] ([i915#2437])
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb2/igt@kms_writeback@writeback-pixel-formats.html
- shard-tglb: NOTRUN -> [SKIP][111] ([i915#2437])
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb1/igt@kms_writeback@writeback-pixel-formats.html
* igt@nouveau_crc@pipe-b-ctx-flip-skip-current-frame:
- shard-apl: NOTRUN -> [SKIP][112] ([fdo#109271]) +196 similar issues
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl3/igt@nouveau_crc@pipe-b-ctx-flip-skip-current-frame.html
* igt@prime_nv_api@i915_nv_import_twice_check_flink_name:
- shard-iclb: NOTRUN -> [SKIP][113] ([fdo#109291]) +1 similar issue
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb5/igt@prime_nv_api@i915_nv_import_twice_check_flink_name.html
- shard-tglb: NOTRUN -> [SKIP][114] ([fdo#109291]) +1 similar issue
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb7/igt@prime_nv_api@i915_nv_import_twice_check_flink_name.html
* igt@sysfs_clients@recycle:
- shard-apl: [PASS][115] -> [FAIL][116] ([i915#3028])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-apl7/igt@sysfs_clients@recycle.html
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl7/igt@sysfs_clients@recycle.html
* igt@sysfs_clients@recycle-many:
- shard-apl: NOTRUN -> [FAIL][117] ([i915#3028])
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl7/igt@sysfs_clients@recycle-many.html
- shard-kbl: [PASS][118] -> [FAIL][119] ([i915#3028])
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-kbl4/igt@sysfs_clients@recycle-many.html
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl1/igt@sysfs_clients@recycle-many.html
- shard-snb: [PASS][120] -> [FAIL][121] ([i915#3028])
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-snb6/igt@sysfs_clients@recycle-many.html
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-snb7/igt@sysfs_clients@recycle-many.html
* igt@sysfs_clients@sema-10@vcs0:
- shard-apl: NOTRUN -> [SKIP][122] ([fdo#109271] / [i915#3026]) +3 similar issues
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl2/igt@sysfs_clients@sema-10@vcs0.html
- shard-kbl: NOTRUN -> [SKIP][123] ([fdo#109271] / [i915#3026]) +3 similar issues
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl4/igt@sysfs_clients@sema-10@vcs0.html
#### Possible fixes ####
* igt@gem_exec_balancer@hang:
- shard-iclb: [INCOMPLETE][124] ([i915#1895] / [i915#3031]) -> [PASS][125]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-iclb2/igt@gem_exec_balancer@hang.html
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb5/igt@gem_exec_balancer@hang.html
* igt@gem_exec_fair@basic-none@rcs0:
- shard-glk: [FAIL][126] ([i915#2842]) -> [PASS][127]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-glk7/igt@gem_exec_fair@basic-none@rcs0.html
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-glk5/igt@gem_exec_fair@basic-none@rcs0.html
* igt@gem_exec_fair@basic-none@vecs0:
- shard-apl: [FAIL][128] ([i915#2842]) -> [PASS][129]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-apl3/igt@gem_exec_fair@basic-none@vecs0.html
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-apl6/igt@gem_exec_fair@basic-none@vecs0.html
* igt@gem_exec_fair@basic-pace@vcs1:
- shard-kbl: [SKIP][130] ([fdo#109271]) -> [PASS][131]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-kbl4/igt@gem_exec_fair@basic-pace@vcs1.html
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl1/igt@gem_exec_fair@basic-pace@vcs1.html
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-kbl: [FAIL][132] ([i915#2842]) -> [PASS][133]
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-kbl4/igt@gem_exec_fair@basic-pace@vecs0.html
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl1/igt@gem_exec_fair@basic-pace@vecs0.html
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [FAIL][134] ([i915#2849]) -> [PASS][135]
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-iclb8/igt@gem_exec_fair@basic-throttle@rcs0.html
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-iclb5/igt@gem_exec_fair@basic-throttle@rcs0.html
* igt@i915_pm_rc6_residency@rc6-fence:
- shard-hsw: [WARN][136] ([i915#1519]) -> [PASS][137]
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-hsw4/igt@i915_pm_rc6_residency@rc6-fence.html
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-hsw4/igt@i915_pm_rc6_residency@rc6-fence.html
* igt@i915_selftest@live@hangcheck:
- shard-hsw: [INCOMPLETE][138] ([i915#2782]) -> [PASS][139]
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-hsw4/igt@i915_selftest@live@hangcheck.html
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-hsw7/igt@i915_selftest@live@hangcheck.html
* igt@kms_cursor_legacy@cursora-vs-flipa-legacy:
- shard-snb: [SKIP][140] ([fdo#109271]) -> [PASS][141]
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-snb6/igt@kms_cursor_legacy@cursora-vs-flipa-legacy.html
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-snb2/igt@kms_cursor_legacy@cursora-vs-flipa-legacy.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1:
- shard-tglb: [FAIL][142] ([i915#2598]) -> [PASS][143]
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-tglb5/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1.html
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb6/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1.html
* igt@kms_hdmi_inject@inject-audio:
- shard-tglb: [SKIP][144] ([i915#433]) -> [PASS][145]
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-tglb7/igt@kms_hdmi_inject@inject-audio.html
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-tglb1/igt@kms_hdmi_inject@inject-audio.html
* igt@kms_hdr@bpc-switch-suspend:
- shard-kbl: [DMESG-WARN][146] ([i915#180]) -> [PASS][147]
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-kbl7/igt@kms_hdr@bpc-switch-suspend.html
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-kbl6/igt@kms_hdr@bpc-switch-suspend.html
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/index.html
[-- Attachment #1.2: Type: text/html, Size: 34297 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_hdr: Fix bpc-switch tests on AMD hardware
2021-02-19 19:35 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
@ 2021-02-19 22:00 ` Jeremy Cline
0 siblings, 0 replies; 22+ messages in thread
From: Jeremy Cline @ 2021-02-19 22:00 UTC (permalink / raw)
To: igt-dev
Hi,
On Fri, Feb 19, 2021 at 07:35:53PM -0000, Patchwork wrote:
> == Series Details ==
>
> Series: tests/kms_hdr: Fix bpc-switch tests on AMD hardware
> URL : https://patchwork.freedesktop.org/series/87232/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_9790_full -> IGTPW_5540_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with IGTPW_5540_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in IGTPW_5540_full, please notify your bug team to allow them
> to document this new failure mode, which will reduce false positives in CI.
>
> External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/index.html
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in IGTPW_5540_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_hdr@bpc-switch:
> - shard-hsw: NOTRUN -> [FAIL][1]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-hsw2/igt@kms_hdr@bpc-switch.html
>
> * igt@kms_hdr@bpc-switch-dpms:
> - shard-hsw: [PASS][2] -> [FAIL][3] +1 similar issue
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9790/shard-hsw1/igt@kms_hdr@bpc-switch-dpms.html
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5540/shard-hsw4/igt@kms_hdr@bpc-switch-dpms.html
>
Is it valuable to run the HDR tests on this hardware? As far as I can
tell the tests are failing because the plane scaling is invalid, but
from my interpretation of the test matrix it's fine on newer hardware
which support HDR.
I'm not sure whether to add something to just skip the tests for
older[0] hardware entirely, or to fiddle with the test so this hardware
is happy again.
[0] https://www.intel.com/content/dam/support/us/en/documents/graphics/HDR_Intel_Graphics_TechWhitePaper.pdf
Thanks,
Jeremy
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* [igt-dev] [PATCH i-g-t v2 0/2] Fix up the HDR tests for AMD devices
2021-02-19 17:27 [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
2021-02-19 18:27 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-02-19 19:35 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
@ 2021-03-05 16:42 ` Jeremy Cline
2021-03-05 16:42 ` [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices Jeremy Cline
2021-03-05 16:42 ` [igt-dev] [PATCH i-g-t v2 2/2] kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
2021-03-05 17:17 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev2) Patchwork
` (3 subsequent siblings)
6 siblings, 2 replies; 22+ messages in thread
From: Jeremy Cline @ 2021-03-05 16:42 UTC (permalink / raw)
To: igt-dev
A second attempt at getting the HDR tests working again on AMD devices.
AMD hardware requires a primary plane to be enabled whenever the CRTC
is, but the bpc_switch tests are explicitly removing the primary plane
because old Intel hardware (hsw) has scaling restrictions.
However, Intel only supports HDR in Kaby Lake+ so rather than working
around the scaling restriction this just skips the HDR tests on hardware
that doesn't support HDR.
Jeremy Cline (2):
kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices
kms_hdr: Fix bpc-switch tests on AMD hardware
tests/kms_hdr.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
--
2.30.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices
2021-03-05 16:42 ` [igt-dev] [PATCH i-g-t v2 0/2] Fix up the HDR tests for AMD devices Jeremy Cline
@ 2021-03-05 16:42 ` Jeremy Cline
2021-03-08 8:47 ` Petri Latvala
2021-03-05 16:42 ` [igt-dev] [PATCH i-g-t v2 2/2] kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
1 sibling, 1 reply; 22+ messages in thread
From: Jeremy Cline @ 2021-03-05 16:42 UTC (permalink / raw)
To: igt-dev
According to the Intel documentation[0] I could find, HDR support is
only in Kaby Lake+. Skip tests in kms_hdr if the hardware doesn't
support HDR.
[0] https://www.intel.com/content/dam/support/us/en/documents/graphics/HDR_Intel_Graphics_TechWhitePaper.pdf
Signed-off-by: Jeremy Cline <jcline@redhat.com>
---
tests/kms_hdr.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/tests/kms_hdr.c b/tests/kms_hdr.c
index e9dd7f27..7617e8a5 100644
--- a/tests/kms_hdr.c
+++ b/tests/kms_hdr.c
@@ -644,6 +644,12 @@ igt_main
igt_require(data.display.is_atomic);
igt_display_require_output(&data.display);
+
+ /* According to Intel documentation, hardware prior to Kaby Lake does
+ * not support HDR.
+ */
+ if (is_i915_device(data.fd))
+ igt_require(AT_LEAST_GEN(intel_get_drm_devid(data.fd), 9));
}
igt_describe("Tests switching between different display output bpc modes");
--
2.30.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply related [flat|nested] 22+ messages in thread
* [igt-dev] [PATCH i-g-t v2 2/2] kms_hdr: Fix bpc-switch tests on AMD hardware
2021-03-05 16:42 ` [igt-dev] [PATCH i-g-t v2 0/2] Fix up the HDR tests for AMD devices Jeremy Cline
2021-03-05 16:42 ` [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices Jeremy Cline
@ 2021-03-05 16:42 ` Jeremy Cline
2021-03-05 16:48 ` Kazlauskas, Nicholas
1 sibling, 1 reply; 22+ messages in thread
From: Jeremy Cline @ 2021-03-05 16:42 UTC (permalink / raw)
To: igt-dev
Kernel commit b836a274b797 ("drm/amdgpu/dc: Require primary plane to be
enabled whenever the CRTC is") causes the bpc-switch tests to fail,
since the primary plane fb is being removed, which leads to the next
atomic commit failing with -EINVAL.
This stops the removal of the primary plane fb before switching to 10
bits per component and the test now runs successfully.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
---
tests/kms_hdr.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/tests/kms_hdr.c b/tests/kms_hdr.c
index 7617e8a5..8aa3ea78 100644
--- a/tests/kms_hdr.c
+++ b/tests/kms_hdr.c
@@ -223,8 +223,6 @@ static void test_bpc_switch_on_output(data_t *data, igt_output_t *output,
data->h = afb.height;
}
- igt_plane_set_fb(data->primary, NULL);
-
/*
* i915 driver doesn't expose max bpc as debugfs entry,
* so limiting assert only for amd driver.
--
2.30.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply related [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2 2/2] kms_hdr: Fix bpc-switch tests on AMD hardware
2021-03-05 16:42 ` [igt-dev] [PATCH i-g-t v2 2/2] kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
@ 2021-03-05 16:48 ` Kazlauskas, Nicholas
0 siblings, 0 replies; 22+ messages in thread
From: Kazlauskas, Nicholas @ 2021-03-05 16:48 UTC (permalink / raw)
To: Jeremy Cline, igt-dev
On 2021-03-05 11:42 a.m., Jeremy Cline wrote:
> Kernel commit b836a274b797 ("drm/amdgpu/dc: Require primary plane to be
> enabled whenever the CRTC is") causes the bpc-switch tests to fail,
> since the primary plane fb is being removed, which leads to the next
> atomic commit failing with -EINVAL.
>
> This stops the removal of the primary plane fb before switching to 10
> bits per component and the test now runs successfully.
>
> Signed-off-by: Jeremy Cline <jcline@redhat.com>
Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
You'll want to ping someone from Intel or the IGT maintainers for patch
1 in the series, however.
Regards,
Nicholas Kazlauskas
> ---
> tests/kms_hdr.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/tests/kms_hdr.c b/tests/kms_hdr.c
> index 7617e8a5..8aa3ea78 100644
> --- a/tests/kms_hdr.c
> +++ b/tests/kms_hdr.c
> @@ -223,8 +223,6 @@ static void test_bpc_switch_on_output(data_t *data, igt_output_t *output,
> data->h = afb.height;
> }
>
> - igt_plane_set_fb(data->primary, NULL);
> -
> /*
> * i915 driver doesn't expose max bpc as debugfs entry,
> * so limiting assert only for amd driver.
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev2)
2021-02-19 17:27 [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
` (2 preceding siblings ...)
2021-03-05 16:42 ` [igt-dev] [PATCH i-g-t v2 0/2] Fix up the HDR tests for AMD devices Jeremy Cline
@ 2021-03-05 17:17 ` Patchwork
2021-03-05 21:42 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
` (2 subsequent siblings)
6 siblings, 0 replies; 22+ messages in thread
From: Patchwork @ 2021-03-05 17:17 UTC (permalink / raw)
To: Jeremy Cline; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 5779 bytes --]
== Series Details ==
Series: tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev2)
URL : https://patchwork.freedesktop.org/series/87232/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9836 -> IGTPW_5579
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_5579:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@kms_frontbuffer_tracking@basic:
- {fi-rkl-11500t}: [PASS][1] -> [SKIP][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/fi-rkl-11500t/igt@kms_frontbuffer_tracking@basic.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/fi-rkl-11500t/igt@kms_frontbuffer_tracking@basic.html
Known issues
------------
Here are the changes found in IGTPW_5579 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_fence@basic-busy@bcs0:
- fi-kbl-soraka: NOTRUN -> [SKIP][3] ([fdo#109271]) +23 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/fi-kbl-soraka/igt@gem_exec_fence@basic-busy@bcs0.html
* igt@gem_exec_gttfill@basic:
- fi-kbl-8809g: [PASS][4] -> [TIMEOUT][5] ([i915#3145])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/fi-kbl-8809g/igt@gem_exec_gttfill@basic.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/fi-kbl-8809g/igt@gem_exec_gttfill@basic.html
* igt@gem_huc_copy@huc-copy:
- fi-kbl-soraka: NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#2190])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/fi-kbl-soraka/igt@gem_huc_copy@huc-copy.html
* igt@i915_selftest@live@blt:
- fi-snb-2600: [PASS][7] -> [DMESG-FAIL][8] ([i915#1409])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/fi-snb-2600/igt@i915_selftest@live@blt.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/fi-snb-2600/igt@i915_selftest@live@blt.html
* igt@i915_selftest@live@gt_pm:
- fi-kbl-soraka: NOTRUN -> [DMESG-FAIL][9] ([i915#1886] / [i915#2291])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/fi-kbl-soraka/igt@i915_selftest@live@gt_pm.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-kbl-soraka: NOTRUN -> [SKIP][10] ([fdo#109271] / [fdo#111827]) +8 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/fi-kbl-soraka/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_frontbuffer_tracking@basic:
- fi-kbl-soraka: NOTRUN -> [FAIL][11] ([i915#49])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/fi-kbl-soraka/igt@kms_frontbuffer_tracking@basic.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-kbl-soraka: NOTRUN -> [SKIP][12] ([fdo#109271] / [i915#533])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/fi-kbl-soraka/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
#### Possible fixes ####
* igt@gem_linear_blits@basic:
- fi-kbl-8809g: [TIMEOUT][13] ([i915#2502]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/fi-kbl-8809g/igt@gem_linear_blits@basic.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/fi-kbl-8809g/igt@gem_linear_blits@basic.html
* igt@gem_wait@busy@all:
- fi-bsw-nick: [FAIL][15] ([i915#1676]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/fi-bsw-nick/igt@gem_wait@busy@all.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/fi-bsw-nick/igt@gem_wait@busy@all.html
#### Warnings ####
* igt@gem_tiled_blits@basic:
- fi-kbl-8809g: [TIMEOUT][17] ([i915#3145]) -> [TIMEOUT][18] ([i915#2502] / [i915#3145])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/fi-kbl-8809g/igt@gem_tiled_blits@basic.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/fi-kbl-8809g/igt@gem_tiled_blits@basic.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1409]: https://gitlab.freedesktop.org/drm/intel/issues/1409
[i915#1676]: https://gitlab.freedesktop.org/drm/intel/issues/1676
[i915#1886]: https://gitlab.freedesktop.org/drm/intel/issues/1886
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2291]: https://gitlab.freedesktop.org/drm/intel/issues/2291
[i915#2502]: https://gitlab.freedesktop.org/drm/intel/issues/2502
[i915#3145]: https://gitlab.freedesktop.org/drm/intel/issues/3145
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
Participating hosts (43 -> 39)
------------------------------
Additional (1): fi-kbl-soraka
Missing (5): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-dg1-1 fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_6024 -> IGTPW_5579
CI-20190529: 20190529
CI_DRM_9836: 8449e42c5aab6666ce79a2c9f5e75ddd31b9b50e @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_5579: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/index.html
IGT_6024: d8e03fe437f0c328c96717a92ad97719c02ba2cd @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/index.html
[-- Attachment #1.2: Type: text/html, Size: 7076 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* [igt-dev] ✗ Fi.CI.IGT: failure for tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev2)
2021-02-19 17:27 [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
` (3 preceding siblings ...)
2021-03-05 17:17 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev2) Patchwork
@ 2021-03-05 21:42 ` Patchwork
2021-03-10 16:34 ` [igt-dev] [PATCH i-g-t v3] tests/kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
2021-03-10 16:45 ` [igt-dev] ✗ Fi.CI.BUILD: failure for tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev3) Patchwork
6 siblings, 0 replies; 22+ messages in thread
From: Patchwork @ 2021-03-05 21:42 UTC (permalink / raw)
To: Jeremy Cline; +Cc: igt-dev
[-- Attachment #1.1: Type: text/plain, Size: 30276 bytes --]
== Series Details ==
Series: tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev2)
URL : https://patchwork.freedesktop.org/series/87232/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9836_full -> IGTPW_5579_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_5579_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_5579_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_5579_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_mmap_gtt@cpuset-big-copy-xy:
- shard-iclb: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-iclb7/igt@gem_mmap_gtt@cpuset-big-copy-xy.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb2/igt@gem_mmap_gtt@cpuset-big-copy-xy.html
Known issues
------------
Here are the changes found in IGTPW_5579_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@feature_discovery@display-4x:
- shard-tglb: NOTRUN -> [SKIP][3] ([i915#1839])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb2/igt@feature_discovery@display-4x.html
- shard-iclb: NOTRUN -> [SKIP][4] ([i915#1839])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb5/igt@feature_discovery@display-4x.html
* igt@gem_create@create-clear:
- shard-glk: [PASS][5] -> [FAIL][6] ([i915#1888] / [i915#3160])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-glk8/igt@gem_create@create-clear.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk1/igt@gem_create@create-clear.html
* igt@gem_create@create-massive:
- shard-snb: NOTRUN -> [DMESG-WARN][7] ([i915#3002]) +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-snb5/igt@gem_create@create-massive.html
* igt@gem_ctx_param@set-priority-not-supported:
- shard-tglb: NOTRUN -> [SKIP][8] ([fdo#109314])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb6/igt@gem_ctx_param@set-priority-not-supported.html
- shard-iclb: NOTRUN -> [SKIP][9] ([fdo#109314])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb6/igt@gem_ctx_param@set-priority-not-supported.html
* igt@gem_ctx_persistence@clone:
- shard-snb: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#1099]) +5 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-snb5/igt@gem_ctx_persistence@clone.html
* igt@gem_ctx_persistence@hostile:
- shard-hsw: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#1099])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-hsw2/igt@gem_ctx_persistence@hostile.html
* igt@gem_ctx_shared@q-in-order:
- shard-snb: NOTRUN -> [SKIP][12] ([fdo#109271]) +359 similar issues
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-snb2/igt@gem_ctx_shared@q-in-order.html
* igt@gem_eio@unwedge-stress:
- shard-iclb: [PASS][13] -> [TIMEOUT][14] ([i915#2369] / [i915#2481] / [i915#3070])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-iclb8/igt@gem_eio@unwedge-stress.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb3/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_capture@capture@rcs0:
- shard-kbl: [PASS][15] -> [FAIL][16] ([i915#3062])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-kbl3/igt@gem_exec_capture@capture@rcs0.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl6/igt@gem_exec_capture@capture@rcs0.html
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-kbl: [PASS][17] -> [FAIL][18] ([i915#2842])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-kbl4/igt@gem_exec_fair@basic-none-solo@rcs0.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl4/igt@gem_exec_fair@basic-none-solo@rcs0.html
* igt@gem_exec_fair@basic-none@vcs0:
- shard-tglb: NOTRUN -> [FAIL][19] ([i915#2842]) +4 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb3/igt@gem_exec_fair@basic-none@vcs0.html
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-iclb: NOTRUN -> [FAIL][20] ([i915#2842]) +6 similar issues
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb6/igt@gem_exec_fair@basic-pace-solo@rcs0.html
- shard-glk: NOTRUN -> [FAIL][21] ([i915#2842]) +1 similar issue
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk9/igt@gem_exec_fair@basic-pace-solo@rcs0.html
* igt@gem_exec_fair@basic-pace@bcs0:
- shard-tglb: [PASS][22] -> [FAIL][23] ([i915#2842]) +1 similar issue
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-tglb2/igt@gem_exec_fair@basic-pace@bcs0.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb5/igt@gem_exec_fair@basic-pace@bcs0.html
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-glk: [PASS][24] -> [FAIL][25] ([i915#2842]) +1 similar issue
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-glk7/igt@gem_exec_fair@basic-throttle@rcs0.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk9/igt@gem_exec_fair@basic-throttle@rcs0.html
* igt@gem_exec_flush@basic-batch-kernel-default-cmd:
- shard-iclb: NOTRUN -> [SKIP][26] ([fdo#109313])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb8/igt@gem_exec_flush@basic-batch-kernel-default-cmd.html
- shard-tglb: NOTRUN -> [SKIP][27] ([fdo#109313])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb5/igt@gem_exec_flush@basic-batch-kernel-default-cmd.html
* igt@gem_exec_params@no-blt:
- shard-tglb: NOTRUN -> [SKIP][28] ([fdo#109283])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb6/igt@gem_exec_params@no-blt.html
- shard-iclb: NOTRUN -> [SKIP][29] ([fdo#109283])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb3/igt@gem_exec_params@no-blt.html
* igt@gem_exec_reloc@basic-many-active@rcs0:
- shard-glk: [PASS][30] -> [FAIL][31] ([i915#2389])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-glk2/igt@gem_exec_reloc@basic-many-active@rcs0.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk4/igt@gem_exec_reloc@basic-many-active@rcs0.html
* igt@gem_exec_reloc@basic-wide-active@bcs0:
- shard-apl: NOTRUN -> [FAIL][32] ([i915#2389]) +3 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl8/igt@gem_exec_reloc@basic-wide-active@bcs0.html
* igt@gem_exec_reloc@basic-wide-active@rcs0:
- shard-snb: NOTRUN -> [FAIL][33] ([i915#2389]) +5 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-snb6/igt@gem_exec_reloc@basic-wide-active@rcs0.html
* igt@gem_exec_schedule@u-fairslice@rcs0:
- shard-apl: [PASS][34] -> [DMESG-WARN][35] ([i915#1610])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-apl3/igt@gem_exec_schedule@u-fairslice@rcs0.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl6/igt@gem_exec_schedule@u-fairslice@rcs0.html
* igt@gem_exec_whisper@basic-queues:
- shard-glk: [PASS][36] -> [DMESG-WARN][37] ([i915#118] / [i915#95])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-glk6/igt@gem_exec_whisper@basic-queues.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk3/igt@gem_exec_whisper@basic-queues.html
* igt@gem_huc_copy@huc-copy:
- shard-kbl: NOTRUN -> [SKIP][38] ([fdo#109271] / [i915#2190])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl3/igt@gem_huc_copy@huc-copy.html
* igt@gem_mmap_gtt@big-copy-odd:
- shard-glk: [PASS][39] -> [FAIL][40] ([i915#307])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-glk3/igt@gem_mmap_gtt@big-copy-odd.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk3/igt@gem_mmap_gtt@big-copy-odd.html
* igt@gem_pread@exhaustion:
- shard-snb: NOTRUN -> [WARN][41] ([i915#2658])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-snb2/igt@gem_pread@exhaustion.html
* igt@gem_pwrite@basic-exhaustion:
- shard-apl: NOTRUN -> [WARN][42] ([i915#2658])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl8/igt@gem_pwrite@basic-exhaustion.html
* igt@gem_userptr_blits@process-exit-mmap-busy@wc:
- shard-apl: NOTRUN -> [SKIP][43] ([fdo#109271] / [i915#1699]) +3 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl8/igt@gem_userptr_blits@process-exit-mmap-busy@wc.html
* igt@gem_userptr_blits@vma-merge:
- shard-snb: NOTRUN -> [FAIL][44] ([i915#2724])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-snb2/igt@gem_userptr_blits@vma-merge.html
* igt@gen7_exec_parse@cmd-crossing-page:
- shard-tglb: NOTRUN -> [SKIP][45] ([fdo#109289]) +1 similar issue
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb7/igt@gen7_exec_parse@cmd-crossing-page.html
* igt@gen9_exec_parse@bb-start-cmd:
- shard-tglb: NOTRUN -> [SKIP][46] ([fdo#112306])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb5/igt@gen9_exec_parse@bb-start-cmd.html
- shard-iclb: NOTRUN -> [SKIP][47] ([fdo#112306])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb8/igt@gen9_exec_parse@bb-start-cmd.html
* igt@i915_pm_backlight@fade_with_suspend:
- shard-hsw: NOTRUN -> [SKIP][48] ([fdo#109271] / [i915#3012])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-hsw2/igt@i915_pm_backlight@fade_with_suspend.html
* igt@i915_pm_rpm@dpms-non-lpsp:
- shard-tglb: NOTRUN -> [SKIP][49] ([fdo#111644] / [i915#1397] / [i915#2411])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb3/igt@i915_pm_rpm@dpms-non-lpsp.html
- shard-iclb: NOTRUN -> [SKIP][50] ([fdo#110892])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb1/igt@i915_pm_rpm@dpms-non-lpsp.html
* igt@i915_pm_rpm@modeset-pc8-residency-stress:
- shard-iclb: NOTRUN -> [SKIP][51] ([fdo#109293] / [fdo#109506])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb6/igt@i915_pm_rpm@modeset-pc8-residency-stress.html
* igt@i915_pm_rpm@system-suspend-modeset:
- shard-kbl: [PASS][52] -> [INCOMPLETE][53] ([i915#151] / [i915#155])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-kbl3/igt@i915_pm_rpm@system-suspend-modeset.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl3/igt@i915_pm_rpm@system-suspend-modeset.html
* igt@i915_selftest@live@hangcheck:
- shard-hsw: [PASS][54] -> [INCOMPLETE][55] ([i915#2782])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-hsw4/igt@i915_selftest@live@hangcheck.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-hsw2/igt@i915_selftest@live@hangcheck.html
* igt@i915_suspend@forcewake:
- shard-kbl: NOTRUN -> [DMESG-WARN][56] ([i915#180]) +1 similar issue
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl4/igt@i915_suspend@forcewake.html
* igt@kms_big_fb@yf-tiled-64bpp-rotate-270:
- shard-tglb: NOTRUN -> [SKIP][57] ([fdo#111615]) +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb6/igt@kms_big_fb@yf-tiled-64bpp-rotate-270.html
* igt@kms_big_fb@yf-tiled-8bpp-rotate-0:
- shard-iclb: NOTRUN -> [SKIP][58] ([fdo#110723]) +1 similar issue
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb5/igt@kms_big_fb@yf-tiled-8bpp-rotate-0.html
* igt@kms_chamelium@dp-crc-single:
- shard-iclb: NOTRUN -> [SKIP][59] ([fdo#109284] / [fdo#111827]) +3 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb5/igt@kms_chamelium@dp-crc-single.html
* igt@kms_chamelium@hdmi-hpd-storm:
- shard-kbl: NOTRUN -> [SKIP][60] ([fdo#109271] / [fdo#111827]) +11 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl7/igt@kms_chamelium@hdmi-hpd-storm.html
* igt@kms_color@pipe-a-ctm-0-75:
- shard-iclb: NOTRUN -> [FAIL][61] ([i915#1149] / [i915#315])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb4/igt@kms_color@pipe-a-ctm-0-75.html
* igt@kms_color@pipe-a-degamma:
- shard-tglb: NOTRUN -> [FAIL][62] ([i915#1149])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb8/igt@kms_color@pipe-a-degamma.html
- shard-iclb: NOTRUN -> [FAIL][63] ([i915#1149])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb2/igt@kms_color@pipe-a-degamma.html
* igt@kms_color_chamelium@pipe-a-ctm-0-25:
- shard-snb: NOTRUN -> [SKIP][64] ([fdo#109271] / [fdo#111827]) +22 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-snb6/igt@kms_color_chamelium@pipe-a-ctm-0-25.html
* igt@kms_color_chamelium@pipe-a-ctm-limited-range:
- shard-apl: NOTRUN -> [SKIP][65] ([fdo#109271] / [fdo#111827]) +19 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl6/igt@kms_color_chamelium@pipe-a-ctm-limited-range.html
* igt@kms_color_chamelium@pipe-d-ctm-green-to-red:
- shard-tglb: NOTRUN -> [SKIP][66] ([fdo#109284] / [fdo#111827]) +2 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb8/igt@kms_color_chamelium@pipe-d-ctm-green-to-red.html
- shard-hsw: NOTRUN -> [SKIP][67] ([fdo#109271] / [fdo#111827]) +1 similar issue
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-hsw2/igt@kms_color_chamelium@pipe-d-ctm-green-to-red.html
- shard-glk: NOTRUN -> [SKIP][68] ([fdo#109271] / [fdo#111827]) +1 similar issue
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk4/igt@kms_color_chamelium@pipe-d-ctm-green-to-red.html
- shard-iclb: NOTRUN -> [SKIP][69] ([fdo#109278] / [fdo#109284] / [fdo#111827])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb4/igt@kms_color_chamelium@pipe-d-ctm-green-to-red.html
* igt@kms_cursor_crc@pipe-b-cursor-512x170-offscreen:
- shard-iclb: NOTRUN -> [SKIP][70] ([fdo#109278] / [fdo#109279]) +1 similar issue
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb3/igt@kms_cursor_crc@pipe-b-cursor-512x170-offscreen.html
* igt@kms_cursor_crc@pipe-c-cursor-512x512-rapid-movement:
- shard-tglb: NOTRUN -> [SKIP][71] ([fdo#109279])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb6/igt@kms_cursor_crc@pipe-c-cursor-512x512-rapid-movement.html
* igt@kms_cursor_crc@pipe-d-cursor-256x256-random:
- shard-glk: NOTRUN -> [SKIP][72] ([fdo#109271]) +30 similar issues
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk6/igt@kms_cursor_crc@pipe-d-cursor-256x256-random.html
- shard-hsw: NOTRUN -> [SKIP][73] ([fdo#109271] / [i915#533]) +4 similar issues
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-hsw4/igt@kms_cursor_crc@pipe-d-cursor-256x256-random.html
* igt@kms_cursor_crc@pipe-d-cursor-64x21-sliding:
- shard-iclb: NOTRUN -> [SKIP][74] ([fdo#109278]) +8 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb2/igt@kms_cursor_crc@pipe-d-cursor-64x21-sliding.html
* igt@kms_cursor_legacy@cursora-vs-flipb-atomic-transitions-varying-size:
- shard-iclb: NOTRUN -> [SKIP][75] ([fdo#109274] / [fdo#109278]) +1 similar issue
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb2/igt@kms_cursor_legacy@cursora-vs-flipb-atomic-transitions-varying-size.html
* igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic:
- shard-kbl: NOTRUN -> [DMESG-FAIL][76] ([IGT#6])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl7/igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic.html
- shard-apl: NOTRUN -> [DMESG-FAIL][77] ([IGT#6])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl8/igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic.html
* igt@kms_cursor_legacy@flip-vs-cursor-varying-size:
- shard-tglb: NOTRUN -> [FAIL][78] ([i915#2346])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb7/igt@kms_cursor_legacy@flip-vs-cursor-varying-size.html
* igt@kms_cursor_legacy@pipe-d-torture-bo:
- shard-kbl: NOTRUN -> [SKIP][79] ([fdo#109271] / [i915#533]) +1 similar issue
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl7/igt@kms_cursor_legacy@pipe-d-torture-bo.html
- shard-apl: NOTRUN -> [SKIP][80] ([fdo#109271] / [i915#533]) +1 similar issue
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl8/igt@kms_cursor_legacy@pipe-d-torture-bo.html
* igt@kms_flip@2x-blocking-absolute-wf_vblank:
- shard-tglb: NOTRUN -> [SKIP][81] ([fdo#111825]) +11 similar issues
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb2/igt@kms_flip@2x-blocking-absolute-wf_vblank.html
* igt@kms_flip@2x-wf_vblank-ts-check:
- shard-iclb: NOTRUN -> [SKIP][82] ([fdo#109274]) +2 similar issues
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb5/igt@kms_flip@2x-wf_vblank-ts-check.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs:
- shard-kbl: NOTRUN -> [FAIL][83] ([i915#2641])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl3/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs.html
- shard-tglb: NOTRUN -> [SKIP][84] ([i915#2587])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb7/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs.html
- shard-glk: NOTRUN -> [FAIL][85] ([i915#2628])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk6/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile:
- shard-apl: NOTRUN -> [FAIL][86] ([i915#2641]) +1 similar issue
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl6/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-gtt:
- shard-hsw: NOTRUN -> [SKIP][87] ([fdo#109271]) +52 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-hsw4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-mmap-gtt.html
* igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-shrfb-draw-mmap-wc:
- shard-iclb: NOTRUN -> [SKIP][88] ([fdo#109280]) +12 similar issues
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb4/igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-shrfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-wc:
- shard-kbl: NOTRUN -> [SKIP][89] ([fdo#109271]) +101 similar issues
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl7/igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-wc.html
* igt@kms_hdr@bpc-switch-dpms:
- shard-hsw: [PASS][90] -> [SKIP][91] ([fdo#109271]) +2 similar issues
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-hsw2/igt@kms_hdr@bpc-switch-dpms.html
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-hsw2/igt@kms_hdr@bpc-switch-dpms.html
* igt@kms_pipe_crc_basic@disable-crc-after-crtc-pipe-d:
- shard-glk: NOTRUN -> [SKIP][92] ([fdo#109271] / [i915#533])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk4/igt@kms_pipe_crc_basic@disable-crc-after-crtc-pipe-d.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes:
- shard-kbl: [PASS][93] -> [DMESG-WARN][94] ([i915#180])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-kbl3/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl4/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
- shard-apl: NOTRUN -> [FAIL][95] ([fdo#108145] / [i915#265]) +1 similar issue
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl1/igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-7efc:
- shard-kbl: NOTRUN -> [FAIL][96] ([fdo#108145] / [i915#265]) +1 similar issue
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl7/igt@kms_plane_alpha_blend@pipe-c-alpha-7efc.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb:
- shard-glk: NOTRUN -> [FAIL][97] ([i915#265])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk1/igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb.html
- shard-kbl: NOTRUN -> [FAIL][98] ([i915#265])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl4/igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb.html
* igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping:
- shard-apl: NOTRUN -> [SKIP][99] ([fdo#109271] / [i915#2733])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl8/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping.html
- shard-kbl: NOTRUN -> [SKIP][100] ([fdo#109271] / [i915#2733])
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl6/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping.html
- shard-glk: NOTRUN -> [SKIP][101] ([fdo#109271] / [i915#2733])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk2/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping.html
* igt@kms_psr2_sf@cursor-plane-update-sf:
- shard-iclb: NOTRUN -> [SKIP][102] ([i915#658]) +2 similar issues
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb8/igt@kms_psr2_sf@cursor-plane-update-sf.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2:
- shard-apl: NOTRUN -> [SKIP][103] ([fdo#109271] / [i915#658]) +9 similar issues
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl1/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-5:
- shard-glk: NOTRUN -> [SKIP][104] ([fdo#109271] / [i915#658]) +1 similar issue
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk3/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-5.html
- shard-kbl: NOTRUN -> [SKIP][105] ([fdo#109271] / [i915#658]) +3 similar issues
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl1/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-5.html
* igt@kms_psr@psr2_dpms:
- shard-iclb: [PASS][106] -> [SKIP][107] ([fdo#109441])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-iclb2/igt@kms_psr@psr2_dpms.html
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb4/igt@kms_psr@psr2_dpms.html
* igt@kms_setmode@basic:
- shard-snb: NOTRUN -> [FAIL][108] ([i915#31])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-snb5/igt@kms_setmode@basic.html
* igt@kms_sysfs_edid_timing:
- shard-apl: NOTRUN -> [FAIL][109] ([IGT#2])
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl6/igt@kms_sysfs_edid_timing.html
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-kbl: [PASS][110] -> [DMESG-WARN][111] ([i915#180] / [i915#295])
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-kbl6/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl4/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
* igt@kms_writeback@writeback-check-output:
- shard-apl: NOTRUN -> [SKIP][112] ([fdo#109271] / [i915#2437])
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl1/igt@kms_writeback@writeback-check-output.html
* igt@nouveau_crc@pipe-a-source-rg:
- shard-iclb: NOTRUN -> [SKIP][113] ([i915#2530]) +1 similar issue
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb3/igt@nouveau_crc@pipe-a-source-rg.html
- shard-tglb: NOTRUN -> [SKIP][114] ([i915#2530])
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb6/igt@nouveau_crc@pipe-a-source-rg.html
* igt@perf@per-context-mode-unprivileged:
- shard-iclb: NOTRUN -> [SKIP][115] ([fdo#109289]) +2 similar issues
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb5/igt@perf@per-context-mode-unprivileged.html
* igt@prime_nv_api@i915_nv_reimport_twice_check_flink_name:
- shard-apl: NOTRUN -> [SKIP][116] ([fdo#109271]) +199 similar issues
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl1/igt@prime_nv_api@i915_nv_reimport_twice_check_flink_name.html
* igt@prime_nv_api@i915_self_import:
- shard-tglb: NOTRUN -> [SKIP][117] ([fdo#109291]) +1 similar issue
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb6/igt@prime_nv_api@i915_self_import.html
- shard-iclb: NOTRUN -> [SKIP][118] ([fdo#109291]) +1 similar issue
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb7/igt@prime_nv_api@i915_self_import.html
* igt@runner@aborted:
- shard-snb: NOTRUN -> ([FAIL][119], [FAIL][120]) ([i915#3002] / [i915#698])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-snb6/igt@runner@aborted.html
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-snb5/igt@runner@aborted.html
* igt@sysfs_clients@recycle:
- shard-hsw: [PASS][121] -> [FAIL][122] ([i915#3028])
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-hsw2/igt@sysfs_clients@recycle.html
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-hsw2/igt@sysfs_clients@recycle.html
- shard-glk: [PASS][123] -> [FAIL][124] ([i915#3028])
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-glk3/igt@sysfs_clients@recycle.html
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk9/igt@sysfs_clients@recycle.html
- shard-tglb: [PASS][125] -> [FAIL][126] ([i915#3028])
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-tglb2/igt@sysfs_clients@recycle.html
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb5/igt@sysfs_clients@recycle.html
* igt@sysfs_clients@recycle-many:
- shard-apl: [PASS][127] -> [FAIL][128] ([i915#3028])
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-apl1/igt@sysfs_clients@recycle-many.html
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl3/igt@sysfs_clients@recycle-many.html
- shard-kbl: [PASS][129] -> [FAIL][130] ([i915#3028])
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-kbl4/igt@sysfs_clients@recycle-many.html
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl2/igt@sysfs_clients@recycle-many.html
* igt@sysfs_clients@split-10@bcs0:
- shard-apl: NOTRUN -> [SKIP][131] ([fdo#109271] / [i915#3026])
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-apl8/igt@sysfs_clients@split-10@bcs0.html
- shard-kbl: NOTRUN -> [SKIP][132] ([fdo#109271] / [i915#3026])
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-kbl6/igt@sysfs_clients@split-10@bcs0.html
#### Possible fixes ####
* igt@gem_ctx_persistence@close-replace-race:
- shard-glk: [TIMEOUT][133] ([i915#2918]) -> [PASS][134]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-glk7/igt@gem_ctx_persistence@close-replace-race.html
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk2/igt@gem_ctx_persistence@close-replace-race.html
* igt@gem_eio@unwedge-stress:
- shard-tglb: [TIMEOUT][135] ([i915#2369] / [i915#3063]) -> [PASS][136]
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-tglb3/igt@gem_eio@unwedge-stress.html
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-tglb2/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_balancer@hang:
- shard-iclb: [INCOMPLETE][137] ([i915#1895] / [i915#3031]) -> [PASS][138]
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-iclb4/igt@gem_exec_balancer@hang.html
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-iclb7/igt@gem_exec_balancer@hang.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [FAIL][139] ([i915#2842]) -> [PASS][140] +1 similar issue
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9836/shard-glk8/igt@gem_exec_fair@basic-pace-share@rcs0.html
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/shard-glk5/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_5579/index.html
[-- Attachment #1.2: Type: text/html, Size: 33833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices
2021-03-05 16:42 ` [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices Jeremy Cline
@ 2021-03-08 8:47 ` Petri Latvala
2021-03-08 12:41 ` Sharma, Swati2
0 siblings, 1 reply; 22+ messages in thread
From: Petri Latvala @ 2021-03-08 8:47 UTC (permalink / raw)
To: Jeremy Cline, Swati Sharma, Maarten Lankhorst; +Cc: igt-dev
On Fri, Mar 05, 2021 at 11:42:52AM -0500, Jeremy Cline wrote:
> According to the Intel documentation[0] I could find, HDR support is
> only in Kaby Lake+. Skip tests in kms_hdr if the hardware doesn't
> support HDR.
>
> [0] https://www.intel.com/content/dam/support/us/en/documents/graphics/HDR_Intel_Graphics_TechWhitePaper.pdf
>
> Signed-off-by: Jeremy Cline <jcline@redhat.com>
While that might be true, strictly speaking IGT tests are not testing
the HW capabilities but the kernel interfaces. The difference is often
only interesting for nitpicking.
However, in this case a good argument can be made either way, with
what the correct behaviour with setting the "max bpc" property when
the HW doesn't support HDR _output_ should be. IGT tests should be
written the way one would expect "real" userspace to behave; does the
documented kernel interface require userspace to detect the device id
somehow? The connector property is there so one would assume setting
it should work and do something.
A good argument can also be made that even though we're testing "just
the interface", we (Intel) should have a separate test that requires
actual HW support...
Swati, Maarten, thoughts on this? Are we even testing the right things
for i915 at all? Are we able to express the HW requirement for HDR
with something other than comparing devid? Should we? (If we should
not, please suggest a better way to get around the issue being fixed
here)
--
Petri Latvala
> ---
> tests/kms_hdr.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/tests/kms_hdr.c b/tests/kms_hdr.c
> index e9dd7f27..7617e8a5 100644
> --- a/tests/kms_hdr.c
> +++ b/tests/kms_hdr.c
> @@ -644,6 +644,12 @@ igt_main
> igt_require(data.display.is_atomic);
>
> igt_display_require_output(&data.display);
> +
> + /* According to Intel documentation, hardware prior to Kaby Lake does
> + * not support HDR.
> + */
> + if (is_i915_device(data.fd))
> + igt_require(AT_LEAST_GEN(intel_get_drm_devid(data.fd), 9));
> }
>
> igt_describe("Tests switching between different display output bpc modes");
> --
> 2.30.1
>
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices
2021-03-08 8:47 ` Petri Latvala
@ 2021-03-08 12:41 ` Sharma, Swati2
2021-03-08 12:53 ` Petri Latvala
0 siblings, 1 reply; 22+ messages in thread
From: Sharma, Swati2 @ 2021-03-08 12:41 UTC (permalink / raw)
To: Petri Latvala, Jeremy Cline, Maarten Lankhorst; +Cc: igt-dev
On 08-Mar-21 2:17 PM, Petri Latvala wrote:
> On Fri, Mar 05, 2021 at 11:42:52AM -0500, Jeremy Cline wrote:
>> According to the Intel documentation[0] I could find, HDR support is
>> only in Kaby Lake+. Skip tests in kms_hdr if the hardware doesn't
>> support HDR.
>>
>> [0] https://www.intel.com/content/dam/support/us/en/documents/graphics/HDR_Intel_Graphics_TechWhitePaper.pdf
>>
>> Signed-off-by: Jeremy Cline <jcline@redhat.com>
>
>
> While that might be true, strictly speaking IGT tests are not testing
> the HW capabilities but the kernel interfaces. The difference is often
> only interesting for nitpicking.
>
> However, in this case a good argument can be made either way, with
> what the correct behaviour with setting the "max bpc" property when
> the HW doesn't support HDR _output_ should be. IGT tests should be
> written the way one would expect "real" userspace to behave; does the
> documented kernel interface require userspace to detect the device id
> somehow? The connector property is there so one would assume setting
> it should work and do something.
>
> A good argument can also be made that even though we're testing "just
> the interface", we (Intel) should have a separate test that requires
> actual HW support...
>
> Swati, Maarten, thoughts on this? Are we even testing the right things
> for i915 at all? Are we able to express the HW requirement for HDR
> with something other than comparing devid? Should we? (If we should
> not, please suggest a better way to get around the issue being fixed
> here)
There are 2 types of tests which are being validated in kms_hdr
(i) bpc switch
(ii) hdr metadata
And both these tests will skip on platforms which doesn't support
respective connector
properties (MAX_BPC, HDR_OUTPUT_METADATA resp). These tests are
independent of platforms on which they are being tested.
This can be validated from the link below:
https://intel-gfx-ci.01.org/tree/drm-tip/shards-all.html?testfilter=kms_hdr
where you can see platforms which doesn't support either max_bpc or
hdr_metadata
connector properties; tests are being skipped.
And I don't think anything is being fixed here, with gen specific check
even bpc switch
tests cases won't get executed. MAX_BPC is supported by platforms prior
to gen9 aswell. But like said HDR is supported is gen9+; so we can lose
coverage of bpc switch test cases on non-HDR platforms.
IMO there is no need to express HW requirement for HDR; this is already
being
handled smoothly through connector properties.
>
>
--
~Swati Sharma
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices
2021-03-08 12:41 ` Sharma, Swati2
@ 2021-03-08 12:53 ` Petri Latvala
2021-03-08 15:06 ` Jeremy Cline
0 siblings, 1 reply; 22+ messages in thread
From: Petri Latvala @ 2021-03-08 12:53 UTC (permalink / raw)
To: Sharma, Swati2; +Cc: igt-dev
On Mon, Mar 08, 2021 at 06:11:09PM +0530, Sharma, Swati2 wrote:
>
>
> On 08-Mar-21 2:17 PM, Petri Latvala wrote:
> > On Fri, Mar 05, 2021 at 11:42:52AM -0500, Jeremy Cline wrote:
> > > According to the Intel documentation[0] I could find, HDR support is
> > > only in Kaby Lake+. Skip tests in kms_hdr if the hardware doesn't
> > > support HDR.
> > >
> > > [0] https://www.intel.com/content/dam/support/us/en/documents/graphics/HDR_Intel_Graphics_TechWhitePaper.pdf
> > >
> > > Signed-off-by: Jeremy Cline <jcline@redhat.com>
> >
> >
> > While that might be true, strictly speaking IGT tests are not testing
> > the HW capabilities but the kernel interfaces. The difference is often
> > only interesting for nitpicking.
> >
> > However, in this case a good argument can be made either way, with
> > what the correct behaviour with setting the "max bpc" property when
> > the HW doesn't support HDR _output_ should be. IGT tests should be
> > written the way one would expect "real" userspace to behave; does the
> > documented kernel interface require userspace to detect the device id
> > somehow? The connector property is there so one would assume setting
> > it should work and do something.
> >
> > A good argument can also be made that even though we're testing "just
> > the interface", we (Intel) should have a separate test that requires
> > actual HW support...
> >
> > Swati, Maarten, thoughts on this? Are we even testing the right things
> > for i915 at all? Are we able to express the HW requirement for HDR
> > with something other than comparing devid? Should we? (If we should
> > not, please suggest a better way to get around the issue being fixed
> > here)
>
> There are 2 types of tests which are being validated in kms_hdr
> (i) bpc switch
> (ii) hdr metadata
> And both these tests will skip on platforms which doesn't support respective
> connector
> properties (MAX_BPC, HDR_OUTPUT_METADATA resp). These tests are independent
> of platforms on which they are being tested.
> This can be validated from the link below:
> https://intel-gfx-ci.01.org/tree/drm-tip/shards-all.html?testfilter=kms_hdr
> where you can see platforms which doesn't support either max_bpc or
> hdr_metadata
> connector properties; tests are being skipped.
>
> And I don't think anything is being fixed here
What I meant is the fix in patch 2, removing the removal of the
primary plane, which was done because of a HSW limitation. Patch 1
(this thread) is then making sure HSW is unaffected by a spurious
failure. Sorry for not being clear when pulling more CCs.
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices
2021-03-08 12:53 ` Petri Latvala
@ 2021-03-08 15:06 ` Jeremy Cline
2021-03-09 14:01 ` Petri Latvala
0 siblings, 1 reply; 22+ messages in thread
From: Jeremy Cline @ 2021-03-08 15:06 UTC (permalink / raw)
To: Petri Latvala; +Cc: igt-dev
On Mon, Mar 08, 2021 at 02:53:39PM +0200, Petri Latvala wrote:
> On Mon, Mar 08, 2021 at 06:11:09PM +0530, Sharma, Swati2 wrote:
> >
> >
> > On 08-Mar-21 2:17 PM, Petri Latvala wrote:
> > > On Fri, Mar 05, 2021 at 11:42:52AM -0500, Jeremy Cline wrote:
> > > > According to the Intel documentation[0] I could find, HDR support is
> > > > only in Kaby Lake+. Skip tests in kms_hdr if the hardware doesn't
> > > > support HDR.
> > > >
> > > > [0] https://www.intel.com/content/dam/support/us/en/documents/graphics/HDR_Intel_Graphics_TechWhitePaper.pdf
> > > >
> > > > Signed-off-by: Jeremy Cline <jcline@redhat.com>
> > >
> > >
> > > While that might be true, strictly speaking IGT tests are not testing
> > > the HW capabilities but the kernel interfaces. The difference is often
> > > only interesting for nitpicking.
> > >
> > > However, in this case a good argument can be made either way, with
> > > what the correct behaviour with setting the "max bpc" property when
> > > the HW doesn't support HDR _output_ should be. IGT tests should be
> > > written the way one would expect "real" userspace to behave; does the
> > > documented kernel interface require userspace to detect the device id
> > > somehow? The connector property is there so one would assume setting
> > > it should work and do something.
> > >
> > > A good argument can also be made that even though we're testing "just
> > > the interface", we (Intel) should have a separate test that requires
> > > actual HW support...
> > >
> > > Swati, Maarten, thoughts on this? Are we even testing the right things
> > > for i915 at all? Are we able to express the HW requirement for HDR
> > > with something other than comparing devid? Should we? (If we should
> > > not, please suggest a better way to get around the issue being fixed
> > > here)
> >
> > There are 2 types of tests which are being validated in kms_hdr
> > (i) bpc switch
> > (ii) hdr metadata
> > And both these tests will skip on platforms which doesn't support respective
> > connector
> > properties (MAX_BPC, HDR_OUTPUT_METADATA resp). These tests are independent
> > of platforms on which they are being tested.
> > This can be validated from the link below:
> > https://intel-gfx-ci.01.org/tree/drm-tip/shards-all.html?testfilter=kms_hdr
> > where you can see platforms which doesn't support either max_bpc or
> > hdr_metadata
> > connector properties; tests are being skipped.
> >
> > And I don't think anything is being fixed here
>
> What I meant is the fix in patch 2, removing the removal of the
> primary plane, which was done because of a HSW limitation. Patch 1
> (this thread) is then making sure HSW is unaffected by a spurious
> failure. Sorry for not being clear when pulling more CCs.
>
There are definitely finer-grain ways to do this, but this "works" so I
figured it'd be good to start here and have a discussion about it.
One option would be to just wrap the plane-removal call in a device
check. Another would be to try and find a plane size that meets whatever
the scaling requirements are for hsw (assuming there's overlap between
the conflicting requirements of hardware).
I don't have a strong opinion about where the checks happen, it seems
like a trade-off between in-test complexity and the breadth of the test
matrix, and I can't say how useful it is to make sure the MAX_BPC
interface works on a specific generation of hardware. I'm happy to do
either of those options (or another option I've not considered),
whatever you folks think is the best trade-off.
Thanks,
Jeremy
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices
2021-03-08 15:06 ` Jeremy Cline
@ 2021-03-09 14:01 ` Petri Latvala
2021-03-10 12:48 ` Shankar, Uma
0 siblings, 1 reply; 22+ messages in thread
From: Petri Latvala @ 2021-03-09 14:01 UTC (permalink / raw)
To: Jeremy Cline; +Cc: igt-dev
On Mon, Mar 08, 2021 at 10:06:59AM -0500, Jeremy Cline wrote:
> On Mon, Mar 08, 2021 at 02:53:39PM +0200, Petri Latvala wrote:
> > On Mon, Mar 08, 2021 at 06:11:09PM +0530, Sharma, Swati2 wrote:
> > >
> > >
> > > On 08-Mar-21 2:17 PM, Petri Latvala wrote:
> > > > On Fri, Mar 05, 2021 at 11:42:52AM -0500, Jeremy Cline wrote:
> > > > > According to the Intel documentation[0] I could find, HDR support is
> > > > > only in Kaby Lake+. Skip tests in kms_hdr if the hardware doesn't
> > > > > support HDR.
> > > > >
> > > > > [0] https://www.intel.com/content/dam/support/us/en/documents/graphics/HDR_Intel_Graphics_TechWhitePaper.pdf
> > > > >
> > > > > Signed-off-by: Jeremy Cline <jcline@redhat.com>
> > > >
> > > >
> > > > While that might be true, strictly speaking IGT tests are not testing
> > > > the HW capabilities but the kernel interfaces. The difference is often
> > > > only interesting for nitpicking.
> > > >
> > > > However, in this case a good argument can be made either way, with
> > > > what the correct behaviour with setting the "max bpc" property when
> > > > the HW doesn't support HDR _output_ should be. IGT tests should be
> > > > written the way one would expect "real" userspace to behave; does the
> > > > documented kernel interface require userspace to detect the device id
> > > > somehow? The connector property is there so one would assume setting
> > > > it should work and do something.
> > > >
> > > > A good argument can also be made that even though we're testing "just
> > > > the interface", we (Intel) should have a separate test that requires
> > > > actual HW support...
> > > >
> > > > Swati, Maarten, thoughts on this? Are we even testing the right things
> > > > for i915 at all? Are we able to express the HW requirement for HDR
> > > > with something other than comparing devid? Should we? (If we should
> > > > not, please suggest a better way to get around the issue being fixed
> > > > here)
> > >
> > > There are 2 types of tests which are being validated in kms_hdr
> > > (i) bpc switch
> > > (ii) hdr metadata
> > > And both these tests will skip on platforms which doesn't support respective
> > > connector
> > > properties (MAX_BPC, HDR_OUTPUT_METADATA resp). These tests are independent
> > > of platforms on which they are being tested.
> > > This can be validated from the link below:
> > > https://intel-gfx-ci.01.org/tree/drm-tip/shards-all.html?testfilter=kms_hdr
> > > where you can see platforms which doesn't support either max_bpc or
> > > hdr_metadata
> > > connector properties; tests are being skipped.
> > >
> > > And I don't think anything is being fixed here
> >
> > What I meant is the fix in patch 2, removing the removal of the
> > primary plane, which was done because of a HSW limitation. Patch 1
> > (this thread) is then making sure HSW is unaffected by a spurious
> > failure. Sorry for not being clear when pulling more CCs.
> >
>
> There are definitely finer-grain ways to do this, but this "works" so I
> figured it'd be good to start here and have a discussion about it.
>
> One option would be to just wrap the plane-removal call in a device
> check. Another would be to try and find a plane size that meets whatever
> the scaling requirements are for hsw (assuming there's overlap between
> the conflicting requirements of hardware).
>
> I don't have a strong opinion about where the checks happen, it seems
> like a trade-off between in-test complexity and the breadth of the test
> matrix, and I can't say how useful it is to make sure the MAX_BPC
> interface works on a specific generation of hardware. I'm happy to do
> either of those options (or another option I've not considered),
> whatever you folks think is the best trade-off.
Checked how HSW actually behaves with this and
https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_300/shard-hsw4/igt@kms_hdr@bpc-switch.html
Swati, what's your opinion? if (amdgpudevice) around the plane removal
or what's best here?
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices
2021-03-09 14:01 ` Petri Latvala
@ 2021-03-10 12:48 ` Shankar, Uma
2021-03-10 12:53 ` Petri Latvala
0 siblings, 1 reply; 22+ messages in thread
From: Shankar, Uma @ 2021-03-10 12:48 UTC (permalink / raw)
To: Latvala, Petri, Jeremy Cline; +Cc: igt-dev
> -----Original Message-----
> From: Latvala, Petri <petri.latvala@intel.com>
> Sent: Tuesday, March 9, 2021 7:32 PM
> To: Jeremy Cline <jcline@redhat.com>
> Cc: Sharma, Swati2 <swati2.sharma@intel.com>; Maarten Lankhorst
> <maarten.lankhorst@linux.intel.com>; igt-dev@lists.freedesktop.org; Shankar, Uma
> <uma.shankar@intel.com>
> Subject: Re: [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake
> Intel devices
>
> On Mon, Mar 08, 2021 at 10:06:59AM -0500, Jeremy Cline wrote:
> > On Mon, Mar 08, 2021 at 02:53:39PM +0200, Petri Latvala wrote:
> > > On Mon, Mar 08, 2021 at 06:11:09PM +0530, Sharma, Swati2 wrote:
> > > >
> > > >
> > > > On 08-Mar-21 2:17 PM, Petri Latvala wrote:
> > > > > On Fri, Mar 05, 2021 at 11:42:52AM -0500, Jeremy Cline wrote:
> > > > > > According to the Intel documentation[0] I could find, HDR
> > > > > > support is only in Kaby Lake+. Skip tests in kms_hdr if the
> > > > > > hardware doesn't support HDR.
> > > > > >
> > > > > > [0]
> > > > > > https://www.intel.com/content/dam/support/us/en/documents/grap
> > > > > > hics/HDR_Intel_Graphics_TechWhitePaper.pdf
> > > > > >
> > > > > > Signed-off-by: Jeremy Cline <jcline@redhat.com>
> > > > >
> > > > >
> > > > > While that might be true, strictly speaking IGT tests are not
> > > > > testing the HW capabilities but the kernel interfaces. The
> > > > > difference is often only interesting for nitpicking.
> > > > >
> > > > > However, in this case a good argument can be made either way,
> > > > > with what the correct behaviour with setting the "max bpc"
> > > > > property when the HW doesn't support HDR _output_ should be. IGT
> > > > > tests should be written the way one would expect "real"
> > > > > userspace to behave; does the documented kernel interface
> > > > > require userspace to detect the device id somehow? The connector
> > > > > property is there so one would assume setting it should work and do
> something.
> > > > >
> > > > > A good argument can also be made that even though we're testing
> > > > > "just the interface", we (Intel) should have a separate test
> > > > > that requires actual HW support...
> > > > >
> > > > > Swati, Maarten, thoughts on this? Are we even testing the right
> > > > > things for i915 at all? Are we able to express the HW
> > > > > requirement for HDR with something other than comparing devid?
> > > > > Should we? (If we should not, please suggest a better way to get
> > > > > around the issue being fixed
> > > > > here)
> > > >
> > > > There are 2 types of tests which are being validated in kms_hdr
> > > > (i) bpc switch
> > > > (ii) hdr metadata
> > > > And both these tests will skip on platforms which doesn't support
> > > > respective connector properties (MAX_BPC, HDR_OUTPUT_METADATA
> > > > resp). These tests are independent of platforms on which they are
> > > > being tested.
> > > > This can be validated from the link below:
> > > > https://intel-gfx-ci.01.org/tree/drm-tip/shards-all.html?testfilte
> > > > r=kms_hdr where you can see platforms which doesn't support either
> > > > max_bpc or hdr_metadata connector properties; tests are being
> > > > skipped.
> > > >
> > > > And I don't think anything is being fixed here
> > >
> > > What I meant is the fix in patch 2, removing the removal of the
> > > primary plane, which was done because of a HSW limitation. Patch 1
> > > (this thread) is then making sure HSW is unaffected by a spurious
> > > failure. Sorry for not being clear when pulling more CCs.
> > >
> >
> > There are definitely finer-grain ways to do this, but this "works" so
> > I figured it'd be good to start here and have a discussion about it.
> >
> > One option would be to just wrap the plane-removal call in a device
> > check. Another would be to try and find a plane size that meets
> > whatever the scaling requirements are for hsw (assuming there's
> > overlap between the conflicting requirements of hardware).
> >
> > I don't have a strong opinion about where the checks happen, it seems
> > like a trade-off between in-test complexity and the breadth of the
> > test matrix, and I can't say how useful it is to make sure the MAX_BPC
> > interface works on a specific generation of hardware. I'm happy to do
> > either of those options (or another option I've not considered),
> > whatever you folks think is the best trade-off.
>
>
> Checked how HSW actually behaves with this and
>
> https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_300/shard-
> hsw4/igt@kms_hdr@bpc-switch.html
>
> Swati, what's your opinion? if (amdgpudevice) around the plane removal or what's
> best here?
Hi Petri,
I feel limiting it to amdgpudevice seems a safer and easier route here without disturbing the legacy behavior.
Regards,
Uma Shankar
>
>
> --
> Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices
2021-03-10 12:48 ` Shankar, Uma
@ 2021-03-10 12:53 ` Petri Latvala
2021-03-10 14:55 ` Sharma, Swati2
0 siblings, 1 reply; 22+ messages in thread
From: Petri Latvala @ 2021-03-10 12:53 UTC (permalink / raw)
To: Shankar, Uma; +Cc: igt-dev
On Wed, Mar 10, 2021 at 02:48:32PM +0200, Shankar, Uma wrote:
>
>
> > -----Original Message-----
> > From: Latvala, Petri <petri.latvala@intel.com>
> > Sent: Tuesday, March 9, 2021 7:32 PM
> > To: Jeremy Cline <jcline@redhat.com>
> > Cc: Sharma, Swati2 <swati2.sharma@intel.com>; Maarten Lankhorst
> > <maarten.lankhorst@linux.intel.com>; igt-dev@lists.freedesktop.org; Shankar, Uma
> > <uma.shankar@intel.com>
> > Subject: Re: [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake
> > Intel devices
> >
> > On Mon, Mar 08, 2021 at 10:06:59AM -0500, Jeremy Cline wrote:
> > > On Mon, Mar 08, 2021 at 02:53:39PM +0200, Petri Latvala wrote:
> > > > On Mon, Mar 08, 2021 at 06:11:09PM +0530, Sharma, Swati2 wrote:
> > > > >
> > > > >
> > > > > On 08-Mar-21 2:17 PM, Petri Latvala wrote:
> > > > > > On Fri, Mar 05, 2021 at 11:42:52AM -0500, Jeremy Cline wrote:
> > > > > > > According to the Intel documentation[0] I could find, HDR
> > > > > > > support is only in Kaby Lake+. Skip tests in kms_hdr if the
> > > > > > > hardware doesn't support HDR.
> > > > > > >
> > > > > > > [0]
> > > > > > > https://www.intel.com/content/dam/support/us/en/documents/grap
> > > > > > > hics/HDR_Intel_Graphics_TechWhitePaper.pdf
> > > > > > >
> > > > > > > Signed-off-by: Jeremy Cline <jcline@redhat.com>
> > > > > >
> > > > > >
> > > > > > While that might be true, strictly speaking IGT tests are not
> > > > > > testing the HW capabilities but the kernel interfaces. The
> > > > > > difference is often only interesting for nitpicking.
> > > > > >
> > > > > > However, in this case a good argument can be made either way,
> > > > > > with what the correct behaviour with setting the "max bpc"
> > > > > > property when the HW doesn't support HDR _output_ should be. IGT
> > > > > > tests should be written the way one would expect "real"
> > > > > > userspace to behave; does the documented kernel interface
> > > > > > require userspace to detect the device id somehow? The connector
> > > > > > property is there so one would assume setting it should work and do
> > something.
> > > > > >
> > > > > > A good argument can also be made that even though we're testing
> > > > > > "just the interface", we (Intel) should have a separate test
> > > > > > that requires actual HW support...
> > > > > >
> > > > > > Swati, Maarten, thoughts on this? Are we even testing the right
> > > > > > things for i915 at all? Are we able to express the HW
> > > > > > requirement for HDR with something other than comparing devid?
> > > > > > Should we? (If we should not, please suggest a better way to get
> > > > > > around the issue being fixed
> > > > > > here)
> > > > >
> > > > > There are 2 types of tests which are being validated in kms_hdr
> > > > > (i) bpc switch
> > > > > (ii) hdr metadata
> > > > > And both these tests will skip on platforms which doesn't support
> > > > > respective connector properties (MAX_BPC, HDR_OUTPUT_METADATA
> > > > > resp). These tests are independent of platforms on which they are
> > > > > being tested.
> > > > > This can be validated from the link below:
> > > > > https://intel-gfx-ci.01.org/tree/drm-tip/shards-all.html?testfilte
> > > > > r=kms_hdr where you can see platforms which doesn't support either
> > > > > max_bpc or hdr_metadata connector properties; tests are being
> > > > > skipped.
> > > > >
> > > > > And I don't think anything is being fixed here
> > > >
> > > > What I meant is the fix in patch 2, removing the removal of the
> > > > primary plane, which was done because of a HSW limitation. Patch 1
> > > > (this thread) is then making sure HSW is unaffected by a spurious
> > > > failure. Sorry for not being clear when pulling more CCs.
> > > >
> > >
> > > There are definitely finer-grain ways to do this, but this "works" so
> > > I figured it'd be good to start here and have a discussion about it.
> > >
> > > One option would be to just wrap the plane-removal call in a device
> > > check. Another would be to try and find a plane size that meets
> > > whatever the scaling requirements are for hsw (assuming there's
> > > overlap between the conflicting requirements of hardware).
> > >
> > > I don't have a strong opinion about where the checks happen, it seems
> > > like a trade-off between in-test complexity and the breadth of the
> > > test matrix, and I can't say how useful it is to make sure the MAX_BPC
> > > interface works on a specific generation of hardware. I'm happy to do
> > > either of those options (or another option I've not considered),
> > > whatever you folks think is the best trade-off.
> >
> >
> > Checked how HSW actually behaves with this and
> >
> > https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_300/shard-
> > hsw4/igt@kms_hdr@bpc-switch.html
> >
> > Swati, what's your opinion? if (amdgpudevice) around the plane removal or what's
> > best here?
>
> Hi Petri,
> I feel limiting it to amdgpudevice seems a safer and easier route here without disturbing the legacy behavior.
Thanks, let's go with that then.
Jeremy, see above.
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices
2021-03-10 12:53 ` Petri Latvala
@ 2021-03-10 14:55 ` Sharma, Swati2
0 siblings, 0 replies; 22+ messages in thread
From: Sharma, Swati2 @ 2021-03-10 14:55 UTC (permalink / raw)
To: Petri Latvala, Shankar, Uma; +Cc: igt-dev
On 10-Mar-21 6:23 PM, Petri Latvala wrote:
> On Wed, Mar 10, 2021 at 02:48:32PM +0200, Shankar, Uma wrote:
>>
>>
>>> -----Original Message-----
>>> From: Latvala, Petri <petri.latvala@intel.com>
>>> Sent: Tuesday, March 9, 2021 7:32 PM
>>> To: Jeremy Cline <jcline@redhat.com>
>>> Cc: Sharma, Swati2 <swati2.sharma@intel.com>; Maarten Lankhorst
>>> <maarten.lankhorst@linux.intel.com>; igt-dev@lists.freedesktop.org; Shankar, Uma
>>> <uma.shankar@intel.com>
>>> Subject: Re: [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake
>>> Intel devices
>>>
>>> On Mon, Mar 08, 2021 at 10:06:59AM -0500, Jeremy Cline wrote:
>>>> On Mon, Mar 08, 2021 at 02:53:39PM +0200, Petri Latvala wrote:
>>>>> On Mon, Mar 08, 2021 at 06:11:09PM +0530, Sharma, Swati2 wrote:
>>>>>>
>>>>>>
>>>>>> On 08-Mar-21 2:17 PM, Petri Latvala wrote:
>>>>>>> On Fri, Mar 05, 2021 at 11:42:52AM -0500, Jeremy Cline wrote:
>>>>>>>> According to the Intel documentation[0] I could find, HDR
>>>>>>>> support is only in Kaby Lake+. Skip tests in kms_hdr if the
>>>>>>>> hardware doesn't support HDR.
>>>>>>>>
>>>>>>>> [0]
>>>>>>>> https://www.intel.com/content/dam/support/us/en/documents/grap
>>>>>>>> hics/HDR_Intel_Graphics_TechWhitePaper.pdf
>>>>>>>>
>>>>>>>> Signed-off-by: Jeremy Cline <jcline@redhat.com>
>>>>>>>
>>>>>>>
>>>>>>> While that might be true, strictly speaking IGT tests are not
>>>>>>> testing the HW capabilities but the kernel interfaces. The
>>>>>>> difference is often only interesting for nitpicking.
>>>>>>>
>>>>>>> However, in this case a good argument can be made either way,
>>>>>>> with what the correct behaviour with setting the "max bpc"
>>>>>>> property when the HW doesn't support HDR _output_ should be. IGT
>>>>>>> tests should be written the way one would expect "real"
>>>>>>> userspace to behave; does the documented kernel interface
>>>>>>> require userspace to detect the device id somehow? The connector
>>>>>>> property is there so one would assume setting it should work and do
>>> something.
>>>>>>>
>>>>>>> A good argument can also be made that even though we're testing
>>>>>>> "just the interface", we (Intel) should have a separate test
>>>>>>> that requires actual HW support...
>>>>>>>
>>>>>>> Swati, Maarten, thoughts on this? Are we even testing the right
>>>>>>> things for i915 at all? Are we able to express the HW
>>>>>>> requirement for HDR with something other than comparing devid?
>>>>>>> Should we? (If we should not, please suggest a better way to get
>>>>>>> around the issue being fixed
>>>>>>> here)
>>>>>>
>>>>>> There are 2 types of tests which are being validated in kms_hdr
>>>>>> (i) bpc switch
>>>>>> (ii) hdr metadata
>>>>>> And both these tests will skip on platforms which doesn't support
>>>>>> respective connector properties (MAX_BPC, HDR_OUTPUT_METADATA
>>>>>> resp). These tests are independent of platforms on which they are
>>>>>> being tested.
>>>>>> This can be validated from the link below:
>>>>>> https://intel-gfx-ci.01.org/tree/drm-tip/shards-all.html?testfilte
>>>>>> r=kms_hdr where you can see platforms which doesn't support either
>>>>>> max_bpc or hdr_metadata connector properties; tests are being
>>>>>> skipped.
>>>>>>
>>>>>> And I don't think anything is being fixed here
>>>>>
>>>>> What I meant is the fix in patch 2, removing the removal of the
>>>>> primary plane, which was done because of a HSW limitation. Patch 1
>>>>> (this thread) is then making sure HSW is unaffected by a spurious
>>>>> failure. Sorry for not being clear when pulling more CCs.
>>>>>
>>>>
>>>> There are definitely finer-grain ways to do this, but this "works" so
>>>> I figured it'd be good to start here and have a discussion about it.
>>>>
>>>> One option would be to just wrap the plane-removal call in a device
>>>> check. Another would be to try and find a plane size that meets
>>>> whatever the scaling requirements are for hsw (assuming there's
>>>> overlap between the conflicting requirements of hardware).
>>>>
>>>> I don't have a strong opinion about where the checks happen, it seems
>>>> like a trade-off between in-test complexity and the breadth of the
>>>> test matrix, and I can't say how useful it is to make sure the MAX_BPC
>>>> interface works on a specific generation of hardware. I'm happy to do
>>>> either of those options (or another option I've not considered),
>>>> whatever you folks think is the best trade-off.
>>>
>>>
>>> Checked how HSW actually behaves with this and
>>>
>>> https://intel-gfx-ci.01.org/tree/drm-tip/TrybotIGT_300/shard-
>>> hsw4/igt@kms_hdr@bpc-switch.html
>>>
>>> Swati, what's your opinion? if (amdgpudevice) around the plane removal or what's
>>> best here?
>>
>> Hi Petri,
>> I feel limiting it to amdgpudevice seems a safer and easier route here without disturbing the legacy behavior.
>
> Thanks, let's go with that then.
>
> Jeremy, see above.
Yes, agree with Uma.
>
>
--
~Swati Sharma
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* [igt-dev] [PATCH i-g-t v3] tests/kms_hdr: Fix bpc-switch tests on AMD hardware
2021-02-19 17:27 [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
` (4 preceding siblings ...)
2021-03-05 21:42 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
@ 2021-03-10 16:34 ` Jeremy Cline
2021-03-10 16:38 ` Shankar, Uma
2021-03-10 16:45 ` [igt-dev] ✗ Fi.CI.BUILD: failure for tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev3) Patchwork
6 siblings, 1 reply; 22+ messages in thread
From: Jeremy Cline @ 2021-03-10 16:34 UTC (permalink / raw)
To: igt-dev; +Cc: petri.latvala
Kernel commit b836a274b797 ("drm/amdgpu/dc: Require primary plane to be
enabled whenever the CRTC is") causes the bpc-switch tests to fail
since the primary plane fb is being removed, which leads to the next
atomic commit failing with -EINVAL.
Fix this by leaving the primary plane in place for amdgpu devices.
Signed-off-by: Jeremy Cline <jcline@redhat.com>
---
Changes from v2:
- Instead of skipping on pre-Kaby Lake, only remove the primary
plane for AMD devices (thanks for the feedback Petri, Swati,
and Uma!)
tests/kms_hdr.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/tests/kms_hdr.c b/tests/kms_hdr.c
index e9dd7f27..5b8529c8 100644
--- a/tests/kms_hdr.c
+++ b/tests/kms_hdr.c
@@ -223,7 +223,14 @@ static void test_bpc_switch_on_output(data_t *data, igt_output_t *output,
data->h = afb.height;
}
- igt_plane_set_fb(data->primary, NULL);
+ /*
+ * amdgpu requires a primary plane when the CRTC is enabled.
+ * However, some older Intel hardware (hsw) have scaling
+ * requirements that are not met by the plane, so remove it
+ * for non-AMD devices.
+ */
+ if (!is_amdgpu_device(data->fd))
+ igt_plane_set_fb(data->primary, NULL);
/*
* i915 driver doesn't expose max bpc as debugfs entry,
--
2.30.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply related [flat|nested] 22+ messages in thread
* Re: [igt-dev] [PATCH i-g-t v3] tests/kms_hdr: Fix bpc-switch tests on AMD hardware
2021-03-10 16:34 ` [igt-dev] [PATCH i-g-t v3] tests/kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
@ 2021-03-10 16:38 ` Shankar, Uma
0 siblings, 0 replies; 22+ messages in thread
From: Shankar, Uma @ 2021-03-10 16:38 UTC (permalink / raw)
To: Jeremy Cline, igt-dev; +Cc: Latvala, Petri
> -----Original Message-----
> From: Jeremy Cline <jcline@redhat.com>
> Sent: Wednesday, March 10, 2021 10:05 PM
> To: igt-dev@lists.freedesktop.org
> Cc: Latvala, Petri <petri.latvala@intel.com>; Shankar, Uma
> <uma.shankar@intel.com>; Sharma, Swati2 <swati2.sharma@intel.com>;
> maarten.lankhorst@linux.intel.com; nicholas.kazlauskas@amd.com; Jeremy Cline
> <jcline@redhat.com>
> Subject: [PATCH i-g-t v3] tests/kms_hdr: Fix bpc-switch tests on AMD hardware
>
> Kernel commit b836a274b797 ("drm/amdgpu/dc: Require primary plane to be
> enabled whenever the CRTC is") causes the bpc-switch tests to fail since the primary
> plane fb is being removed, which leads to the next atomic commit failing with -
> EINVAL.
>
> Fix this by leaving the primary plane in place for amdgpu devices.
>
> Signed-off-by: Jeremy Cline <jcline@redhat.com>
> ---
> Changes from v2:
> - Instead of skipping on pre-Kaby Lake, only remove the primary
> plane for AMD devices (thanks for the feedback Petri, Swati,
> and Uma!)
Looks good.
Reviewed-by: Uma Shankar <uma.shankar@intel.com>
> tests/kms_hdr.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/tests/kms_hdr.c b/tests/kms_hdr.c index e9dd7f27..5b8529c8 100644
> --- a/tests/kms_hdr.c
> +++ b/tests/kms_hdr.c
> @@ -223,7 +223,14 @@ static void test_bpc_switch_on_output(data_t *data,
> igt_output_t *output,
> data->h = afb.height;
> }
>
> - igt_plane_set_fb(data->primary, NULL);
> + /*
> + * amdgpu requires a primary plane when the CRTC is enabled.
> + * However, some older Intel hardware (hsw) have scaling
> + * requirements that are not met by the plane, so remove it
> + * for non-AMD devices.
> + */
> + if (!is_amdgpu_device(data->fd))
> + igt_plane_set_fb(data->primary, NULL);
>
> /*
> * i915 driver doesn't expose max bpc as debugfs entry,
> --
> 2.30.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* [igt-dev] ✗ Fi.CI.BUILD: failure for tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev3)
2021-02-19 17:27 [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
` (5 preceding siblings ...)
2021-03-10 16:34 ` [igt-dev] [PATCH i-g-t v3] tests/kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
@ 2021-03-10 16:45 ` Patchwork
2021-03-11 9:01 ` Petri Latvala
6 siblings, 1 reply; 22+ messages in thread
From: Patchwork @ 2021-03-10 16:45 UTC (permalink / raw)
To: Jeremy Cline; +Cc: igt-dev
== Series Details ==
Series: tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev3)
URL : https://patchwork.freedesktop.org/series/87232/
State : failure
== Summary ==
Applying: tests/kms_hdr: Fix bpc-switch tests on AMD hardware
Applying: kms_hdr: Fix bpc-switch tests on AMD hardware
Using index info to reconstruct a base tree...
M tests/kms_hdr.c
Falling back to patching base and 3-way merge...
Auto-merging tests/kms_hdr.c
CONFLICT (content): Merge conflict in tests/kms_hdr.c
Patch failed at 0002 kms_hdr: Fix bpc-switch tests on AMD hardware
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [igt-dev] ✗ Fi.CI.BUILD: failure for tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev3)
2021-03-10 16:45 ` [igt-dev] ✗ Fi.CI.BUILD: failure for tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev3) Patchwork
@ 2021-03-11 9:01 ` Petri Latvala
0 siblings, 0 replies; 22+ messages in thread
From: Petri Latvala @ 2021-03-11 9:01 UTC (permalink / raw)
To: igt-dev
On Wed, Mar 10, 2021 at 04:45:21PM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev3)
> URL : https://patchwork.freedesktop.org/series/87232/
> State : failure
>
> == Summary ==
>
> Applying: tests/kms_hdr: Fix bpc-switch tests on AMD hardware
> Applying: kms_hdr: Fix bpc-switch tests on AMD hardware
> Using index info to reconstruct a base tree...
> M tests/kms_hdr.c
> Falling back to patching base and 3-way merge...
> Auto-merging tests/kms_hdr.c
> CONFLICT (content): Merge conflict in tests/kms_hdr.c
> Patch failed at 0002 kms_hdr: Fix bpc-switch tests on AMD hardware
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
Just patchwork being confused.
Merged this, thanks to all involved!
--
Petri Latvala
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2021-03-11 9:01 UTC | newest]
Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-19 17:27 [igt-dev] [PATCH i-g-t] tests/kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
2021-02-19 18:27 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-02-19 19:35 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-02-19 22:00 ` Jeremy Cline
2021-03-05 16:42 ` [igt-dev] [PATCH i-g-t v2 0/2] Fix up the HDR tests for AMD devices Jeremy Cline
2021-03-05 16:42 ` [igt-dev] [PATCH i-g-t v2 1/2] kms_hdr: Skip HDR tests on pre-Kaby Lake Intel devices Jeremy Cline
2021-03-08 8:47 ` Petri Latvala
2021-03-08 12:41 ` Sharma, Swati2
2021-03-08 12:53 ` Petri Latvala
2021-03-08 15:06 ` Jeremy Cline
2021-03-09 14:01 ` Petri Latvala
2021-03-10 12:48 ` Shankar, Uma
2021-03-10 12:53 ` Petri Latvala
2021-03-10 14:55 ` Sharma, Swati2
2021-03-05 16:42 ` [igt-dev] [PATCH i-g-t v2 2/2] kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
2021-03-05 16:48 ` Kazlauskas, Nicholas
2021-03-05 17:17 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev2) Patchwork
2021-03-05 21:42 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-03-10 16:34 ` [igt-dev] [PATCH i-g-t v3] tests/kms_hdr: Fix bpc-switch tests on AMD hardware Jeremy Cline
2021-03-10 16:38 ` Shankar, Uma
2021-03-10 16:45 ` [igt-dev] ✗ Fi.CI.BUILD: failure for tests/kms_hdr: Fix bpc-switch tests on AMD hardware (rev3) Patchwork
2021-03-11 9:01 ` Petri Latvala
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.