* [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect
@ 2022-12-14 18:42 Imre Deak
2022-12-14 18:42 ` [Intel-gfx] [PATCH 2/3] drm/display/dp_mst: Fix down message handling after a packet reception error Imre Deak
` (4 more replies)
0 siblings, 5 replies; 10+ messages in thread
From: Imre Deak @ 2022-12-14 18:42 UTC (permalink / raw)
To: intel-gfx; +Cc: stable, dri-devel
If the sink gets disconnected during receiving a multi-packet DP MST AUX
down-reply/up-request sideband message, the state keeping track of which
packets have been received already is not reset. This results in a failed
sanity check for the subsequent message packet received after a sink is
reconnected (due to the pending message not yet completed with an
end-of-message-transfer packet), indicated by the
"sideband msg set header failed"
error.
Fix the above by resetting the up/down message reception state after a
disconnect event.
Cc: Lyude Paul <lyude@redhat.com>
Cc: <stable@vger.kernel.org> # v3.17+
Signed-off-by: Imre Deak <imre.deak@intel.com>
---
drivers/gpu/drm/display/drm_dp_mst_topology.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
index 51a46689cda70..90819fff2c9ba 100644
--- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
+++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
@@ -3641,6 +3641,9 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
drm_dp_dpcd_writeb(mgr->aux, DP_MSTM_CTRL, 0);
ret = 0;
mgr->payload_id_table_cleared = false;
+
+ memset(&mgr->down_rep_recv, 0, sizeof(mgr->down_rep_recv));
+ memset(&mgr->up_req_recv, 0, sizeof(mgr->up_req_recv));
}
out_unlock:
--
2.37.1
^ permalink raw reply related [flat|nested] 10+ messages in thread
* [Intel-gfx] [PATCH 2/3] drm/display/dp_mst: Fix down message handling after a packet reception error
2022-12-14 18:42 [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect Imre Deak
@ 2022-12-14 18:42 ` Imre Deak
2022-12-14 18:42 ` [Intel-gfx] [PATCH 3/3] drm/display/dp_mst: Fix payload addition on a disconnected sink Imre Deak
` (3 subsequent siblings)
4 siblings, 0 replies; 10+ messages in thread
From: Imre Deak @ 2022-12-14 18:42 UTC (permalink / raw)
To: intel-gfx; +Cc: stable, dri-devel
After an error during receiving a packet for a multi-packet DP MST
sideband message, the state tracking which packets have been received
already is not reset. This prevents the reception of subsequent down
messages (due to the pending message not yet completed with an
end-of-message-transfer packet).
Fix the above by resetting the reception state after a packet error.
Cc: Lyude Paul <lyude@redhat.com>
Cc: <stable@vger.kernel.org> # v3.17+
Signed-off-by: Imre Deak <imre.deak@intel.com>
---
drivers/gpu/drm/display/drm_dp_mst_topology.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
index 90819fff2c9ba..01350510244f2 100644
--- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
+++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
@@ -3856,7 +3856,7 @@ static int drm_dp_mst_handle_down_rep(struct drm_dp_mst_topology_mgr *mgr)
struct drm_dp_sideband_msg_rx *msg = &mgr->down_rep_recv;
if (!drm_dp_get_one_sb_msg(mgr, false, &mstb))
- goto out;
+ goto out_clear_reply;
/* Multi-packet message transmission, don't clear the reply */
if (!msg->have_eomt)
--
2.37.1
^ permalink raw reply related [flat|nested] 10+ messages in thread
* [Intel-gfx] [PATCH 3/3] drm/display/dp_mst: Fix payload addition on a disconnected sink
2022-12-14 18:42 [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect Imre Deak
2022-12-14 18:42 ` [Intel-gfx] [PATCH 2/3] drm/display/dp_mst: Fix down message handling after a packet reception error Imre Deak
@ 2022-12-14 18:42 ` Imre Deak
2022-12-14 20:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect Patchwork
` (2 subsequent siblings)
4 siblings, 0 replies; 10+ messages in thread
From: Imre Deak @ 2022-12-14 18:42 UTC (permalink / raw)
To: intel-gfx; +Cc: stable, dri-devel
If an MST stream is enabled on a disconnected sink, the payload for the
stream is not created and the MST manager's payload count/next start VC
slot is not updated. Since the payload's start VC slot may still contain
a valid value (!= -1) the subsequent disabling of such a stream could
cause an incorrect decrease of the payload count/next start VC slot in
drm_dp_remove_payload() and hence later payload additions will fail.
Fix the above by marking the payload as invalid in the above case, so
that it's skipped during payload removal. While at it add a debug print
for this case.
Cc: Lyude Paul <lyude@redhat.com>
Cc: <stable@vger.kernel.org> # v6.1+
Signed-off-by: Imre Deak <imre.deak@intel.com>
---
drivers/gpu/drm/display/drm_dp_mst_topology.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
index 01350510244f2..5861b0a6247bc 100644
--- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
+++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
@@ -3309,8 +3309,13 @@ int drm_dp_add_payload_part1(struct drm_dp_mst_topology_mgr *mgr,
int ret;
port = drm_dp_mst_topology_get_port_validated(mgr, payload->port);
- if (!port)
+ if (!port) {
+ drm_dbg_kms(mgr->dev,
+ "VCPI %d for port %p not in topology, not creating a payload\n",
+ payload->vcpi, payload->port);
+ payload->vc_start_slot = -1;
return 0;
+ }
if (mgr->payload_count == 0)
mgr->next_start_slot = mst_state->start_slot;
--
2.37.1
^ permalink raw reply related [flat|nested] 10+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect
2022-12-14 18:42 [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect Imre Deak
2022-12-14 18:42 ` [Intel-gfx] [PATCH 2/3] drm/display/dp_mst: Fix down message handling after a packet reception error Imre Deak
2022-12-14 18:42 ` [Intel-gfx] [PATCH 3/3] drm/display/dp_mst: Fix payload addition on a disconnected sink Imre Deak
@ 2022-12-14 20:54 ` Patchwork
2022-12-14 21:41 ` [Intel-gfx] [PATCH 1/3] " Lyude Paul
2022-12-16 8:06 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/3] " Patchwork
4 siblings, 0 replies; 10+ messages in thread
From: Patchwork @ 2022-12-14 20:54 UTC (permalink / raw)
To: Imre Deak; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 5502 bytes --]
== Series Details ==
Series: series starting with [1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect
URL : https://patchwork.freedesktop.org/series/111943/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12506 -> Patchwork_111943v1
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/index.html
Participating hosts (40 -> 40)
------------------------------
No changes in participating hosts
Known issues
------------
Here are the changes found in Patchwork_111943v1 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_gttfill@basic:
- fi-pnv-d510: [PASS][1] -> [FAIL][2] ([i915#7229])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/fi-pnv-d510/igt@gem_exec_gttfill@basic.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/fi-pnv-d510/igt@gem_exec_gttfill@basic.html
* igt@i915_selftest@live@execlists:
- fi-bsw-kefka: [PASS][3] -> [INCOMPLETE][4] ([i915#2940] / [i915#6734])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/fi-bsw-kefka/igt@i915_selftest@live@execlists.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/fi-bsw-kefka/igt@i915_selftest@live@execlists.html
* igt@i915_selftest@live@gt_heartbeat:
- fi-kbl-soraka: [PASS][5] -> [DMESG-FAIL][6] ([i915#5334])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/fi-kbl-soraka/igt@i915_selftest@live@gt_heartbeat.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/fi-kbl-soraka/igt@i915_selftest@live@gt_heartbeat.html
* igt@i915_selftest@live@hangcheck:
- fi-hsw-4770: [PASS][7] -> [INCOMPLETE][8] ([i915#4785])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-rkl-guc: NOTRUN -> [SKIP][9] ([fdo#111827])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/fi-rkl-guc/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_setmode@basic-clone-single-crtc:
- fi-snb-2600: NOTRUN -> [SKIP][10] ([fdo#109271])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/fi-snb-2600/igt@kms_setmode@basic-clone-single-crtc.html
* igt@runner@aborted:
- fi-hsw-4770: NOTRUN -> [FAIL][11] ([fdo#109271] / [i915#4312] / [i915#5594])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/fi-hsw-4770/igt@runner@aborted.html
- fi-bsw-kefka: NOTRUN -> [FAIL][12] ([fdo#109271] / [i915#4312])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/fi-bsw-kefka/igt@runner@aborted.html
#### Possible fixes ####
* igt@i915_selftest@live@migrate:
- bat-adlp-4: [DMESG-FAIL][13] ([i915#7699]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/bat-adlp-4/igt@i915_selftest@live@migrate.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/bat-adlp-4/igt@i915_selftest@live@migrate.html
* igt@i915_selftest@live@workarounds:
- fi-rkl-guc: [INCOMPLETE][15] ([i915#4983]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/fi-rkl-guc/igt@i915_selftest@live@workarounds.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/fi-rkl-guc/igt@i915_selftest@live@workarounds.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#2940]: https://gitlab.freedesktop.org/drm/intel/issues/2940
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4785]: https://gitlab.freedesktop.org/drm/intel/issues/4785
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
[i915#5594]: https://gitlab.freedesktop.org/drm/intel/issues/5594
[i915#6471]: https://gitlab.freedesktop.org/drm/intel/issues/6471
[i915#6734]: https://gitlab.freedesktop.org/drm/intel/issues/6734
[i915#7229]: https://gitlab.freedesktop.org/drm/intel/issues/7229
[i915#7554]: https://gitlab.freedesktop.org/drm/intel/issues/7554
[i915#7699]: https://gitlab.freedesktop.org/drm/intel/issues/7699
Build changes
-------------
* Linux: CI_DRM_12506 -> Patchwork_111943v1
CI-20190529: 20190529
CI_DRM_12506: d58c07107cf979eebf3538b0b1b0539b345c66a1 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7094: 1763071e9d50c5e992257c9197cb26f166de6fae @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_111943v1: d58c07107cf979eebf3538b0b1b0539b345c66a1 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
9a2d5ca9a4fa drm/display/dp_mst: Fix payload addition on a disconnected sink
2b8f5b546d38 drm/display/dp_mst: Fix down message handling after a packet reception error
ebc1f5c45728 drm/display/dp_mst: Fix down/up message handling after sink disconnect
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/index.html
[-- Attachment #2: Type: text/html, Size: 6423 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect
2022-12-14 18:42 [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect Imre Deak
` (2 preceding siblings ...)
2022-12-14 20:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect Patchwork
@ 2022-12-14 21:41 ` Lyude Paul
2022-12-16 15:10 ` Imre Deak
2022-12-16 8:06 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/3] " Patchwork
4 siblings, 1 reply; 10+ messages in thread
From: Lyude Paul @ 2022-12-14 21:41 UTC (permalink / raw)
To: Imre Deak, intel-gfx; +Cc: stable, dri-devel
For the whole series:
Reviewed-by: Lyude Paul <lyude@redhat.com>
Thanks!
On Wed, 2022-12-14 at 20:42 +0200, Imre Deak wrote:
> If the sink gets disconnected during receiving a multi-packet DP MST AUX
> down-reply/up-request sideband message, the state keeping track of which
> packets have been received already is not reset. This results in a failed
> sanity check for the subsequent message packet received after a sink is
> reconnected (due to the pending message not yet completed with an
> end-of-message-transfer packet), indicated by the
>
> "sideband msg set header failed"
>
> error.
>
> Fix the above by resetting the up/down message reception state after a
> disconnect event.
>
> Cc: Lyude Paul <lyude@redhat.com>
> Cc: <stable@vger.kernel.org> # v3.17+
> Signed-off-by: Imre Deak <imre.deak@intel.com>
> ---
> drivers/gpu/drm/display/drm_dp_mst_topology.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
> index 51a46689cda70..90819fff2c9ba 100644
> --- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
> +++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
> @@ -3641,6 +3641,9 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
> drm_dp_dpcd_writeb(mgr->aux, DP_MSTM_CTRL, 0);
> ret = 0;
> mgr->payload_id_table_cleared = false;
> +
> + memset(&mgr->down_rep_recv, 0, sizeof(mgr->down_rep_recv));
> + memset(&mgr->up_req_recv, 0, sizeof(mgr->up_req_recv));
> }
>
> out_unlock:
--
Cheers,
Lyude Paul (she/her)
Software Engineer at Red Hat
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect
2022-12-14 18:42 [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect Imre Deak
` (3 preceding siblings ...)
2022-12-14 21:41 ` [Intel-gfx] [PATCH 1/3] " Lyude Paul
@ 2022-12-16 8:06 ` Patchwork
4 siblings, 0 replies; 10+ messages in thread
From: Patchwork @ 2022-12-16 8:06 UTC (permalink / raw)
To: Imre Deak; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 39702 bytes --]
== Series Details ==
Series: series starting with [1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect
URL : https://patchwork.freedesktop.org/series/111943/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12506_full -> Patchwork_111943v1_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (14 -> 14)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_111943v1_full:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@i915_selftest@live@sanitycheck:
- {shard-rkl}: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-rkl-5/igt@i915_selftest@live@sanitycheck.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-rkl-5/igt@i915_selftest@live@sanitycheck.html
* igt@kms_cursor_crc@cursor-onscreen-512x512:
- {shard-rkl}: [SKIP][3] ([i915#4098]) -> [SKIP][4] +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-rkl-5/igt@kms_cursor_crc@cursor-onscreen-512x512.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-rkl-5/igt@kms_cursor_crc@cursor-onscreen-512x512.html
Known issues
------------
Here are the changes found in Patchwork_111943v1_full that come from known issues:
### CI changes ###
#### Possible fixes ####
* boot:
- shard-snb: ([PASS][5], [PASS][6], [PASS][7], [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], [PASS][13], [PASS][14], [PASS][15], [PASS][16], [FAIL][17], [PASS][18], [PASS][19], [PASS][20], [PASS][21], [PASS][22], [PASS][23], [PASS][24], [PASS][25], [PASS][26], [PASS][27], [PASS][28], [PASS][29]) ([i915#4338]) -> ([PASS][30], [PASS][31], [PASS][32], [PASS][33], [PASS][34], [PASS][35], [PASS][36], [PASS][37], [PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], [PASS][43], [PASS][44], [PASS][45], [PASS][46], [PASS][47], [PASS][48], [PASS][49], [PASS][50], [PASS][51], [PASS][52], [PASS][53], [PASS][54])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb7/boot.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb7/boot.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb7/boot.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb7/boot.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb7/boot.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb7/boot.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb7/boot.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb7/boot.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb5/boot.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb5/boot.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb5/boot.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb5/boot.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb5/boot.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb5/boot.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb5/boot.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb5/boot.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb5/boot.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb4/boot.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb4/boot.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb4/boot.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb4/boot.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb4/boot.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb4/boot.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb4/boot.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-snb4/boot.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb7/boot.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb7/boot.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb7/boot.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb7/boot.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb7/boot.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb7/boot.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb7/boot.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb5/boot.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb5/boot.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb5/boot.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb5/boot.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb5/boot.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb5/boot.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb5/boot.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb5/boot.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb5/boot.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb4/boot.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb4/boot.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb4/boot.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb4/boot.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb4/boot.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb4/boot.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb4/boot.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb4/boot.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb4/boot.html
### IGT changes ###
#### Issues hit ####
* igt@gem_eio@unwedge-stress:
- shard-snb: NOTRUN -> [FAIL][55] ([i915#3354])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb4/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_balancer@parallel-keep-in-fence:
- shard-iclb: [PASS][56] -> [SKIP][57] ([i915#4525]) +2 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-iclb2/igt@gem_exec_balancer@parallel-keep-in-fence.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-iclb3/igt@gem_exec_balancer@parallel-keep-in-fence.html
* 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_12506/shard-tglb1/igt@gem_exec_fair@basic-pace-share@rcs0.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-tglb6/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-iclb: [PASS][60] -> [FAIL][61] ([i915#2842])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-iclb1/igt@gem_exec_fair@basic-pace-solo@rcs0.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-iclb6/igt@gem_exec_fair@basic-pace-solo@rcs0.html
* igt@gen9_exec_parse@allowed-single:
- shard-glk: [PASS][62] -> [DMESG-WARN][63] ([i915#5566] / [i915#716])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-glk1/igt@gen9_exec_parse@allowed-single.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-glk1/igt@gen9_exec_parse@allowed-single.html
* igt@i915_pm_dc@dc9-dpms:
- shard-iclb: [PASS][64] -> [SKIP][65] ([i915#4281])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-iclb6/igt@i915_pm_dc@dc9-dpms.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-iclb3/igt@i915_pm_dc@dc9-dpms.html
* igt@kms_addfb_basic@addfb25-yf-tiled-legacy:
- shard-skl: [PASS][66] -> [DMESG-WARN][67] ([i915#1982])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-skl6/igt@kms_addfb_basic@addfb25-yf-tiled-legacy.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl4/igt@kms_addfb_basic@addfb25-yf-tiled-legacy.html
* igt@kms_async_flips@alternate-sync-async-flip@pipe-b-edp-1:
- shard-skl: [PASS][68] -> [FAIL][69] ([i915#2521]) +1 similar issue
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-skl6/igt@kms_async_flips@alternate-sync-async-flip@pipe-b-edp-1.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl1/igt@kms_async_flips@alternate-sync-async-flip@pipe-b-edp-1.html
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip-async-flip:
- shard-tglb: [PASS][70] -> [FAIL][71] ([i915#3743])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-tglb7/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip-async-flip.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-tglb2/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip-async-flip.html
* igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][72] ([fdo#109271] / [i915#3886]) +1 similar issue
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl7/igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_gen12_rc_ccs_cc:
- shard-glk: NOTRUN -> [SKIP][73] ([fdo#109271] / [i915#3886])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-glk5/igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-d-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc:
- shard-apl: NOTRUN -> [SKIP][74] ([fdo#109271]) +4 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-apl3/igt@kms_ccs@pipe-d-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-d-random-ccs-data-4_tiled_dg2_mc_ccs:
- shard-glk: NOTRUN -> [SKIP][75] ([fdo#109271]) +8 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-glk5/igt@kms_ccs@pipe-d-random-ccs-data-4_tiled_dg2_mc_ccs.html
* igt@kms_chamelium@common-hpd-after-suspend:
- shard-snb: NOTRUN -> [SKIP][76] ([fdo#109271] / [fdo#111827]) +3 similar issues
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb4/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_chamelium@hdmi-crc-nonplanar-formats:
- shard-skl: NOTRUN -> [SKIP][77] ([fdo#109271] / [fdo#111827])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl7/igt@kms_chamelium@hdmi-crc-nonplanar-formats.html
* igt@kms_cursor_legacy@cursor-vs-flip@atomic-transitions-varying-size:
- shard-skl: NOTRUN -> [INCOMPLETE][78] ([i915#7096])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl7/igt@kms_cursor_legacy@cursor-vs-flip@atomic-transitions-varying-size.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1:
- shard-skl: [PASS][79] -> [FAIL][80] ([i915#79])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-skl4/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl7/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1.html
* igt@kms_flip@flip-vs-expired-vblank@c-edp1:
- shard-skl: [PASS][81] -> [FAIL][82] ([i915#2122]) +1 similar issue
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-skl1/igt@kms_flip@flip-vs-expired-vblank@c-edp1.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl4/igt@kms_flip@flip-vs-expired-vblank@c-edp1.html
* igt@kms_flip@flip-vs-suspend-interruptible@b-edp1:
- shard-skl: [PASS][83] -> [INCOMPLETE][84] ([i915#4839])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-skl1/igt@kms_flip@flip-vs-suspend-interruptible@b-edp1.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl7/igt@kms_flip@flip-vs-suspend-interruptible@b-edp1.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-valid-mode:
- shard-iclb: NOTRUN -> [SKIP][85] ([i915#2672]) +3 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-iclb6/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-valid-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-downscaling@pipe-a-valid-mode:
- shard-iclb: NOTRUN -> [SKIP][86] ([i915#2587] / [i915#2672]) +3 similar issues
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-iclb5/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-16bpp-4tile-downscaling@pipe-a-valid-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs-downscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][87] ([i915#2672] / [i915#3555]) +1 similar issue
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs-downscaling@pipe-a-default-mode.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-indfb-draw-mmap-wc:
- shard-skl: NOTRUN -> [SKIP][88] ([fdo#109271]) +34 similar issues
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl7/igt@kms_frontbuffer_tracking@fbcpsr-1p-offscren-pri-indfb-draw-mmap-wc.html
* igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation@pipe-a-vga-1:
- shard-snb: NOTRUN -> [SKIP][89] ([fdo#109271]) +70 similar issues
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-snb4/igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-rotation@pipe-a-vga-1.html
* igt@kms_plane_scaling@planes-downscale-factor-0-5@pipe-a-edp-1:
- shard-iclb: [PASS][90] -> [SKIP][91] ([i915#5235]) +2 similar issues
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-iclb8/igt@kms_plane_scaling@planes-downscale-factor-0-5@pipe-a-edp-1.html
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-iclb2/igt@kms_plane_scaling@planes-downscale-factor-0-5@pipe-a-edp-1.html
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: [PASS][92] -> [SKIP][93] ([fdo#109441]) +4 similar issues
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-iclb3/igt@kms_psr@psr2_cursor_plane_move.html
* igt@sysfs_clients@sema-50:
- shard-skl: NOTRUN -> [SKIP][94] ([fdo#109271] / [i915#2994])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl7/igt@sysfs_clients@sema-50.html
* igt@sysfs_heartbeat_interval@mixed@vecs0:
- shard-skl: [PASS][95] -> [FAIL][96] ([i915#1731])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-skl6/igt@sysfs_heartbeat_interval@mixed@vecs0.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl6/igt@sysfs_heartbeat_interval@mixed@vecs0.html
#### Possible fixes ####
* igt@gem_ctx_exec@basic-nohangcheck:
- {shard-rkl}: [FAIL][97] ([i915#6268]) -> [PASS][98]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-rkl-6/igt@gem_ctx_exec@basic-nohangcheck.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-rkl-4/igt@gem_ctx_exec@basic-nohangcheck.html
- {shard-tglu}: [FAIL][99] ([i915#6268]) -> [PASS][100]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-tglu-5/igt@gem_ctx_exec@basic-nohangcheck.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-tglu-4/igt@gem_ctx_exec@basic-nohangcheck.html
* igt@gem_ctx_isolation@nonpriv-switch@bcs0:
- {shard-rkl}: [FAIL][101] ([i915#7673]) -> [PASS][102] +4 similar issues
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-rkl-6/igt@gem_ctx_isolation@nonpriv-switch@bcs0.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-rkl-5/igt@gem_ctx_isolation@nonpriv-switch@bcs0.html
* igt@gem_exec_balancer@parallel-keep-submit-fence:
- shard-iclb: [SKIP][103] ([i915#4525]) -> [PASS][104] +2 similar issues
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-iclb8/igt@gem_exec_balancer@parallel-keep-submit-fence.html
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-iclb2/igt@gem_exec_balancer@parallel-keep-submit-fence.html
* igt@gem_exec_endless@dispatch@bcs0:
- {shard-rkl}: [SKIP][105] ([i915#6247]) -> [PASS][106]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-rkl-5/igt@gem_exec_endless@dispatch@bcs0.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-rkl-1/igt@gem_exec_endless@dispatch@bcs0.html
* igt@gem_exec_fair@basic-deadline:
- {shard-rkl}: [FAIL][107] ([i915#2846]) -> [PASS][108]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-rkl-2/igt@gem_exec_fair@basic-deadline.html
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-rkl-3/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none@rcs0:
- shard-tglb: [FAIL][109] ([i915#2842]) -> [PASS][110]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-tglb2/igt@gem_exec_fair@basic-none@rcs0.html
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-tglb6/igt@gem_exec_fair@basic-none@rcs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [FAIL][111] ([i915#2842]) -> [PASS][112] +2 similar issues
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-glk2/igt@gem_exec_fair@basic-pace-share@rcs0.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-glk9/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_reloc@basic-wc-cpu:
- {shard-rkl}: [SKIP][113] ([i915#3281]) -> [PASS][114] +6 similar issues
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-rkl-2/igt@gem_exec_reloc@basic-wc-cpu.html
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-rkl-5/igt@gem_exec_reloc@basic-wc-cpu.html
* igt@gem_lmem_swapping@parallel-multi@lmem0:
- {shard-dg1}: [DMESG-WARN][115] -> [PASS][116] +2 similar issues
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-dg1-16/igt@gem_lmem_swapping@parallel-multi@lmem0.html
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-dg1-13/igt@gem_lmem_swapping@parallel-multi@lmem0.html
* igt@gem_pread@snoop:
- {shard-rkl}: [SKIP][117] ([i915#3282]) -> [PASS][118] +3 similar issues
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-rkl-6/igt@gem_pread@snoop.html
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-rkl-5/igt@gem_pread@snoop.html
* igt@gen9_exec_parse@allowed-single:
- shard-apl: [DMESG-WARN][119] ([i915#5566] / [i915#716]) -> [PASS][120]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-apl8/igt@gen9_exec_parse@allowed-single.html
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-apl3/igt@gen9_exec_parse@allowed-single.html
* igt@gen9_exec_parse@shadow-peek:
- {shard-rkl}: [SKIP][121] ([i915#2527]) -> [PASS][122] +1 similar issue
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-rkl-2/igt@gen9_exec_parse@shadow-peek.html
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-rkl-5/igt@gen9_exec_parse@shadow-peek.html
* igt@i915_pm_rc6_residency@rc6-idle@rcs0:
- {shard-dg1}: [FAIL][123] ([i915#3591]) -> [PASS][124]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-dg1-19/igt@i915_pm_rc6_residency@rc6-idle@rcs0.html
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-dg1-15/igt@i915_pm_rc6_residency@rc6-idle@rcs0.html
* igt@i915_pm_rpm@dpms-mode-unset-lpsp:
- {shard-rkl}: [SKIP][125] ([i915#1397]) -> [PASS][126]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-rkl-3/igt@i915_pm_rpm@dpms-mode-unset-lpsp.html
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-rkl-6/igt@i915_pm_rpm@dpms-mode-unset-lpsp.html
* igt@i915_pm_rpm@modeset-non-lpsp-stress-no-wait:
- {shard-dg1}: [SKIP][127] ([i915#1397]) -> [PASS][128]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-dg1-14/igt@i915_pm_rpm@modeset-non-lpsp-stress-no-wait.html
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-dg1-16/igt@i915_pm_rpm@modeset-non-lpsp-stress-no-wait.html
* igt@i915_selftest@live@execlists:
- shard-skl: [INCOMPLETE][129] -> [PASS][130]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-skl4/igt@i915_selftest@live@execlists.html
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl1/igt@i915_selftest@live@execlists.html
* igt@i915_selftest@live@hangcheck:
- shard-tglb: [DMESG-WARN][131] ([i915#5591]) -> [PASS][132]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-tglb5/igt@i915_selftest@live@hangcheck.html
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-tglb2/igt@i915_selftest@live@hangcheck.html
* igt@i915_suspend@basic-s2idle-without-i915:
- {shard-dg1}: [DMESG-WARN][133] ([i915#4391]) -> [PASS][134] +1 similar issue
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-dg1-16/igt@i915_suspend@basic-s2idle-without-i915.html
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-dg1-13/igt@i915_suspend@basic-s2idle-without-i915.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1:
- shard-skl: [FAIL][135] ([i915#79]) -> [PASS][136] +1 similar issue
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-skl4/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1.html
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl7/igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1.html
* igt@kms_flip@plain-flip-fb-recreate-interruptible@b-edp1:
- shard-skl: [FAIL][137] ([i915#2122]) -> [PASS][138]
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-skl6/igt@kms_flip@plain-flip-fb-recreate-interruptible@b-edp1.html
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-skl6/igt@kms_flip@plain-flip-fb-recreate-interruptible@b-edp1.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move:
- {shard-rkl}: [SKIP][139] ([i915#1849] / [i915#4098]) -> [PASS][140] +4 similar issues
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-rkl-1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move.html
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-rkl-6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move.html
* igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-b-edp-1:
- shard-iclb: [SKIP][141] ([i915#5235]) -> [PASS][142] +2 similar issues
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-iclb2/igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-b-edp-1.html
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-iclb6/igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-b-edp-1.html
* igt@kms_psr@cursor_blt:
- {shard-rkl}: [SKIP][143] ([i915#1072]) -> [PASS][144]
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-rkl-1/igt@kms_psr@cursor_blt.html
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-rkl-6/igt@kms_psr@cursor_blt.html
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [SKIP][145] ([fdo#109441]) -> [PASS][146] +1 similar issue
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-iclb1/igt@kms_psr@psr2_cursor_mmap_cpu.html
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
* igt@kms_psr_stress_test@invalidate-primary-flip-overlay:
- shard-tglb: [SKIP][147] ([i915#5519]) -> [PASS][148]
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-tglb7/igt@kms_psr_stress_test@invalidate-primary-flip-overlay.html
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-tglb2/igt@kms_psr_stress_test@invalidate-primary-flip-overlay.html
* igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend:
- {shard-rkl}: [SKIP][149] ([i915#1845] / [i915#4098]) -> [PASS][150] +2 similar issues
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-rkl-1/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-rkl-6/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html
* igt@perf@stress-open-close:
- shard-glk: [INCOMPLETE][151] ([i915#5213]) -> [PASS][152]
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-glk8/igt@perf@stress-open-close.html
[152]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-glk4/igt@perf@stress-open-close.html
#### Warnings ####
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-tglb: [SKIP][153] ([i915#2848]) -> [FAIL][154] ([i915#2842])
[153]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-tglb6/igt@gem_exec_fair@basic-none-share@rcs0.html
[154]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-tglb7/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@kms_psr2_sf@cursor-plane-move-continuous-exceed-sf:
- shard-iclb: [SKIP][155] ([i915#2920]) -> [SKIP][156] ([i915#658])
[155]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-iclb2/igt@kms_psr2_sf@cursor-plane-move-continuous-exceed-sf.html
[156]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-iclb6/igt@kms_psr2_sf@cursor-plane-move-continuous-exceed-sf.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area:
- shard-iclb: [SKIP][157] ([fdo#111068] / [i915#658]) -> [SKIP][158] ([i915#2920]) +1 similar issue
[157]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-iclb8/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area.html
[158]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-iclb2/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area.html
* igt@runner@aborted:
- shard-apl: ([FAIL][159], [FAIL][160], [FAIL][161]) ([fdo#109271] / [i915#3002] / [i915#4312]) -> ([FAIL][162], [FAIL][163]) ([i915#3002] / [i915#4312])
[159]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-apl8/igt@runner@aborted.html
[160]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-apl3/igt@runner@aborted.html
[161]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12506/shard-apl2/igt@runner@aborted.html
[162]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-apl2/igt@runner@aborted.html
[163]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/shard-apl6/igt@runner@aborted.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109279]: https://bugs.freedesktop.org/show_bug.cgi?id=109279
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109283]: https://bugs.freedesktop.org/show_bug.cgi?id=109283
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#109302]: https://bugs.freedesktop.org/show_bug.cgi?id=109302
[fdo#109309]: https://bugs.freedesktop.org/show_bug.cgi?id=109309
[fdo#109312]: https://bugs.freedesktop.org/show_bug.cgi?id=109312
[fdo#109313]: https://bugs.freedesktop.org/show_bug.cgi?id=109313
[fdo#109314]: https://bugs.freedesktop.org/show_bug.cgi?id=109314
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109506]: https://bugs.freedesktop.org/show_bug.cgi?id=109506
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#110542]: https://bugs.freedesktop.org/show_bug.cgi?id=110542
[fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615
[fdo#111644]: https://bugs.freedesktop.org/show_bug.cgi?id=111644
[fdo#111656]: https://bugs.freedesktop.org/show_bug.cgi?id=111656
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[fdo#112054]: https://bugs.freedesktop.org/show_bug.cgi?id=112054
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#132]: https://gitlab.freedesktop.org/drm/intel/issues/132
[i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397
[i915#1731]: https://gitlab.freedesktop.org/drm/intel/issues/1731
[i915#1769]: https://gitlab.freedesktop.org/drm/intel/issues/1769
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#1839]: https://gitlab.freedesktop.org/drm/intel/issues/1839
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#1849]: https://gitlab.freedesktop.org/drm/intel/issues/1849
[i915#1850]: https://gitlab.freedesktop.org/drm/intel/issues/1850
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437
[i915#2521]: https://gitlab.freedesktop.org/drm/intel/issues/2521
[i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527
[i915#2532]: https://gitlab.freedesktop.org/drm/intel/issues/2532
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587
[i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#2705]: https://gitlab.freedesktop.org/drm/intel/issues/2705
[i915#280]: https://gitlab.freedesktop.org/drm/intel/issues/280
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2846]: https://gitlab.freedesktop.org/drm/intel/issues/2846
[i915#2848]: https://gitlab.freedesktop.org/drm/intel/issues/2848
[i915#2856]: https://gitlab.freedesktop.org/drm/intel/issues/2856
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[i915#3002]: https://gitlab.freedesktop.org/drm/intel/issues/3002
[i915#3116]: https://gitlab.freedesktop.org/drm/intel/issues/3116
[i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297
[i915#3299]: https://gitlab.freedesktop.org/drm/intel/issues/3299
[i915#3323]: https://gitlab.freedesktop.org/drm/intel/issues/3323
[i915#3354]: https://gitlab.freedesktop.org/drm/intel/issues/3354
[i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359
[i915#3469]: https://gitlab.freedesktop.org/drm/intel/issues/3469
[i915#3528]: https://gitlab.freedesktop.org/drm/intel/issues/3528
[i915#3546]: https://gitlab.freedesktop.org/drm/intel/issues/3546
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3558]: https://gitlab.freedesktop.org/drm/intel/issues/3558
[i915#3591]: https://gitlab.freedesktop.org/drm/intel/issues/3591
[i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3734]: https://gitlab.freedesktop.org/drm/intel/issues/3734
[i915#3742]: https://gitlab.freedesktop.org/drm/intel/issues/3742
[i915#3743]: https://gitlab.freedesktop.org/drm/intel/issues/3743
[i915#3804]: https://gitlab.freedesktop.org/drm/intel/issues/3804
[i915#3825]: https://gitlab.freedesktop.org/drm/intel/issues/3825
[i915#3826]: https://gitlab.freedesktop.org/drm/intel/issues/3826
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#3955]: https://gitlab.freedesktop.org/drm/intel/issues/3955
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078
[i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#426]: https://gitlab.freedesktop.org/drm/intel/issues/426
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#4275]: https://gitlab.freedesktop.org/drm/intel/issues/4275
[i915#4281]: https://gitlab.freedesktop.org/drm/intel/issues/4281
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4338]: https://gitlab.freedesktop.org/drm/intel/issues/4338
[i915#4391]: https://gitlab.freedesktop.org/drm/intel/issues/4391
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4767]: https://gitlab.freedesktop.org/drm/intel/issues/4767
[i915#4778]: https://gitlab.freedesktop.org/drm/intel/issues/4778
[i915#4839]: https://gitlab.freedesktop.org/drm/intel/issues/4839
[i915#4991]: https://gitlab.freedesktop.org/drm/intel/issues/4991
[i915#5174]: https://gitlab.freedesktop.org/drm/intel/issues/5174
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5213]: https://gitlab.freedesktop.org/drm/intel/issues/5213
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#5288]: https://gitlab.freedesktop.org/drm/intel/issues/5288
[i915#5289]: https://gitlab.freedesktop.org/drm/intel/issues/5289
[i915#5325]: https://gitlab.freedesktop.org/drm/intel/issues/5325
[i915#5327]: https://gitlab.freedesktop.org/drm/intel/issues/5327
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5439]: https://gitlab.freedesktop.org/drm/intel/issues/5439
[i915#5519]: https://gitlab.freedesktop.org/drm/intel/issues/5519
[i915#5566]: https://gitlab.freedesktop.org/drm/intel/issues/5566
[i915#5591]: https://gitlab.freedesktop.org/drm/intel/issues/5591
[i915#5608]: https://gitlab.freedesktop.org/drm/intel/issues/5608
[i915#5723]: https://gitlab.freedesktop.org/drm/intel/issues/5723
[i915#5775]: https://gitlab.freedesktop.org/drm/intel/issues/5775
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#6117]: https://gitlab.freedesktop.org/drm/intel/issues/6117
[i915#6230]: https://gitlab.freedesktop.org/drm/intel/issues/6230
[i915#6245]: https://gitlab.freedesktop.org/drm/intel/issues/6245
[i915#6247]: https://gitlab.freedesktop.org/drm/intel/issues/6247
[i915#6248]: https://gitlab.freedesktop.org/drm/intel/issues/6248
[i915#6252]: https://gitlab.freedesktop.org/drm/intel/issues/6252
[i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268
[i915#6335]: https://gitlab.freedesktop.org/drm/intel/issues/6335
[i915#6412]: https://gitlab.freedesktop.org/drm/intel/issues/6412
[i915#6497]: https://gitlab.freedesktop.org/drm/intel/issues/6497
[i915#6524]: https://gitlab.freedesktop.org/drm/intel/issues/6524
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#6768]: https://gitlab.freedesktop.org/drm/intel/issues/6768
[i915#6944]: https://gitlab.freedesktop.org/drm/intel/issues/6944
[i915#6953]: https://gitlab.freedesktop.org/drm/intel/issues/6953
[i915#7052]: https://gitlab.freedesktop.org/drm/intel/issues/7052
[i915#7096]: https://gitlab.freedesktop.org/drm/intel/issues/7096
[i915#7116]: https://gitlab.freedesktop.org/drm/intel/issues/7116
[i915#7118]: https://gitlab.freedesktop.org/drm/intel/issues/7118
[i915#7128]: https://gitlab.freedesktop.org/drm/intel/issues/7128
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#7397]: https://gitlab.freedesktop.org/drm/intel/issues/7397
[i915#7443]: https://gitlab.freedesktop.org/drm/intel/issues/7443
[i915#7456]: https://gitlab.freedesktop.org/drm/intel/issues/7456
[i915#7561]: https://gitlab.freedesktop.org/drm/intel/issues/7561
[i915#7651]: https://gitlab.freedesktop.org/drm/intel/issues/7651
[i915#7673]: https://gitlab.freedesktop.org/drm/intel/issues/7673
[i915#7681]: https://gitlab.freedesktop.org/drm/intel/issues/7681
[i915#7688]: https://gitlab.freedesktop.org/drm/intel/issues/7688
[i915#7697]: https://gitlab.freedesktop.org/drm/intel/issues/7697
[i915#7701]: https://gitlab.freedesktop.org/drm/intel/issues/7701
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
Build changes
-------------
* Linux: CI_DRM_12506 -> Patchwork_111943v1
CI-20190529: 20190529
CI_DRM_12506: d58c07107cf979eebf3538b0b1b0539b345c66a1 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7094: 1763071e9d50c5e992257c9197cb26f166de6fae @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_111943v1: d58c07107cf979eebf3538b0b1b0539b345c66a1 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111943v1/index.html
[-- Attachment #2: Type: text/html, Size: 37138 bytes --]
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect
2022-12-14 21:41 ` [Intel-gfx] [PATCH 1/3] " Lyude Paul
@ 2022-12-16 15:10 ` Imre Deak
2022-12-16 16:10 ` Jani Nikula
0 siblings, 1 reply; 10+ messages in thread
From: Imre Deak @ 2022-12-16 15:10 UTC (permalink / raw)
To: Lyude Paul; +Cc: intel-gfx, stable, dri-devel
On Wed, Dec 14, 2022 at 04:41:42PM -0500, Lyude Paul wrote:
> For the whole series:
>
> Reviewed-by: Lyude Paul <lyude@redhat.com>
Thanks for the review, pushed it to drm-misc-next.
> Thanks!
>
> On Wed, 2022-12-14 at 20:42 +0200, Imre Deak wrote:
> > If the sink gets disconnected during receiving a multi-packet DP MST AUX
> > down-reply/up-request sideband message, the state keeping track of which
> > packets have been received already is not reset. This results in a failed
> > sanity check for the subsequent message packet received after a sink is
> > reconnected (due to the pending message not yet completed with an
> > end-of-message-transfer packet), indicated by the
> >
> > "sideband msg set header failed"
> >
> > error.
> >
> > Fix the above by resetting the up/down message reception state after a
> > disconnect event.
> >
> > Cc: Lyude Paul <lyude@redhat.com>
> > Cc: <stable@vger.kernel.org> # v3.17+
> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> > ---
> > drivers/gpu/drm/display/drm_dp_mst_topology.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
> > index 51a46689cda70..90819fff2c9ba 100644
> > --- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
> > +++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
> > @@ -3641,6 +3641,9 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
> > drm_dp_dpcd_writeb(mgr->aux, DP_MSTM_CTRL, 0);
> > ret = 0;
> > mgr->payload_id_table_cleared = false;
> > +
> > + memset(&mgr->down_rep_recv, 0, sizeof(mgr->down_rep_recv));
> > + memset(&mgr->up_req_recv, 0, sizeof(mgr->up_req_recv));
> > }
> >
> > out_unlock:
>
> --
> Cheers,
> Lyude Paul (she/her)
> Software Engineer at Red Hat
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect
2022-12-16 15:10 ` Imre Deak
@ 2022-12-16 16:10 ` Jani Nikula
2022-12-16 16:33 ` Imre Deak
0 siblings, 1 reply; 10+ messages in thread
From: Jani Nikula @ 2022-12-16 16:10 UTC (permalink / raw)
To: imre.deak, Lyude Paul; +Cc: intel-gfx, dri-devel, stable
On Fri, 16 Dec 2022, Imre Deak <imre.deak@intel.com> wrote:
> On Wed, Dec 14, 2022 at 04:41:42PM -0500, Lyude Paul wrote:
>> For the whole series:
>>
>> Reviewed-by: Lyude Paul <lyude@redhat.com>
>
> Thanks for the review, pushed it to drm-misc-next.
Hmm, with the drm-misc *not* cherry-picking patches from drm-misc-next
to drm-misc-fixes, these will only get backported to stable kernels
after they hit Linus' tree in the next (as opposed to current) merge
window after a full development cycle. Wonder if they should be
expedited.
BR,
Jani.
>
>> Thanks!
>>
>> On Wed, 2022-12-14 at 20:42 +0200, Imre Deak wrote:
>> > If the sink gets disconnected during receiving a multi-packet DP MST AUX
>> > down-reply/up-request sideband message, the state keeping track of which
>> > packets have been received already is not reset. This results in a failed
>> > sanity check for the subsequent message packet received after a sink is
>> > reconnected (due to the pending message not yet completed with an
>> > end-of-message-transfer packet), indicated by the
>> >
>> > "sideband msg set header failed"
>> >
>> > error.
>> >
>> > Fix the above by resetting the up/down message reception state after a
>> > disconnect event.
>> >
>> > Cc: Lyude Paul <lyude@redhat.com>
>> > Cc: <stable@vger.kernel.org> # v3.17+
>> > Signed-off-by: Imre Deak <imre.deak@intel.com>
>> > ---
>> > drivers/gpu/drm/display/drm_dp_mst_topology.c | 3 +++
>> > 1 file changed, 3 insertions(+)
>> >
>> > diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> > index 51a46689cda70..90819fff2c9ba 100644
>> > --- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> > +++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> > @@ -3641,6 +3641,9 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
>> > drm_dp_dpcd_writeb(mgr->aux, DP_MSTM_CTRL, 0);
>> > ret = 0;
>> > mgr->payload_id_table_cleared = false;
>> > +
>> > + memset(&mgr->down_rep_recv, 0, sizeof(mgr->down_rep_recv));
>> > + memset(&mgr->up_req_recv, 0, sizeof(mgr->up_req_recv));
>> > }
>> >
>> > out_unlock:
>>
>> --
>> Cheers,
>> Lyude Paul (she/her)
>> Software Engineer at Red Hat
>>
--
Jani Nikula, Intel Open Source Graphics Center
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect
2022-12-16 16:10 ` Jani Nikula
@ 2022-12-16 16:33 ` Imre Deak
2022-12-16 16:49 ` Jani Nikula
0 siblings, 1 reply; 10+ messages in thread
From: Imre Deak @ 2022-12-16 16:33 UTC (permalink / raw)
To: Jani Nikula; +Cc: intel-gfx, dri-devel, stable
On Fri, Dec 16, 2022 at 06:10:39PM +0200, Jani Nikula wrote:
> On Fri, 16 Dec 2022, Imre Deak <imre.deak@intel.com> wrote:
> > On Wed, Dec 14, 2022 at 04:41:42PM -0500, Lyude Paul wrote:
> >> For the whole series:
> >>
> >> Reviewed-by: Lyude Paul <lyude@redhat.com>
> >
> > Thanks for the review, pushed it to drm-misc-next.
>
> Hmm, with the drm-misc *not* cherry-picking patches from drm-misc-next
> to drm-misc-fixes, these will only get backported to stable kernels
> after they hit Linus' tree in the next (as opposed to current) merge
> window after a full development cycle. Wonder if they should be
> expedited.
Ok, it should've been pushed to -fixes then, will do that next time.
Yes, I think sending them already before the next merge window would be
good.
>
> BR,
> Jani.
>
> >
> >> Thanks!
> >>
> >> On Wed, 2022-12-14 at 20:42 +0200, Imre Deak wrote:
> >> > If the sink gets disconnected during receiving a multi-packet DP MST AUX
> >> > down-reply/up-request sideband message, the state keeping track of which
> >> > packets have been received already is not reset. This results in a failed
> >> > sanity check for the subsequent message packet received after a sink is
> >> > reconnected (due to the pending message not yet completed with an
> >> > end-of-message-transfer packet), indicated by the
> >> >
> >> > "sideband msg set header failed"
> >> >
> >> > error.
> >> >
> >> > Fix the above by resetting the up/down message reception state after a
> >> > disconnect event.
> >> >
> >> > Cc: Lyude Paul <lyude@redhat.com>
> >> > Cc: <stable@vger.kernel.org> # v3.17+
> >> > Signed-off-by: Imre Deak <imre.deak@intel.com>
> >> > ---
> >> > drivers/gpu/drm/display/drm_dp_mst_topology.c | 3 +++
> >> > 1 file changed, 3 insertions(+)
> >> >
> >> > diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
> >> > index 51a46689cda70..90819fff2c9ba 100644
> >> > --- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
> >> > +++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
> >> > @@ -3641,6 +3641,9 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
> >> > drm_dp_dpcd_writeb(mgr->aux, DP_MSTM_CTRL, 0);
> >> > ret = 0;
> >> > mgr->payload_id_table_cleared = false;
> >> > +
> >> > + memset(&mgr->down_rep_recv, 0, sizeof(mgr->down_rep_recv));
> >> > + memset(&mgr->up_req_recv, 0, sizeof(mgr->up_req_recv));
> >> > }
> >> >
> >> > out_unlock:
> >>
> >> --
> >> Cheers,
> >> Lyude Paul (she/her)
> >> Software Engineer at Red Hat
> >>
>
> --
> Jani Nikula, Intel Open Source Graphics Center
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect
2022-12-16 16:33 ` Imre Deak
@ 2022-12-16 16:49 ` Jani Nikula
0 siblings, 0 replies; 10+ messages in thread
From: Jani Nikula @ 2022-12-16 16:49 UTC (permalink / raw)
To: imre.deak; +Cc: intel-gfx, Maxime Ripard, dri-devel, Thomas Zimmermann, stable
On Fri, 16 Dec 2022, Imre Deak <imre.deak@intel.com> wrote:
> On Fri, Dec 16, 2022 at 06:10:39PM +0200, Jani Nikula wrote:
>> On Fri, 16 Dec 2022, Imre Deak <imre.deak@intel.com> wrote:
>> > On Wed, Dec 14, 2022 at 04:41:42PM -0500, Lyude Paul wrote:
>> >> For the whole series:
>> >>
>> >> Reviewed-by: Lyude Paul <lyude@redhat.com>
>> >
>> > Thanks for the review, pushed it to drm-misc-next.
>>
>> Hmm, with the drm-misc *not* cherry-picking patches from drm-misc-next
>> to drm-misc-fixes, these will only get backported to stable kernels
>> after they hit Linus' tree in the next (as opposed to current) merge
>> window after a full development cycle. Wonder if they should be
>> expedited.
>
> Ok, it should've been pushed to -fixes then, will do that next time.
> Yes, I think sending them already before the next merge window would be
> good.
Cc: drm-misc maintainers, I think this is for you to figure out.
BR,
Jani.
>
>>
>> BR,
>> Jani.
>>
>> >
>> >> Thanks!
>> >>
>> >> On Wed, 2022-12-14 at 20:42 +0200, Imre Deak wrote:
>> >> > If the sink gets disconnected during receiving a multi-packet DP MST AUX
>> >> > down-reply/up-request sideband message, the state keeping track of which
>> >> > packets have been received already is not reset. This results in a failed
>> >> > sanity check for the subsequent message packet received after a sink is
>> >> > reconnected (due to the pending message not yet completed with an
>> >> > end-of-message-transfer packet), indicated by the
>> >> >
>> >> > "sideband msg set header failed"
>> >> >
>> >> > error.
>> >> >
>> >> > Fix the above by resetting the up/down message reception state after a
>> >> > disconnect event.
>> >> >
>> >> > Cc: Lyude Paul <lyude@redhat.com>
>> >> > Cc: <stable@vger.kernel.org> # v3.17+
>> >> > Signed-off-by: Imre Deak <imre.deak@intel.com>
>> >> > ---
>> >> > drivers/gpu/drm/display/drm_dp_mst_topology.c | 3 +++
>> >> > 1 file changed, 3 insertions(+)
>> >> >
>> >> > diff --git a/drivers/gpu/drm/display/drm_dp_mst_topology.c b/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> >> > index 51a46689cda70..90819fff2c9ba 100644
>> >> > --- a/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> >> > +++ b/drivers/gpu/drm/display/drm_dp_mst_topology.c
>> >> > @@ -3641,6 +3641,9 @@ int drm_dp_mst_topology_mgr_set_mst(struct drm_dp_mst_topology_mgr *mgr, bool ms
>> >> > drm_dp_dpcd_writeb(mgr->aux, DP_MSTM_CTRL, 0);
>> >> > ret = 0;
>> >> > mgr->payload_id_table_cleared = false;
>> >> > +
>> >> > + memset(&mgr->down_rep_recv, 0, sizeof(mgr->down_rep_recv));
>> >> > + memset(&mgr->up_req_recv, 0, sizeof(mgr->up_req_recv));
>> >> > }
>> >> >
>> >> > out_unlock:
>> >>
>> >> --
>> >> Cheers,
>> >> Lyude Paul (she/her)
>> >> Software Engineer at Red Hat
>> >>
>>
>> --
>> Jani Nikula, Intel Open Source Graphics Center
--
Jani Nikula, Intel Open Source Graphics Center
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2022-12-16 16:50 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-12-14 18:42 [Intel-gfx] [PATCH 1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect Imre Deak
2022-12-14 18:42 ` [Intel-gfx] [PATCH 2/3] drm/display/dp_mst: Fix down message handling after a packet reception error Imre Deak
2022-12-14 18:42 ` [Intel-gfx] [PATCH 3/3] drm/display/dp_mst: Fix payload addition on a disconnected sink Imre Deak
2022-12-14 20:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/3] drm/display/dp_mst: Fix down/up message handling after sink disconnect Patchwork
2022-12-14 21:41 ` [Intel-gfx] [PATCH 1/3] " Lyude Paul
2022-12-16 15:10 ` Imre Deak
2022-12-16 16:10 ` Jani Nikula
2022-12-16 16:33 ` Imre Deak
2022-12-16 16:49 ` Jani Nikula
2022-12-16 8:06 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/3] " Patchwork
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox