drm/i915: Fix display problems after resume

PATCH Superseded Thomas Hellström 3 participants 6 messages Sep 12, 2022 – Sep 13, 2022

Subsystems (2)

DRM drivers Intel i915

lore

Share & tools

lore

Thomas Hellström

author

2022-09-12 12:20 UTC #0 lore raw

PATCH 1/1 drm/i915: Fix display problems after resume

Commit 39a2bd34c933 ("drm/i915: Use the vma resource as argument for gtt binding / unbinding") introduced a regression that due to the vma resource tracking of the binding state, dpt ptes were not correctly repopulated. Fix this by clearing the vma resource state before repopulating. The state will subsequently be restored by the bind_vma operation.

Fixes 39a2bd34c933 ("drm/i915: Use the vma resource as argument for gtt binding / unbinding")

Signed-off-by Thomas Hellström <[email protected]>

---
 drivers/gpu/drm/i915/gt/intel_ggtt.c | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

drivers/gpu/drm/i915/gt/intel_ggtt.c +7 -1

index 30cf5c3369d9..2049a00417af 100644
@@ -1275,10 +1275,16 @@ bool i915_ggtt_resume_vm(struct i915_address_space *vm)
 			atomic_read(&vma->flags) & I915_VMA_BIND_MASK;
 
 		GEM_BUG_ON(!was_bound);
-		if (!retained_ptes)
+		if (!retained_ptes) {
+			/*
+			 * Clear the bound flags of the vma resource to allow
+			 * ptes to be repopulated.
+			 */
+			vma->resource->bound_flags = 0;
 			vma->ops->bind_vma(vm, NULL, vma->resource,
 					   obj ? obj->cache_level : 0,
 					   was_bound);
+		}
 		if (obj) { /* only used during resume => exclusive access */
 			write_domain_objs |= fetch_and_zero(&obj->write_domain);
 			obj->read_domains |= I915_GEM_DOMAIN_GTT;

Signature · 1 line

2.34.1

Ville Syrjälä

2022-09-12 12:43 UTC #1 lore raw

Quoted 3 lines · Thomas Hellström

Commit 39a2bd34c933 ("drm/i915: Use the vma resource as argument for gtt binding / unbinding") introduced a regression that due to the vma resource tracking of the binding state, dpt ptes were not correctly repopulated.

Doesn't this mean all ggtt ptes weren't repopulated? So I'm wondering how anything at all has been working?

Quoted 33 lines

Fix this by clearing the vma resource state before repopulating. The state will subsequently be restored by the bind_vma operation.

Fixes 39a2bd34c933 ("drm/i915: Use the vma resource as argument for gtt binding / unbinding")

Signed-off-by Thomas Hellström <[email protected]>

---
 drivers/gpu/drm/i915/gt/intel_ggtt.c | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

drivers/gpu/drm/i915/gt/intel_ggtt.c +7 -1

index 30cf5c3369d9..2049a00417af 100644
@@ -1275,10 +1275,16 @@ bool i915_ggtt_resume_vm(struct i915_address_space *vm)
 			atomic_read(&vma->flags) & I915_VMA_BIND_MASK;
 
 		GEM_BUG_ON(!was_bound);
-		if (!retained_ptes)
+		if (!retained_ptes) {
+			/*
+			 * Clear the bound flags of the vma resource to allow
+			 * ptes to be repopulated.
+			 */
+			vma->resource->bound_flags = 0;
 			vma->ops->bind_vma(vm, NULL, vma->resource,
 					   obj ? obj->cache_level : 0,
 					   was_bound);
+		}
 		if (obj) { /* only used during resume => exclusive access */
 			write_domain_objs |= fetch_and_zero(&obj->write_domain);
 			obj->read_domains |= I915_GEM_DOMAIN_GTT;

Signature · 1 line

2.34.1

Signature · 2 lines

Ville Syrjälä
Intel

Thomas Hellström

author

2022-09-12 12:49 UTC #2 lore raw

Quoted 10 lines · Ville Syrjälä

Quoted 6 lines · Thomas Hellström
Commit 39a2bd34c933 ("drm/i915: Use the vma resource as argument for gtt
binding / unbinding") introduced a regression that due to the vma resource
tracking of the binding state, dpt ptes were not correctly repopulated.
Doesn't this mean all ggtt ptes weren't repopulated? So I'm wondering how anything at all has been working?

ggtt ptes had a different check that was copy-pasted from the pre-vma- resource code and that wasn't that strict. Hence why it worked.

/Thomas

Quoted 43 lines

Quoted 42 lines
Fix this by clearing the vma resource state before repopulating. The state will subsequently be restored by the bind_vma operation.
Fixes 39a2bd34c933 ("drm/i915: Use the vma resource as argument
for gtt binding / unbinding")
Signed-off-by Thomas Hellström <[email protected]>
---
drivers/gpu/drm/i915/gt/intel_ggtt.c | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/gt/intel_ggtt.c +0 -0
index 30cf5c3369d9..2049a00417af 100644
@@ -1275,10 +1275,16 @@ bool i915_ggtt_resume_vm(struct
 i915_address_space *vm)
                        atomic_read(&vma->flags) & I915_VMA_BIND_MASK;

                GEM_BUG_ON(!was_bound);
-               if (!retained_ptes)
+               if (!retained_ptes) {
+                       /*
+                        * Clear the bound flags of the vma resource to allow
+                        * ptes to be repopulated.
+                        */
+                       vma->resource->bound_flags = 0; vma->ops->bind_vma(vm, NULL, vma->resource, obj ? obj->cache_level :
0,
                                           was_bound);
+               }
                if (obj) { /* only used during resume => exclusive access */
                        write_domain_objs |= fetch_and_zero(&obj-
Quoted 1 line
write_domain);
                        obj->read_domains |= I915_GEM_DOMAIN_GTT;
Signature · 1 line
2.34.1

Ville Syrjälä

2022-09-12 16:49 UTC #3 lore raw

Quoted 9 lines · Thomas Hellström

Quoted 8 lines · Ville Syrjälä
Quoted 6 lines · Thomas Hellström
Commit 39a2bd34c933 ("drm/i915: Use the vma resource as argument for gtt
binding / unbinding") introduced a regression that due to the vma resource
tracking of the binding state, dpt ptes were not correctly repopulated.

Quoted 5 lines

Quoted 2 lines
Doesn't this mean all ggtt ptes weren't repopulated? So I'm wondering how anything at all has been working?
ggtt ptes had a different check that was copy-pasted from the pre-vma- resource code and that wasn't that strict. Hence why it worked.

The ggtt one seems to want to skip if the vma is already bound with the other flag than what we're using this time, but doesn't skip if it's already bound with the same flag(s). I have no idea what it's trying to achieve there.

The dpt case skips if it's a bound at all, which seems much more obvious but the fact that ggtt code never did that makes me suspect it's not that clear cut.

So seems to me that the two checks are trying to do achieve different goals, but at least I can't tell why that is.

Signature · 2 lines

Ville Syrjälä
Intel

Patchwork

2022-09-12 20:21 UTC #4 lore raw

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Fix display problems after resume

In reply to Thomas Hellström

== Series Details ==

Series: drm/i915: Fix display problems after resume
URL : https://patchwork.freedesktop.org/series/108432/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_12123 -> Patchwork_108432v1
====================================================

Summary
-------

**SUCCESS**

No regressions found.

External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/index.html

Participating hosts (42 -> 39)
------------------------------

Missing (3): fi-ctg-p8600 fi-hsw-4770 fi-bdw-samus

Known issues
------------

Here are the changes found in Patchwork_108432v1 that come from known issues:

### IGT changes ###

#### Issues hit ####

* igt@i915_selftest@live@requests:
- fi-blb-e6850: [PASS][1] -> [DMESG-FAIL][2] ([i915#4528])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/fi-blb-e6850/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/fi-blb-e6850/igt@i915_selftest@[email protected]

#### Possible fixes ####

* igt@gem_exec_gttfill@basic:
- {bat-rpls-2}: [DMESG-WARN][3] -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/bat-rpls-2/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/bat-rpls-2/igt@[email protected]

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

[i915#2867]: https://gitlab.freedesktop.org/drm/intel/issues/2867
[i915#4258]: https://gitlab.freedesktop.org/drm/intel/issues/4258
[i915#4528]: https://gitlab.freedesktop.org/drm/intel/issues/4528
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#5537]: https://gitlab.freedesktop.org/drm/intel/issues/5537
[i915#6257]: https://gitlab.freedesktop.org/drm/intel/issues/6257
[i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367

Build changes
-------------

* Linux: CI_DRM_12123 -> Patchwork_108432v1

CI-20190529: 20190529
CI_DRM_12123: 5dd153b15e2e3198fca3d84db9e155f454645f91 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6650: f7aff600ab16d6405f0704b1743d2b7909715752 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_108432v1: 5dd153b15e2e3198fca3d84db9e155f454645f91 @ git://anongit.freedesktop.org/gfx-ci/linux

### Linux commits

a6309c422ba4 drm/i915: Fix display problems after resume

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/index.html

Patchwork

2022-09-13 01:41 UTC #5 lore raw

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Fix display problems after resume

In reply to Thomas Hellström

== Series Details ==

Series: drm/i915: Fix display problems after resume
URL : https://patchwork.freedesktop.org/series/108432/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_12123_full -> Patchwork_108432v1_full
====================================================

Summary
-------

**SUCCESS**

No regressions found.

Participating hosts (11 -> 11)
------------------------------

No changes in participating hosts

Known issues
------------

Here are the changes found in Patchwork_108432v1_full that come from known issues:

### CI changes ###

#### Issues hit ####

### IGT changes ###

#### Issues hit ####

* igt@gem_ctx_exec@basic-nohangcheck:
- shard-tglb: [PASS][51] -> [FAIL][52] ([i915#6268])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-tglb7/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-tglb6/igt@[email protected]

* igt@gem_eio@kms:
- shard-tglb: [PASS][53] -> [FAIL][54] ([i915#5784])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-tglb7/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-tglb3/igt@[email protected]

* igt@gem_exec_balancer@parallel-keep-in-fence:
- shard-iclb: [PASS][55] -> [SKIP][56] ([i915#4525]) +3 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-iclb4/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb7/igt@[email protected]

* igt@gem_exec_fair@basic-none@vcs1:
- shard-iclb: NOTRUN -> [FAIL][57] ([i915#2842]) +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb2/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [PASS][58] -> [FAIL][59] ([i915#2842])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-tglb1/igt@gem_exec_fair@[email protected]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-tglb3/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-glk: [PASS][60] -> [FAIL][61] ([i915#2842])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-glk5/igt@gem_exec_fair@[email protected]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-glk9/igt@gem_exec_fair@[email protected]

* igt@i915_pm_dc@dc6-dpms:
- shard-iclb: [PASS][62] -> [FAIL][63] ([i915#454])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-iclb6/igt@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb3/igt@[email protected]

* igt@i915_pm_rps@engine-order:
- shard-glk: [PASS][64] -> [FAIL][65] ([i915#6537])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-glk2/igt@[email protected]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-glk7/igt@[email protected]

* igt@i915_selftest@live@hangcheck:
- shard-tglb: [PASS][66] -> [DMESG-WARN][67] ([i915#5591])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-tglb7/igt@i915_selftest@[email protected]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-tglb3/igt@i915_selftest@[email protected]

* igt@i915_suspend@sysfs-reader:
- shard-apl: [PASS][68] -> [DMESG-WARN][69] ([i915#180]) +2 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-apl4/igt@[email protected]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-apl8/igt@[email protected]

* igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions:
- shard-glk: [PASS][70] -> [FAIL][71] ([i915#2346])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-glk6/igt@kms_cursor_legacy@[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-glk5/igt@kms_cursor_legacy@[email protected]

* igt@kms_dither@fb-8bpc-vs-panel-6bpc@pipe-a-hdmi-a-1:
- shard-glk: NOTRUN -> [SKIP][72] ([fdo#109271])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-glk3/igt@kms_dither@[email protected]

* igt@kms_flip@2x-flip-vs-absolute-wf_vblank-interruptible:
- shard-iclb: NOTRUN -> [SKIP][73] ([fdo#109274])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb3/igt@kms_flip@2x-flip-vs-absolute-wf_vblank-interruptible.html

* igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-upscaling@pipe-a-valid-mode:
- shard-iclb: NOTRUN -> [SKIP][74] ([i915#2587] / [i915#2672]) +5 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb4/igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-upscaling@pipe-a-valid-mode.html

* igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-32bpp-yftile-upscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][75] ([i915#2672]) +8 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-32bpp-yftile-upscaling@pipe-a-default-mode.html

* igt@kms_plane_scaling@planes-downscale-factor-0-5@pipe-a-edp-1:
- shard-iclb: [PASS][76] -> [SKIP][77] ([i915#5235]) +2 similar issues
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-iclb7/igt@kms_plane_scaling@[email protected]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb2/igt@kms_plane_scaling@[email protected]

* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [PASS][78] -> [SKIP][79] ([fdo#109441])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb8/igt@kms_psr@psr2_cursor_mmap_cpu.html

#### Possible fixes ####

* igt@gem_ctx_exec@basic-close-race:
- shard-iclb: [INCOMPLETE][80] -> [PASS][81]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-iclb6/igt@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb3/igt@[email protected]

* igt@gem_exec_balancer@parallel-balancer:
- shard-iclb: [SKIP][82] ([i915#4525]) -> [PASS][83] +1 similar issue
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-iclb3/igt@[email protected]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb4/igt@[email protected]

* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-apl: [FAIL][84] ([i915#2842]) -> [PASS][85]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-apl8/igt@gem_exec_fair@[email protected]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-apl1/igt@gem_exec_fair@[email protected]

* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [FAIL][86] ([i915#2842]) -> [PASS][87] +1 similar issue
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-glk2/igt@gem_exec_fair@[email protected]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-glk7/igt@gem_exec_fair@[email protected]

* igt@gem_exec_reloc@basic-write-gtt:
- {shard-rkl}: [SKIP][88] ([i915#3281]) -> [PASS][89] +1 similar issue
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-rkl-6/igt@[email protected]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-rkl-5/igt@[email protected]

* igt@gem_partial_pwrite_pread@writes-after-reads:
- {shard-rkl}: [SKIP][90] ([i915#3282]) -> [PASS][91]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-rkl-6/igt@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-rkl-5/igt@[email protected]

* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: [SKIP][92] ([fdo#109441]) -> [PASS][93] +1 similar issue
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-iclb7/igt@kms_psr@psr2_cursor_plane_move.html
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html

* igt@perf@gen8-unprivileged-single-ctx-counters:
- {shard-rkl}: [SKIP][94] ([i915#2436]) -> [PASS][95]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-rkl-6/igt@[email protected]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-rkl-5/igt@[email protected]

* igt@perf@polling-parameterized:
- shard-glk: [FAIL][96] ([i915#5639]) -> [PASS][97]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-glk1/igt@[email protected]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-glk6/igt@[email protected]

#### Warnings ####

* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-iclb: [SKIP][98] ([i915#588]) -> [SKIP][99] ([i915#658])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-iclb2/igt@[email protected]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb5/igt@[email protected]

* igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-fully-sf:
- shard-iclb: [SKIP][100] ([i915#2920]) -> [SKIP][101] ([i915#658])
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-iclb2/igt@[email protected]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb5/igt@[email protected]

* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area:
- shard-iclb: [SKIP][102] ([i915#2920]) -> [SKIP][103] ([fdo#111068] / [i915#658])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-iclb2/igt@[email protected]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb8/igt@[email protected]

* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area:
- shard-iclb: [SKIP][104] ([fdo#111068] / [i915#658]) -> [SKIP][105] ([i915#2920]) +1 similar issue
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-iclb5/igt@[email protected]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb2/igt@[email protected]

* igt@kms_psr2_su@page_flip-nv12:
- shard-iclb: [FAIL][106] ([i915#5939]) -> [SKIP][107] ([fdo#109642] / [fdo#111068] / [i915#658])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12123/shard-iclb2/igt@kms_psr2_su@page_flip-nv12.html
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/shard-iclb5/igt@kms_psr2_su@page_flip-nv12.html

{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).

Build changes
-------------

* Linux: CI_DRM_12123 -> Patchwork_108432v1

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108432v1/index.html