* [PATCH] drm/dp_mst: Tune down the WARN modesetting a port with full_pbn=0
@ 2021-02-16 12:34 ` Imre Deak
0 siblings, 0 replies; 8+ messages in thread
From: Imre Deak @ 2021-02-16 12:34 UTC (permalink / raw)
To: dri-devel; +Cc: intel-gfx
It's possible to modeset a connector/mst port that has a 0 full_pbn
value: if the sink on the port deasserts its HPD and a branch device
reports this via a CSN with the port's ddps=0 and pdt!=NONE the driver
clears full_pbn, but the corresponding connector can be still
modesetted.
This happened on a DELL U2719D monitor as the branch device and an LG
27UL650-W daisy-chained to it, the LG monitor generating a long HPD
pulse (doing this for some reason always when waking up from some power
saving state).
Tune down the WARN about this scenario to a debug message.
References: https://gitlab.freedesktop.org/drm/intel/-/issues/1917
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Imre Deak <imre.deak@intel.com>
---
drivers/gpu/drm/drm_dp_mst_topology.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c b/drivers/gpu/drm/drm_dp_mst_topology.c
index 0a54506c27738..dcaf4bf9b62f6 100644
--- a/drivers/gpu/drm/drm_dp_mst_topology.c
+++ b/drivers/gpu/drm/drm_dp_mst_topology.c
@@ -5118,11 +5118,15 @@ drm_dp_mst_atomic_check_port_bw_limit(struct drm_dp_mst_port *port,
if (!found)
return 0;
- /* This should never happen, as it means we tried to
- * set a mode before querying the full_pbn
+ /*
+ * This could happen if the sink deasserted its HPD line, but
+ * the branch device still reports it as attached (PDT != NONE).
*/
- if (WARN_ON(!port->full_pbn))
+ if (!port->full_pbn) {
+ drm_dbg_kms(port->mgr->dev, "[MSTB:%p] [MST PORT:%p] no BW available for the port\n",
+ port->parent, port);
return -EINVAL;
+ }
pbn_used = vcpi->pbn;
} else {
--
2.25.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [Intel-gfx] [PATCH] drm/dp_mst: Tune down the WARN modesetting a port with full_pbn=0
@ 2021-02-16 12:34 ` Imre Deak
0 siblings, 0 replies; 8+ messages in thread
From: Imre Deak @ 2021-02-16 12:34 UTC (permalink / raw)
To: dri-devel; +Cc: intel-gfx
It's possible to modeset a connector/mst port that has a 0 full_pbn
value: if the sink on the port deasserts its HPD and a branch device
reports this via a CSN with the port's ddps=0 and pdt!=NONE the driver
clears full_pbn, but the corresponding connector can be still
modesetted.
This happened on a DELL U2719D monitor as the branch device and an LG
27UL650-W daisy-chained to it, the LG monitor generating a long HPD
pulse (doing this for some reason always when waking up from some power
saving state).
Tune down the WARN about this scenario to a debug message.
References: https://gitlab.freedesktop.org/drm/intel/-/issues/1917
Cc: Lyude Paul <lyude@redhat.com>
Signed-off-by: Imre Deak <imre.deak@intel.com>
---
drivers/gpu/drm/drm_dp_mst_topology.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c b/drivers/gpu/drm/drm_dp_mst_topology.c
index 0a54506c27738..dcaf4bf9b62f6 100644
--- a/drivers/gpu/drm/drm_dp_mst_topology.c
+++ b/drivers/gpu/drm/drm_dp_mst_topology.c
@@ -5118,11 +5118,15 @@ drm_dp_mst_atomic_check_port_bw_limit(struct drm_dp_mst_port *port,
if (!found)
return 0;
- /* This should never happen, as it means we tried to
- * set a mode before querying the full_pbn
+ /*
+ * This could happen if the sink deasserted its HPD line, but
+ * the branch device still reports it as attached (PDT != NONE).
*/
- if (WARN_ON(!port->full_pbn))
+ if (!port->full_pbn) {
+ drm_dbg_kms(port->mgr->dev, "[MSTB:%p] [MST PORT:%p] no BW available for the port\n",
+ port->parent, port);
return -EINVAL;
+ }
pbn_used = vcpi->pbn;
} else {
--
2.25.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/dp_mst: Tune down the WARN modesetting a port with full_pbn=0
2021-02-16 12:34 ` [Intel-gfx] " Imre Deak
(?)
@ 2021-02-16 16:01 ` Patchwork
-1 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2021-02-16 16:01 UTC (permalink / raw)
To: Imre Deak; +Cc: intel-gfx
[-- Attachment #1.1: Type: text/plain, Size: 2141 bytes --]
== Series Details ==
Series: drm/dp_mst: Tune down the WARN modesetting a port with full_pbn=0
URL : https://patchwork.freedesktop.org/series/87123/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9779 -> Patchwork_19685
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/index.html
Known issues
------------
Here are the changes found in Patchwork_19685 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_hangman@error-state-basic:
- 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_9779/fi-tgl-y/igt@i915_hangman@error-state-basic.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/fi-tgl-y/igt@i915_hangman@error-state-basic.html
#### Possible fixes ####
* igt@prime_vgem@basic-fence-flip:
- fi-tgl-y: [DMESG-WARN][3] ([i915#402]) -> [PASS][4] +2 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/fi-tgl-y/igt@prime_vgem@basic-fence-flip.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/fi-tgl-y/igt@prime_vgem@basic-fence-flip.html
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
Participating hosts (45 -> 40)
------------------------------
Missing (5): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_9779 -> Patchwork_19685
CI-20190529: 20190529
CI_DRM_9779: 775dbe8d5e041442fcadf63894468a63582a87a2 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6004: fe9ac2aeffc1828c6d61763a611a44fbd450aa96 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_19685: a84885e21626c39afbc7ae68e907c370ca6b163b @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
a84885e21626 drm/dp_mst: Tune down the WARN modesetting a port with full_pbn=0
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/index.html
[-- Attachment #1.2: Type: text/html, Size: 2827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Intel-gfx] ✓ Fi.CI.IGT: success for drm/dp_mst: Tune down the WARN modesetting a port with full_pbn=0
2021-02-16 12:34 ` [Intel-gfx] " Imre Deak
(?)
(?)
@ 2021-02-16 17:46 ` Patchwork
-1 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2021-02-16 17:46 UTC (permalink / raw)
To: Imre Deak; +Cc: intel-gfx
[-- Attachment #1.1: Type: text/plain, Size: 30288 bytes --]
== Series Details ==
Series: drm/dp_mst: Tune down the WARN modesetting a port with full_pbn=0
URL : https://patchwork.freedesktop.org/series/87123/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9779_full -> Patchwork_19685_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_19685_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@feature_discovery@psr2:
- shard-iclb: [PASS][1] -> [SKIP][2] ([i915#658])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb2/igt@feature_discovery@psr2.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb3/igt@feature_discovery@psr2.html
* igt@gem_ctx_persistence@legacy-engines-mixed-process:
- shard-snb: NOTRUN -> [SKIP][3] ([fdo#109271] / [i915#1099]) +2 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-snb5/igt@gem_ctx_persistence@legacy-engines-mixed-process.html
* igt@gem_eio@in-flight-10ms:
- shard-iclb: [PASS][4] -> [TIMEOUT][5] ([i915#1037] / [i915#2502])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb2/igt@gem_eio@in-flight-10ms.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb3/igt@gem_eio@in-flight-10ms.html
* igt@gem_eio@unwedge-stress:
- shard-tglb: [PASS][6] -> [TIMEOUT][7] ([i915#1037] / [i915#3063])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-tglb1/igt@gem_eio@unwedge-stress.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-tglb3/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: NOTRUN -> [FAIL][8] ([i915#2846])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl6/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [PASS][9] -> [FAIL][10] ([i915#2842])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-tglb1/igt@gem_exec_fair@basic-flow@rcs0.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-tglb1/igt@gem_exec_fair@basic-flow@rcs0.html
* igt@gem_exec_fair@basic-none-vip@rcs0:
- shard-kbl: [PASS][11] -> [FAIL][12] ([i915#2842])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-kbl7/igt@gem_exec_fair@basic-none-vip@rcs0.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl7/igt@gem_exec_fair@basic-none-vip@rcs0.html
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-glk: [PASS][13] -> [FAIL][14] ([i915#2842]) +1 similar issue
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-glk5/igt@gem_exec_fair@basic-throttle@rcs0.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-glk5/igt@gem_exec_fair@basic-throttle@rcs0.html
* igt@gem_exec_reloc@basic-many-active@vcs0:
- shard-kbl: NOTRUN -> [FAIL][15] ([i915#2389]) +4 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl1/igt@gem_exec_reloc@basic-many-active@vcs0.html
* igt@gem_exec_reloc@basic-parallel:
- shard-apl: NOTRUN -> [TIMEOUT][16] ([i915#1729])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl7/igt@gem_exec_reloc@basic-parallel.html
* igt@gem_exec_schedule@u-fairslice@vcs1:
- shard-iclb: [PASS][17] -> [DMESG-WARN][18] ([i915#2803])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb4/igt@gem_exec_schedule@u-fairslice@vcs1.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb4/igt@gem_exec_schedule@u-fairslice@vcs1.html
* igt@gem_exec_schedule@u-semaphore-codependency:
- shard-glk: [PASS][19] -> [DMESG-WARN][20] ([i915#1610])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-glk9/igt@gem_exec_schedule@u-semaphore-codependency.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-glk1/igt@gem_exec_schedule@u-semaphore-codependency.html
- shard-skl: [PASS][21] -> [DMESG-WARN][22] ([i915#409])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl5/igt@gem_exec_schedule@u-semaphore-codependency.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl6/igt@gem_exec_schedule@u-semaphore-codependency.html
* igt@gem_exec_suspend@basic-s3:
- shard-skl: [PASS][23] -> [INCOMPLETE][24] ([i915#198])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl2/igt@gem_exec_suspend@basic-s3.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl2/igt@gem_exec_suspend@basic-s3.html
* igt@gem_huc_copy@huc-copy:
- shard-kbl: NOTRUN -> [SKIP][25] ([fdo#109271] / [i915#2190])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl4/igt@gem_huc_copy@huc-copy.html
* igt@gem_pwrite@basic-exhaustion:
- shard-iclb: NOTRUN -> [WARN][26] ([i915#2658])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb3/igt@gem_pwrite@basic-exhaustion.html
- shard-apl: NOTRUN -> [WARN][27] ([i915#2658])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl6/igt@gem_pwrite@basic-exhaustion.html
* igt@gem_userptr_blits@input-checking:
- shard-snb: NOTRUN -> [DMESG-WARN][28] ([i915#3002])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-snb5/igt@gem_userptr_blits@input-checking.html
* igt@gem_userptr_blits@process-exit-mmap-busy@wc:
- shard-apl: NOTRUN -> [SKIP][29] ([fdo#109271] / [i915#1699]) +3 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl3/igt@gem_userptr_blits@process-exit-mmap-busy@wc.html
* igt@gen7_exec_parse@cmd-crossing-page:
- shard-tglb: NOTRUN -> [SKIP][30] ([fdo#109289])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-tglb1/igt@gen7_exec_parse@cmd-crossing-page.html
* igt@gen9_exec_parse@allowed-all:
- shard-skl: [PASS][31] -> [DMESG-WARN][32] ([i915#1436] / [i915#716])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl3/igt@gen9_exec_parse@allowed-all.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl3/igt@gen9_exec_parse@allowed-all.html
* igt@i915_pm_dc@dc6-dpms:
- shard-kbl: NOTRUN -> [FAIL][33] ([i915#454])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl4/igt@i915_pm_dc@dc6-dpms.html
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp:
- shard-kbl: NOTRUN -> [SKIP][34] ([fdo#109271] / [i915#1937])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl1/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-dp.html
* igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-hdmi-a:
- shard-glk: NOTRUN -> [SKIP][35] ([fdo#109271] / [i915#1937])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-glk7/igt@i915_pm_lpsp@kms-lpsp@kms-lpsp-hdmi-a.html
* igt@kms_async_flips@alternate-sync-async-flip:
- shard-skl: [PASS][36] -> [FAIL][37] ([i915#2521])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl1/igt@kms_async_flips@alternate-sync-async-flip.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl7/igt@kms_async_flips@alternate-sync-async-flip.html
* igt@kms_big_fb@x-tiled-16bpp-rotate-90:
- shard-tglb: NOTRUN -> [SKIP][38] ([fdo#111614])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-tglb1/igt@kms_big_fb@x-tiled-16bpp-rotate-90.html
* igt@kms_big_joiner@basic:
- shard-kbl: NOTRUN -> [SKIP][39] ([fdo#109271] / [i915#2705])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl6/igt@kms_big_joiner@basic.html
* igt@kms_big_joiner@invalid-modeset:
- shard-apl: NOTRUN -> [SKIP][40] ([fdo#109271] / [i915#2705])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl8/igt@kms_big_joiner@invalid-modeset.html
* igt@kms_chamelium@dp-hpd-storm-disable:
- shard-skl: NOTRUN -> [SKIP][41] ([fdo#109271] / [fdo#111827]) +3 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl9/igt@kms_chamelium@dp-hpd-storm-disable.html
* igt@kms_chamelium@hdmi-hpd-enable-disable-mode:
- shard-snb: NOTRUN -> [SKIP][42] ([fdo#109271] / [fdo#111827]) +11 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-snb5/igt@kms_chamelium@hdmi-hpd-enable-disable-mode.html
* igt@kms_chamelium@hdmi-hpd-storm:
- shard-kbl: NOTRUN -> [SKIP][43] ([fdo#109271] / [fdo#111827]) +18 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl1/igt@kms_chamelium@hdmi-hpd-storm.html
* igt@kms_chamelium@vga-hpd-enable-disable-mode:
- shard-glk: NOTRUN -> [SKIP][44] ([fdo#109271] / [fdo#111827]) +4 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-glk7/igt@kms_chamelium@vga-hpd-enable-disable-mode.html
* igt@kms_color_chamelium@pipe-c-ctm-0-25:
- shard-apl: NOTRUN -> [SKIP][45] ([fdo#109271] / [fdo#111827]) +17 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl1/igt@kms_color_chamelium@pipe-c-ctm-0-25.html
- shard-tglb: NOTRUN -> [SKIP][46] ([fdo#109284] / [fdo#111827]) +3 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-tglb1/igt@kms_color_chamelium@pipe-c-ctm-0-25.html
* igt@kms_content_protection@atomic-dpms:
- shard-kbl: NOTRUN -> [TIMEOUT][47] ([i915#1319]) +2 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl4/igt@kms_content_protection@atomic-dpms.html
* igt@kms_cursor_crc@pipe-a-cursor-512x170-sliding:
- shard-kbl: NOTRUN -> [SKIP][48] ([fdo#109271]) +167 similar issues
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl4/igt@kms_cursor_crc@pipe-a-cursor-512x170-sliding.html
* igt@kms_cursor_crc@pipe-c-cursor-64x21-offscreen:
- shard-skl: [PASS][49] -> [FAIL][50] ([i915#54]) +8 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl4/igt@kms_cursor_crc@pipe-c-cursor-64x21-offscreen.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl4/igt@kms_cursor_crc@pipe-c-cursor-64x21-offscreen.html
* igt@kms_cursor_crc@pipe-c-cursor-64x64-onscreen:
- shard-skl: NOTRUN -> [FAIL][51] ([i915#54])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl9/igt@kms_cursor_crc@pipe-c-cursor-64x64-onscreen.html
* igt@kms_cursor_legacy@pipe-d-single-bo:
- shard-kbl: NOTRUN -> [SKIP][52] ([fdo#109271] / [i915#533]) +2 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl6/igt@kms_cursor_legacy@pipe-d-single-bo.html
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-kbl: NOTRUN -> [INCOMPLETE][53] ([i915#155] / [i915#180] / [i915#636])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl4/igt@kms_fbcon_fbt@fbc-suspend.html
* igt@kms_flip@2x-flip-vs-rmfb-interruptible:
- shard-iclb: NOTRUN -> [SKIP][54] ([fdo#109274])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb3/igt@kms_flip@2x-flip-vs-rmfb-interruptible.html
* igt@kms_flip@plain-flip-ts-check@c-edp1:
- shard-skl: [PASS][55] -> [FAIL][56] ([i915#2122])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl1/igt@kms_flip@plain-flip-ts-check@c-edp1.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl2/igt@kms_flip@plain-flip-ts-check@c-edp1.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs:
- shard-kbl: NOTRUN -> [FAIL][57] ([i915#2641])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl4/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-64bpp-ytile:
- shard-kbl: NOTRUN -> [SKIP][58] ([fdo#109271] / [i915#2642])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl4/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-64bpp-ytile.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile:
- shard-apl: NOTRUN -> [SKIP][59] ([fdo#109271] / [i915#2642])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl6/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile:
- shard-apl: NOTRUN -> [FAIL][60] ([i915#2641])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl3/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile.html
* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-spr-indfb-draw-mmap-wc:
- shard-apl: NOTRUN -> [SKIP][61] ([fdo#109271]) +151 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl6/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-spr-indfb-draw-mmap-wc.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-indfb-msflip-blt:
- shard-iclb: NOTRUN -> [SKIP][62] ([fdo#109280])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb3/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-indfb-msflip-blt.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-shrfb-plflip-blt:
- shard-tglb: NOTRUN -> [SKIP][63] ([fdo#111825]) +2 similar issues
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-tglb1/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-shrfb-plflip-blt.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-spr-indfb-onoff:
- shard-skl: NOTRUN -> [SKIP][64] ([fdo#109271]) +40 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl9/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-spr-indfb-onoff.html
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-onoff:
- shard-snb: NOTRUN -> [SKIP][65] ([fdo#109271]) +206 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-snb5/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-onoff.html
* igt@kms_frontbuffer_tracking@psr-1p-rte:
- shard-skl: [PASS][66] -> [FAIL][67] ([i915#49])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl9/igt@kms_frontbuffer_tracking@psr-1p-rte.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl8/igt@kms_frontbuffer_tracking@psr-1p-rte.html
* igt@kms_frontbuffer_tracking@psr-2p-primscrn-spr-indfb-draw-mmap-wc:
- shard-glk: NOTRUN -> [SKIP][68] ([fdo#109271]) +25 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-glk7/igt@kms_frontbuffer_tracking@psr-2p-primscrn-spr-indfb-draw-mmap-wc.html
* igt@kms_hdr@bpc-switch-suspend:
- shard-kbl: [PASS][69] -> [DMESG-WARN][70] ([i915#180])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-kbl2/igt@kms_hdr@bpc-switch-suspend.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl2/igt@kms_hdr@bpc-switch-suspend.html
* igt@kms_hdr@static-swap:
- shard-tglb: NOTRUN -> [SKIP][71] ([i915#1187])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-tglb1/igt@kms_hdr@static-swap.html
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-d:
- shard-apl: NOTRUN -> [SKIP][72] ([fdo#109271] / [i915#533]) +1 similar issue
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl3/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-d.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-7efc:
- shard-skl: NOTRUN -> [FAIL][73] ([fdo#108145] / [i915#265])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl9/igt@kms_plane_alpha_blend@pipe-a-alpha-7efc.html
* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-skl: [PASS][74] -> [FAIL][75] ([fdo#108145] / [i915#265])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl9/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl8/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-7efc:
- shard-kbl: NOTRUN -> [FAIL][76] ([fdo#108145] / [i915#265]) +1 similar issue
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl4/igt@kms_plane_alpha_blend@pipe-c-alpha-7efc.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-basic:
- shard-apl: NOTRUN -> [FAIL][77] ([fdo#108145] / [i915#265]) +1 similar issue
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl7/igt@kms_plane_alpha_blend@pipe-c-alpha-basic.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb:
- shard-apl: NOTRUN -> [FAIL][78] ([i915#265])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl3/igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2:
- shard-apl: NOTRUN -> [SKIP][79] ([fdo#109271] / [i915#658]) +3 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl3/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-2.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3:
- shard-glk: NOTRUN -> [SKIP][80] ([fdo#109271] / [i915#658])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-glk7/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-3.html
* igt@kms_psr2_sf@plane-move-sf-dmg-area-1:
- shard-skl: NOTRUN -> [SKIP][81] ([fdo#109271] / [i915#658])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl9/igt@kms_psr2_sf@plane-move-sf-dmg-area-1.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5:
- shard-kbl: NOTRUN -> [SKIP][82] ([fdo#109271] / [i915#658]) +4 similar issues
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-5.html
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: [PASS][83] -> [SKIP][84] ([fdo#109441]) +2 similar issues
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb5/igt@kms_psr@psr2_no_drrs.html
* igt@kms_sysfs_edid_timing:
- shard-apl: NOTRUN -> [FAIL][85] ([IGT#2])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl8/igt@kms_sysfs_edid_timing.html
* igt@kms_vblank@pipe-a-accuracy-idle:
- shard-glk: [PASS][86] -> [FAIL][87] ([i915#43])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-glk5/igt@kms_vblank@pipe-a-accuracy-idle.html
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-glk9/igt@kms_vblank@pipe-a-accuracy-idle.html
* igt@kms_vblank@pipe-c-ts-continuation-suspend:
- shard-apl: [PASS][88] -> [DMESG-WARN][89] ([i915#180])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-apl7/igt@kms_vblank@pipe-c-ts-continuation-suspend.html
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl1/igt@kms_vblank@pipe-c-ts-continuation-suspend.html
* igt@kms_writeback@writeback-check-output:
- shard-apl: NOTRUN -> [SKIP][90] ([fdo#109271] / [i915#2437])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl7/igt@kms_writeback@writeback-check-output.html
* igt@kms_writeback@writeback-fb-id:
- shard-kbl: NOTRUN -> [SKIP][91] ([fdo#109271] / [i915#2437])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl4/igt@kms_writeback@writeback-fb-id.html
* igt@nouveau_crc@ctx-flip-threshold-reset-after-capture:
- shard-iclb: NOTRUN -> [SKIP][92] ([i915#2530])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb3/igt@nouveau_crc@ctx-flip-threshold-reset-after-capture.html
* igt@sysfs_clients@busy@rcs0:
- shard-glk: [PASS][93] -> [FAIL][94] ([i915#3019])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-glk8/igt@sysfs_clients@busy@rcs0.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-glk8/igt@sysfs_clients@busy@rcs0.html
* igt@sysfs_clients@sema-10@bcs0:
- shard-iclb: [PASS][95] -> [SKIP][96] ([i915#3026])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb8/igt@sysfs_clients@sema-10@bcs0.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb8/igt@sysfs_clients@sema-10@bcs0.html
* igt@sysfs_clients@sema-10@vcs0:
- shard-apl: NOTRUN -> [SKIP][97] ([fdo#109271] / [i915#3026]) +2 similar issues
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl8/igt@sysfs_clients@sema-10@vcs0.html
* igt@sysfs_clients@split-10@vcs0:
- shard-skl: NOTRUN -> [SKIP][98] ([fdo#109271] / [i915#3026]) +3 similar issues
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl9/igt@sysfs_clients@split-10@vcs0.html
* igt@sysfs_clients@split-25@rcs0:
- shard-skl: [PASS][99] -> [SKIP][100] ([fdo#109271]) +1 similar issue
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl5/igt@sysfs_clients@split-25@rcs0.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl10/igt@sysfs_clients@split-25@rcs0.html
#### Possible fixes ####
* igt@gem_exec_balancer@hang:
- shard-iclb: [INCOMPLETE][101] ([i915#1895] / [i915#2295]) -> [PASS][102]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb2/igt@gem_exec_balancer@hang.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb3/igt@gem_exec_balancer@hang.html
* igt@gem_exec_fair@basic-pace@bcs0:
- shard-tglb: [FAIL][103] ([i915#2842]) -> [PASS][104]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-tglb2/igt@gem_exec_fair@basic-pace@bcs0.html
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-tglb2/igt@gem_exec_fair@basic-pace@bcs0.html
* igt@gem_exec_reloc@basic-many-active@rcs0:
- shard-apl: [FAIL][105] ([i915#2389]) -> [PASS][106]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-apl3/igt@gem_exec_reloc@basic-many-active@rcs0.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl8/igt@gem_exec_reloc@basic-many-active@rcs0.html
* igt@gem_exec_schedule@u-fairslice@bcs0:
- shard-tglb: [DMESG-WARN][107] ([i915#2803]) -> [PASS][108]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-tglb8/igt@gem_exec_schedule@u-fairslice@bcs0.html
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-tglb1/igt@gem_exec_schedule@u-fairslice@bcs0.html
* igt@gem_exec_schedule@u-fairslice@vcs0:
- shard-iclb: [DMESG-WARN][109] ([i915#2803]) -> [PASS][110]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb4/igt@gem_exec_schedule@u-fairslice@vcs0.html
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb4/igt@gem_exec_schedule@u-fairslice@vcs0.html
* igt@gem_exec_schedule@u-fairslice@vecs0:
- shard-apl: [DMESG-WARN][111] ([i915#1610]) -> [PASS][112]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-apl7/igt@gem_exec_schedule@u-fairslice@vecs0.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-apl1/igt@gem_exec_schedule@u-fairslice@vecs0.html
* igt@gem_exec_whisper@basic-queues-forked-all:
- shard-glk: [DMESG-WARN][113] ([i915#118] / [i915#95]) -> [PASS][114] +1 similar issue
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-glk6/igt@gem_exec_whisper@basic-queues-forked-all.html
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-glk8/igt@gem_exec_whisper@basic-queues-forked-all.html
* igt@kms_cursor_crc@pipe-b-cursor-64x64-offscreen:
- shard-skl: [FAIL][115] ([i915#54]) -> [PASS][116] +8 similar issues
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl4/igt@kms_cursor_crc@pipe-b-cursor-64x64-offscreen.html
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl4/igt@kms_cursor_crc@pipe-b-cursor-64x64-offscreen.html
* igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
- shard-kbl: [DMESG-WARN][117] ([i915#180]) -> [PASS][118] +4 similar issues
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-kbl4/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-kbl1/igt@kms_flip@flip-vs-suspend-interruptible@a-dp1.html
* igt@kms_flip@plain-flip-fb-recreate-interruptible@b-edp1:
- shard-skl: [FAIL][119] ([i915#2122]) -> [PASS][120]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl6/igt@kms_flip@plain-flip-fb-recreate-interruptible@b-edp1.html
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl7/igt@kms_flip@plain-flip-fb-recreate-interruptible@b-edp1.html
* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-render:
- shard-skl: [DMESG-WARN][121] ([i915#1982]) -> [PASS][122]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl7/igt@kms_frontbuffer_tracking@psr-rgb101010-draw-render.html
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl3/igt@kms_frontbuffer_tracking@psr-rgb101010-draw-render.html
* igt@kms_hdr@bpc-switch:
- shard-skl: [FAIL][123] ([i915#1188]) -> [PASS][124]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl1/igt@kms_hdr@bpc-switch.html
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl2/igt@kms_hdr@bpc-switch.html
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [SKIP][125] ([fdo#109441]) -> [PASS][126] +3 similar issues
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb6/igt@kms_psr@psr2_cursor_mmap_cpu.html
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
* igt@perf@polling:
- shard-skl: [FAIL][127] ([i915#1542]) -> [PASS][128]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-skl8/igt@perf@polling.html
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-skl1/igt@perf@polling.html
* igt@perf@polling-parameterized:
- shard-glk: [FAIL][129] ([i915#1542]) -> [PASS][130]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-glk2/igt@perf@polling-parameterized.html
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-glk8/igt@perf@polling-parameterized.html
- shard-iclb: [FAIL][131] ([i915#1542]) -> [PASS][132]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb5/igt@perf@polling-parameterized.html
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb5/igt@perf@polling-parameterized.html
* igt@sysfs_clients@busy@vcs0:
- shard-iclb: [FAIL][133] ([i915#3019]) -> [PASS][134]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb8/igt@sysfs_clients@busy@vcs0.html
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb3/igt@sysfs_clients@busy@vcs0.html
* igt@sysfs_clients@recycle:
- shard-tglb: [FAIL][135] ([i915#3028]) -> [PASS][136]
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-tglb1/igt@sysfs_clients@recycle.html
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-tglb3/igt@sysfs_clients@recycle.html
* {igt@sysfs_clients@recycle-many}:
- shard-iclb: [FAIL][137] ([i915#3028]) -> [PASS][138]
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb5/igt@sysfs_clients@recycle-many.html
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb2/igt@sysfs_clients@recycle-many.html
#### Warnings ####
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [FAIL][139] ([i915#2849]) -> [FAIL][140] ([i915#2842])
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb1/igt@gem_exec_fair@basic-throttle@rcs0.html
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb2/igt@gem_exec_fair@basic-throttle@rcs0.html
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-iclb: [SKIP][141] ([i915#588]) -> [SKIP][142] ([i915#658])
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb2/igt@i915_pm_dc@dc3co-vpb-simulation.html
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb3/igt@i915_pm_dc@dc3co-vpb-simulation.html
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: [WARN][143] ([i915#2681] / [i915#2684]) -> [WARN][144] ([i915#1804] / [i915#2684])
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb1/igt@i915_pm_rc6_residency@rc6-idle.html
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/shard-iclb6/igt@i915_pm_rc6_residency@rc6-idle.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1:
- shard-iclb: [SKIP][145] ([i915#2920]) -> [SKIP][146] ([i915#658]) +3 similar issues
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_9779/shard-iclb2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1.html
[146]: https:/
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19685/index.html
[-- Attachment #1.2: Type: text/html, Size: 33595 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] drm/dp_mst: Tune down the WARN modesetting a port with full_pbn=0
2021-02-16 12:34 ` [Intel-gfx] " Imre Deak
@ 2021-02-17 18:07 ` Lyude Paul
-1 siblings, 0 replies; 8+ messages in thread
From: Lyude Paul @ 2021-02-17 18:07 UTC (permalink / raw)
To: Imre Deak, dri-devel; +Cc: intel-gfx
On Tue, 2021-02-16 at 14:34 +0200, Imre Deak wrote:
> It's possible to modeset a connector/mst port that has a 0 full_pbn
> value: if the sink on the port deasserts its HPD and a branch device
> reports this via a CSN with the port's ddps=0 and pdt!=NONE the driver
> clears full_pbn, but the corresponding connector can be still
> modesetted.
>
> This happened on a DELL U2719D monitor as the branch device and an LG
> 27UL650-W daisy-chained to it, the LG monitor generating a long HPD
> pulse (doing this for some reason always when waking up from some power
> saving state).
>
> Tune down the WARN about this scenario to a debug message.
>
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/1917
> Cc: Lyude Paul <lyude@redhat.com>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
> ---
> drivers/gpu/drm/drm_dp_mst_topology.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c
> b/drivers/gpu/drm/drm_dp_mst_topology.c
> index 0a54506c27738..dcaf4bf9b62f6 100644
> --- a/drivers/gpu/drm/drm_dp_mst_topology.c
> +++ b/drivers/gpu/drm/drm_dp_mst_topology.c
> @@ -5118,11 +5118,15 @@ drm_dp_mst_atomic_check_port_bw_limit(struct
> drm_dp_mst_port *port,
> if (!found)
> return 0;
>
> - /* This should never happen, as it means we tried to
> - * set a mode before querying the full_pbn
> + /*
> + * This could happen if the sink deasserted its HPD line, but
> + * the branch device still reports it as attached (PDT !=
> NONE).
> */
> - if (WARN_ON(!port->full_pbn))
> + if (!port->full_pbn) {
> + drm_dbg_kms(port->mgr->dev, "[MSTB:%p] [MST PORT:%p]
> no BW available for the port\n",
> + port->parent, port);
Shouldn't this use the atomic debugging level? With that fixed, this is:
Reviewed-by: Lyude Paul <lyude@redhat.com>
> return -EINVAL;
> + }
>
> pbn_used = vcpi->pbn;
> } else {
--
Sincerely,
Lyude Paul (she/her)
Software Engineer at Red Hat
Note: I deal with a lot of emails and have a lot of bugs on my plate. If you've
asked me a question, are waiting for a review/merge on a patch, etc. and I
haven't responded in a while, please feel free to send me another email to check
on my status. I don't bite!
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/dp_mst: Tune down the WARN modesetting a port with full_pbn=0
@ 2021-02-17 18:07 ` Lyude Paul
0 siblings, 0 replies; 8+ messages in thread
From: Lyude Paul @ 2021-02-17 18:07 UTC (permalink / raw)
To: Imre Deak, dri-devel; +Cc: intel-gfx
On Tue, 2021-02-16 at 14:34 +0200, Imre Deak wrote:
> It's possible to modeset a connector/mst port that has a 0 full_pbn
> value: if the sink on the port deasserts its HPD and a branch device
> reports this via a CSN with the port's ddps=0 and pdt!=NONE the driver
> clears full_pbn, but the corresponding connector can be still
> modesetted.
>
> This happened on a DELL U2719D monitor as the branch device and an LG
> 27UL650-W daisy-chained to it, the LG monitor generating a long HPD
> pulse (doing this for some reason always when waking up from some power
> saving state).
>
> Tune down the WARN about this scenario to a debug message.
>
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/1917
> Cc: Lyude Paul <lyude@redhat.com>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
> ---
> drivers/gpu/drm/drm_dp_mst_topology.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c
> b/drivers/gpu/drm/drm_dp_mst_topology.c
> index 0a54506c27738..dcaf4bf9b62f6 100644
> --- a/drivers/gpu/drm/drm_dp_mst_topology.c
> +++ b/drivers/gpu/drm/drm_dp_mst_topology.c
> @@ -5118,11 +5118,15 @@ drm_dp_mst_atomic_check_port_bw_limit(struct
> drm_dp_mst_port *port,
> if (!found)
> return 0;
>
> - /* This should never happen, as it means we tried to
> - * set a mode before querying the full_pbn
> + /*
> + * This could happen if the sink deasserted its HPD line, but
> + * the branch device still reports it as attached (PDT !=
> NONE).
> */
> - if (WARN_ON(!port->full_pbn))
> + if (!port->full_pbn) {
> + drm_dbg_kms(port->mgr->dev, "[MSTB:%p] [MST PORT:%p]
> no BW available for the port\n",
> + port->parent, port);
Shouldn't this use the atomic debugging level? With that fixed, this is:
Reviewed-by: Lyude Paul <lyude@redhat.com>
> return -EINVAL;
> + }
>
> pbn_used = vcpi->pbn;
> } else {
--
Sincerely,
Lyude Paul (she/her)
Software Engineer at Red Hat
Note: I deal with a lot of emails and have a lot of bugs on my plate. If you've
asked me a question, are waiting for a review/merge on a patch, etc. and I
haven't responded in a while, please feel free to send me another email to check
on my status. I don't bite!
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] drm/dp_mst: Tune down the WARN modesetting a port with full_pbn=0
2021-02-17 18:07 ` [Intel-gfx] " Lyude Paul
@ 2021-02-17 18:27 ` Imre Deak
-1 siblings, 0 replies; 8+ messages in thread
From: Imre Deak @ 2021-02-17 18:27 UTC (permalink / raw)
To: Lyude Paul; +Cc: intel-gfx, dri-devel
On Wed, Feb 17, 2021 at 01:07:11PM -0500, Lyude Paul wrote:
> On Tue, 2021-02-16 at 14:34 +0200, Imre Deak wrote:
> > It's possible to modeset a connector/mst port that has a 0 full_pbn
> > value: if the sink on the port deasserts its HPD and a branch device
> > reports this via a CSN with the port's ddps=0 and pdt!=NONE the driver
> > clears full_pbn, but the corresponding connector can be still
> > modesetted.
> >
> > This happened on a DELL U2719D monitor as the branch device and an LG
> > 27UL650-W daisy-chained to it, the LG monitor generating a long HPD
> > pulse (doing this for some reason always when waking up from some power
> > saving state).
> >
> > Tune down the WARN about this scenario to a debug message.
> >
> > References: https://gitlab.freedesktop.org/drm/intel/-/issues/1917
> > Cc: Lyude Paul <lyude@redhat.com>
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > ---
> > drivers/gpu/drm/drm_dp_mst_topology.c | 10 +++++++---
> > 1 file changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c
> > b/drivers/gpu/drm/drm_dp_mst_topology.c
> > index 0a54506c27738..dcaf4bf9b62f6 100644
> > --- a/drivers/gpu/drm/drm_dp_mst_topology.c
> > +++ b/drivers/gpu/drm/drm_dp_mst_topology.c
> > @@ -5118,11 +5118,15 @@ drm_dp_mst_atomic_check_port_bw_limit(struct
> > drm_dp_mst_port *port,
> > if (!found)
> > return 0;
> >
> > - /* This should never happen, as it means we tried to
> > - * set a mode before querying the full_pbn
> > + /*
> > + * This could happen if the sink deasserted its HPD line, but
> > + * the branch device still reports it as attached (PDT != NONE).
> > */
> > - if (WARN_ON(!port->full_pbn))
> > + if (!port->full_pbn) {
> > + drm_dbg_kms(port->mgr->dev, "[MSTB:%p] [MST PORT:%p] no BW available for the port\n",
> > + port->parent, port);
>
> Shouldn't this use the atomic debugging level? With that fixed, this is:
>
> Reviewed-by: Lyude Paul <lyude@redhat.com>
Thanks, yes mixed up the debug level, will fix that.
> > return -EINVAL;
> > + }
> >
> > pbn_used = vcpi->pbn;
> > } else {
>
> --
> Sincerely,
> Lyude Paul (she/her)
> Software Engineer at Red Hat
>
> Note: I deal with a lot of emails and have a lot of bugs on my plate. If you've
> asked me a question, are waiting for a review/merge on a patch, etc. and I
> haven't responded in a while, please feel free to send me another email to check
> on my status. I don't bite!
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/dp_mst: Tune down the WARN modesetting a port with full_pbn=0
@ 2021-02-17 18:27 ` Imre Deak
0 siblings, 0 replies; 8+ messages in thread
From: Imre Deak @ 2021-02-17 18:27 UTC (permalink / raw)
To: Lyude Paul; +Cc: intel-gfx, dri-devel
On Wed, Feb 17, 2021 at 01:07:11PM -0500, Lyude Paul wrote:
> On Tue, 2021-02-16 at 14:34 +0200, Imre Deak wrote:
> > It's possible to modeset a connector/mst port that has a 0 full_pbn
> > value: if the sink on the port deasserts its HPD and a branch device
> > reports this via a CSN with the port's ddps=0 and pdt!=NONE the driver
> > clears full_pbn, but the corresponding connector can be still
> > modesetted.
> >
> > This happened on a DELL U2719D monitor as the branch device and an LG
> > 27UL650-W daisy-chained to it, the LG monitor generating a long HPD
> > pulse (doing this for some reason always when waking up from some power
> > saving state).
> >
> > Tune down the WARN about this scenario to a debug message.
> >
> > References: https://gitlab.freedesktop.org/drm/intel/-/issues/1917
> > Cc: Lyude Paul <lyude@redhat.com>
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > ---
> > drivers/gpu/drm/drm_dp_mst_topology.c | 10 +++++++---
> > 1 file changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_dp_mst_topology.c
> > b/drivers/gpu/drm/drm_dp_mst_topology.c
> > index 0a54506c27738..dcaf4bf9b62f6 100644
> > --- a/drivers/gpu/drm/drm_dp_mst_topology.c
> > +++ b/drivers/gpu/drm/drm_dp_mst_topology.c
> > @@ -5118,11 +5118,15 @@ drm_dp_mst_atomic_check_port_bw_limit(struct
> > drm_dp_mst_port *port,
> > if (!found)
> > return 0;
> >
> > - /* This should never happen, as it means we tried to
> > - * set a mode before querying the full_pbn
> > + /*
> > + * This could happen if the sink deasserted its HPD line, but
> > + * the branch device still reports it as attached (PDT != NONE).
> > */
> > - if (WARN_ON(!port->full_pbn))
> > + if (!port->full_pbn) {
> > + drm_dbg_kms(port->mgr->dev, "[MSTB:%p] [MST PORT:%p] no BW available for the port\n",
> > + port->parent, port);
>
> Shouldn't this use the atomic debugging level? With that fixed, this is:
>
> Reviewed-by: Lyude Paul <lyude@redhat.com>
Thanks, yes mixed up the debug level, will fix that.
> > return -EINVAL;
> > + }
> >
> > pbn_used = vcpi->pbn;
> > } else {
>
> --
> Sincerely,
> Lyude Paul (she/her)
> Software Engineer at Red Hat
>
> Note: I deal with a lot of emails and have a lot of bugs on my plate. If you've
> asked me a question, are waiting for a review/merge on a patch, etc. and I
> haven't responded in a while, please feel free to send me another email to check
> on my status. I don't bite!
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2021-02-17 18:28 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-02-16 12:34 [PATCH] drm/dp_mst: Tune down the WARN modesetting a port with full_pbn=0 Imre Deak
2021-02-16 12:34 ` [Intel-gfx] " Imre Deak
2021-02-16 16:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-02-16 17:46 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-02-17 18:07 ` [PATCH] " Lyude Paul
2021-02-17 18:07 ` [Intel-gfx] " Lyude Paul
2021-02-17 18:27 ` Imre Deak
2021-02-17 18:27 ` [Intel-gfx] " Imre Deak
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.