Skip to contentSkip to conversation

drm/i915: Tune down link train error messages due to IO failure

PATCH In review Imre Deak 4 participants 8 messages May 23, 2019 – May 25, 2019

Subsystems (2)
lore
Share & tools
lore

Imre Deak

author
#0 lore raw

PATCH 1/1 drm/i915: Tune down link train error messages due to IO failure

An IO failure happens if the sink is unplugged. This scenario shouldn't be logged with error level, since it is not a user visible problem. Converting the corresponding error messages to be debug messages also ensures that we don't fail some CI test incorrectly that tests the unplugging while a mode is still active on the given connector (like the kms_chamelium tests imititating such an unplug during being suspended).

Leave those link training error messages that are due to an actual transfer rate error (and not an IO error) as-is, as that kind of problem is related to the user's configuration (cable, mode, monitor) and so it is really user visible.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110390

---
 drivers/gpu/drm/i915/intel_dp_link_training.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/gpu/drm/i915/intel_dp_link_training.c +6 -6
index 9b1fccea966b..392ebeb89ce8 100644
@@ -169,7 +169,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 	if (!intel_dp_reset_link_train(intel_dp,
 				       DP_TRAINING_PATTERN_1 |
 				       DP_LINK_SCRAMBLING_DISABLE)) {
-		DRM_ERROR("failed to enable link training\n");
+		DRM_DEBUG_KMS("failed to enable link training\n");
 		return false;
 	}
 
@@ -193,7 +193,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 		drm_dp_link_train_clock_recovery_delay(intel_dp->dpcd);
 
 		if (!intel_dp_get_link_status(intel_dp, link_status)) {
-			DRM_ERROR("failed to get link status\n");
+			DRM_DEBUG_KMS("failed to get link status\n");
 			return false;
 		}
 
@@ -217,7 +217,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 		/* Update training set as requested by target */
 		intel_get_adjust_train(intel_dp, link_status);
 		if (!intel_dp_update_link_train(intel_dp)) {
-			DRM_ERROR("failed to update link training\n");
+			DRM_DEBUG_KMS("failed to update link training\n");
 			return false;
 		}
 
@@ -295,7 +295,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 	/* channel equalization */
 	if (!intel_dp_set_link_train(intel_dp,
 				     training_pattern)) {
-		DRM_ERROR("failed to start channel equalization\n");
+		DRM_DEBUG_KMS("failed to start channel equalization\n");
 		return false;
 	}
 
@@ -303,7 +303,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 
 		drm_dp_link_train_channel_eq_delay(intel_dp->dpcd);
 		if (!intel_dp_get_link_status(intel_dp, link_status)) {
-			DRM_ERROR("failed to get link status\n");
+			DRM_DEBUG_KMS("failed to get link status\n");
 			break;
 		}
 
@@ -327,7 +327,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 		/* Update training set as requested by target */
 		intel_get_adjust_train(intel_dp, link_status);
 		if (!intel_dp_update_link_train(intel_dp)) {
-			DRM_ERROR("failed to update link training\n");
+			DRM_DEBUG_KMS("failed to update link training\n");
 			break;
 		}
 	}
Signature · 6 lines
2.17.1

_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
#1 lore raw

✓ Fi.CI.BAT: success for drm/i915: Tune down link train error messages due to IO failure

== Series Details ==

== Series Details ==

Series: drm/i915: Tune down link train error messages due to IO failure
URL : https://patchwork.freedesktop.org/series/61039/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_6132 -> Patchwork_13079
====================================================

Summary
-------

**SUCCESS**

No regressions found.

External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/

Possible new issues
-------------------

Here are the unknown changes that may have been introduced in Patchwork_13079:

### IGT changes ###

#### Suppressed ####

The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.

* igt@kms_flip@basic-flip-vs-wf_vblank:
- {fi-icl-u3}: [DMESG-FAIL][1] ([fdo#110718]) -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/fi-icl-u3/igt@kms_flip@basic-flip-vs-wf_vblank.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/fi-icl-u3/igt@kms_flip@basic-flip-vs-wf_vblank.html

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

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

### IGT changes ###

#### Issues hit ####

* igt@i915_selftest@live_hangcheck:
- fi-skl-iommu: [PASS][3] -> [INCOMPLETE][4] ([fdo#108602] / [fdo#108744])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/fi-skl-iommu/igt@i915_selftest@live_hangcheck.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/fi-skl-iommu/igt@i915_selftest@live_hangcheck.html

#### Possible fixes ####

* igt@gem_ctx_create@basic-files:
- {fi-icl-dsi}: [INCOMPLETE][5] ([fdo#107713] / [fdo#109100]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/fi-icl-dsi/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/fi-icl-dsi/igt@[email protected]

* igt@gem_exec_reloc@basic-write-gtt-noreloc:
- {fi-icl-u3}: [DMESG-WARN][7] ([fdo#107724]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/fi-icl-u3/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/fi-icl-u3/igt@[email protected]

* igt@gem_exec_suspend@basic-s3:
- fi-blb-e6850: [INCOMPLETE][9] ([fdo#107718]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/fi-blb-e6850/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/fi-blb-e6850/igt@[email protected]

* igt@kms_chamelium@common-hpd-after-suspend:
- fi-kbl-7500u: [DMESG-WARN][11] ([fdo#102505] / [fdo#103558] / [fdo#105079] / [fdo#105602]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/fi-kbl-7500u/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/fi-kbl-7500u/igt@[email protected]
- {fi-icl-u2}: [DMESG-WARN][13] ([fdo#102505] / [fdo#110390] / [fdo#110718]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/fi-icl-u2/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/fi-icl-u2/igt@[email protected]
- {fi-cml-u2}: [DMESG-WARN][15] ([fdo#102505]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/fi-cml-u2/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/fi-cml-u2/igt@[email protected]

* igt@kms_flip@basic-plain-flip:
- {fi-icl-u3}: [DMESG-WARN][17] ([fdo#110718]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/fi-icl-u3/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/fi-icl-u3/igt@[email protected]

#### Warnings ####

* igt@i915_selftest@live_hangcheck:
- fi-apl-guc: [INCOMPLETE][19] ([fdo#103927] / [fdo#110624]) -> [DMESG-FAIL][20] ([fdo#110620])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/fi-apl-guc/igt@i915_selftest@live_hangcheck.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/fi-apl-guc/igt@i915_selftest@live_hangcheck.html

* igt@runner@aborted:
- fi-apl-guc: [FAIL][21] ([fdo#110624]) -> [FAIL][22] ([fdo#110622])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/fi-apl-guc/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/fi-apl-guc/igt@[email protected]

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

[fdo#102505]: https://bugs.freedesktop.org/show_bug.cgi?id=102505
[fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#105079]: https://bugs.freedesktop.org/show_bug.cgi?id=105079
[fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#108602]: https://bugs.freedesktop.org/show_bug.cgi?id=108602
[fdo#108730]: https://bugs.freedesktop.org/show_bug.cgi?id=108730
[fdo#108744]: https://bugs.freedesktop.org/show_bug.cgi?id=108744
[fdo#109100]: https://bugs.freedesktop.org/show_bug.cgi?id=109100
[fdo#110390]: https://bugs.freedesktop.org/show_bug.cgi?id=110390
[fdo#110620]: https://bugs.freedesktop.org/show_bug.cgi?id=110620
[fdo#110622]: https://bugs.freedesktop.org/show_bug.cgi?id=110622
[fdo#110624]: https://bugs.freedesktop.org/show_bug.cgi?id=110624
[fdo#110718]: https://bugs.freedesktop.org/show_bug.cgi?id=110718

Participating hosts (54 -> 46)
------------------------------

Missing (8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus

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

* Linux: CI_DRM_6132 -> Patchwork_13079

CI_DRM_6132: 78850b480c542b2e10da5a93afac2e13307909cb @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5010: 631f3ac2e78c8d6332afc693bf290ae23d8d5685 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_13079: d43e42399d099994c556ea4077ffc96779030fe8 @ git://anongit.freedesktop.org/gfx-ci/linux

== Linux commits ==

d43e42399d09 drm/i915: Tune down link train error messages due to IO failure

== Logs ==

For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

#2 lore raw
In reply to Imre Deak
Quoted 11 lines · Imre Deak

An IO failure happens if the sink is unplugged. This scenario shouldn't be logged with error level, since it is not a user visible problem. Converting the corresponding error messages to be debug messages also ensures that we don't fail some CI test incorrectly that tests the unplugging while a mode is still active on the given connector (like the kms_chamelium tests imititating such an unplug during being suspended).

Leave those link training error messages that are due to an actual transfer rate error (and not an IO error) as-is, as that kind of problem is related to the user's configuration (cable, mode, monitor) and so it is really user visible.

Are there some scenarios that would be warranting a DRM_ERROR? If so, then we should decide on the verbosity based on wether the connector is connected or disconnected, don't you think?

Martin

Quoted 58 lines

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110390

---
 drivers/gpu/drm/i915/intel_dp_link_training.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/gpu/drm/i915/intel_dp_link_training.c +5 -5
index 9b1fccea966b..392ebeb89ce8 100644
@@ -169,7 +169,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 	if (!intel_dp_reset_link_train(intel_dp,
 				       DP_TRAINING_PATTERN_1 |
 				       DP_LINK_SCRAMBLING_DISABLE)) {
-		DRM_ERROR("failed to enable link training\n");
+		DRM_DEBUG_KMS("failed to enable link training\n");
 		return false;
 	}
 
@@ -193,7 +193,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 		drm_dp_link_train_clock_recovery_delay(intel_dp->dpcd);
 
 		if (!intel_dp_get_link_status(intel_dp, link_status)) {
-			DRM_ERROR("failed to get link status\n");
+			DRM_DEBUG_KMS("failed to get link status\n");
 			return false;
 		}
 
@@ -217,7 +217,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 		/* Update training set as requested by target */
 		intel_get_adjust_train(intel_dp, link_status);
 		if (!intel_dp_update_link_train(intel_dp)) {
-			DRM_ERROR("failed to update link training\n");
+			DRM_DEBUG_KMS("failed to update link training\n");
 			return false;
 		}
 
@@ -295,7 +295,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 	/* channel equalization */
 	if (!intel_dp_set_link_train(intel_dp,
 				     training_pattern)) {
-		DRM_ERROR("failed to start channel equalization\n");
+		DRM_DEBUG_KMS("failed to start channel equalization\n");
 		return false;
 	}
 
@@ -303,7 +303,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 
 		drm_dp_link_train_channel_eq_delay(intel_dp->dpcd);
 		if (!intel_dp_get_link_status(intel_dp, link_status)) {
-			DRM_ERROR("failed to get link status\n");
+			DRM_DEBUG_KMS("failed to get link status\n");
 			break;
 		}
 

drivers/gpu/drm/i915/intel_dp_link_training.c intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp) · line 333

Quoted 8 lines
drivers/gpu/drm/i915/intel_dp_link_training.c +1 -1
@@ -327,7 +327,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 		/* Update training set as requested by target */
 		intel_get_adjust_train(intel_dp, link_status);
 		if (!intel_dp_update_link_train(intel_dp)) {
-			DRM_ERROR("failed to update link training\n");
+			DRM_DEBUG_KMS("failed to update link training\n");
 			break;
 		}
 	}

_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

author
#3 lore raw
Quoted 8 lines · Martin Peres
Quoted 7 lines · Imre Deak

An IO failure happens if the sink is unplugged. This scenario shouldn't be logged with error level, since it is not a user visible problem. Converting the corresponding error messages to be debug messages also ensures that we don't fail some CI test incorrectly that tests the unplugging while a mode is still active on the given connector (like the kms_chamelium tests imititating such an unplug during being suspended).

Quoted 8 lines
Quoted 4 lines

Leave those link training error messages that are due to an actual transfer rate error (and not an IO error) as-is, as that kind of problem is related to the user's configuration (cable, mode, monitor) and so it is really user visible.

Are there some scenarios that would be warranting a DRM_ERROR? If so, then we should decide on the verbosity based on wether the connector is connected or disconnected, don't you think?

I don't think we should depend on the correctness of setting the message level correctly based on the live state, since the live state itself is flaky/unreliable based on the timing of the unplug vs. the settling of the live state flag. For instance we could see the AUX IO failing already but live state still indicating that the sink is plugged, so we'd print again an error instead of the correct tuned-down note.

Quoted 58 lines

Martin

Quoted 56 lines

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110390

---
 drivers/gpu/drm/i915/intel_dp_link_training.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/gpu/drm/i915/intel_dp_link_training.c +5 -5
index 9b1fccea966b..392ebeb89ce8 100644
@@ -169,7 +169,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 	if (!intel_dp_reset_link_train(intel_dp,
 				       DP_TRAINING_PATTERN_1 |
 				       DP_LINK_SCRAMBLING_DISABLE)) {
-		DRM_ERROR("failed to enable link training\n");
+		DRM_DEBUG_KMS("failed to enable link training\n");
 		return false;
 	}
 
@@ -193,7 +193,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 		drm_dp_link_train_clock_recovery_delay(intel_dp->dpcd);
 
 		if (!intel_dp_get_link_status(intel_dp, link_status)) {
-			DRM_ERROR("failed to get link status\n");
+			DRM_DEBUG_KMS("failed to get link status\n");
 			return false;
 		}
 
@@ -217,7 +217,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 		/* Update training set as requested by target */
 		intel_get_adjust_train(intel_dp, link_status);
 		if (!intel_dp_update_link_train(intel_dp)) {
-			DRM_ERROR("failed to update link training\n");
+			DRM_DEBUG_KMS("failed to update link training\n");
 			return false;
 		}
 
@@ -295,7 +295,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 	/* channel equalization */
 	if (!intel_dp_set_link_train(intel_dp,
 				     training_pattern)) {
-		DRM_ERROR("failed to start channel equalization\n");
+		DRM_DEBUG_KMS("failed to start channel equalization\n");
 		return false;
 	}
 
@@ -303,7 +303,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 
 		drm_dp_link_train_channel_eq_delay(intel_dp->dpcd);
 		if (!intel_dp_get_link_status(intel_dp, link_status)) {
-			DRM_ERROR("failed to get link status\n");
+			DRM_DEBUG_KMS("failed to get link status\n");
 			break;
 		}
 
Quoted 11 lines

drivers/gpu/drm/i915/intel_dp_link_training.c intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp) · line 333

Quoted 10 lines
drivers/gpu/drm/i915/intel_dp_link_training.c +1 -1
@@ -327,7 +327,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 		/* Update training set as requested by target */
 		intel_get_adjust_train(intel_dp, link_status);
 		if (!intel_dp_update_link_train(intel_dp)) {
-			DRM_ERROR("failed to update link training\n");
+			DRM_DEBUG_KMS("failed to update link training\n");
 			break;
 		}
 	}

_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

#4 lore raw
Quoted 18 lines · Imre Deak
Quoted 8 lines · Martin Peres
Quoted 7 lines · Imre Deak

An IO failure happens if the sink is unplugged. This scenario shouldn't be logged with error level, since it is not a user visible problem. Converting the corresponding error messages to be debug messages also ensures that we don't fail some CI test incorrectly that tests the unplugging while a mode is still active on the given connector (like the kms_chamelium tests imititating such an unplug during being suspended).

Quoted 8 lines
Quoted 4 lines

Leave those link training error messages that are due to an actual transfer rate error (and not an IO error) as-is, as that kind of problem is related to the user's configuration (cable, mode, monitor) and so it is really user visible.

Are there some scenarios that would be warranting a DRM_ERROR? If so, then we should decide on the verbosity based on wether the connector is connected or disconnected, don't you think?

Quoted 7 lines

I don't think we should depend on the correctness of setting the message level correctly based on the live state, since the live state itself is flaky/unreliable based on the timing of the unplug vs. the settling of the live state flag. For instance we could see the AUX IO failing already but live state still indicating that the sink is plugged, so we'd print again an error instead of the correct tuned-down note.

But in case of AUX failures which we see a lot when AUX power
is accidently off or eDP is still not ON or sink is unplugged while the link training was in process, doesnt it make sense to
call it as a DRM_ERROR and not just a DEBUG_KMS.
For Eg: the CI tests failed due to AUX timeouts should be the actual failures which would be filtered now if we tune it down to DEBUG_KMS.

Manasi

Quoted 69 lines
Quoted 58 lines

Martin

Quoted 56 lines

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110390

---
 drivers/gpu/drm/i915/intel_dp_link_training.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/gpu/drm/i915/intel_dp_link_training.c +5 -5
index 9b1fccea966b..392ebeb89ce8 100644
@@ -169,7 +169,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 	if (!intel_dp_reset_link_train(intel_dp,
 				       DP_TRAINING_PATTERN_1 |
 				       DP_LINK_SCRAMBLING_DISABLE)) {
-		DRM_ERROR("failed to enable link training\n");
+		DRM_DEBUG_KMS("failed to enable link training\n");
 		return false;
 	}
 
@@ -193,7 +193,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 		drm_dp_link_train_clock_recovery_delay(intel_dp->dpcd);
 
 		if (!intel_dp_get_link_status(intel_dp, link_status)) {
-			DRM_ERROR("failed to get link status\n");
+			DRM_DEBUG_KMS("failed to get link status\n");
 			return false;
 		}
 
@@ -217,7 +217,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 		/* Update training set as requested by target */
 		intel_get_adjust_train(intel_dp, link_status);
 		if (!intel_dp_update_link_train(intel_dp)) {
-			DRM_ERROR("failed to update link training\n");
+			DRM_DEBUG_KMS("failed to update link training\n");
 			return false;
 		}
 
@@ -295,7 +295,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 	/* channel equalization */
 	if (!intel_dp_set_link_train(intel_dp,
 				     training_pattern)) {
-		DRM_ERROR("failed to start channel equalization\n");
+		DRM_DEBUG_KMS("failed to start channel equalization\n");
 		return false;
 	}
 
@@ -303,7 +303,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 
 		drm_dp_link_train_channel_eq_delay(intel_dp->dpcd);
 		if (!intel_dp_get_link_status(intel_dp, link_status)) {
-			DRM_ERROR("failed to get link status\n");
+			DRM_DEBUG_KMS("failed to get link status\n");
 			break;
 		}
 
Quoted 11 lines

drivers/gpu/drm/i915/intel_dp_link_training.c intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp) · line 333

Quoted 10 lines
drivers/gpu/drm/i915/intel_dp_link_training.c +1 -1
@@ -327,7 +327,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 		/* Update training set as requested by target */
 		intel_get_adjust_train(intel_dp, link_status);
 		if (!intel_dp_update_link_train(intel_dp)) {
-			DRM_ERROR("failed to update link training\n");
+			DRM_DEBUG_KMS("failed to update link training\n");
 			break;
 		}
 	}
Quoted 4 lines

_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

author
#5 lore raw
Quoted 26 lines · Manasi Navare
Quoted 18 lines · Imre Deak
Quoted 8 lines · Martin Peres
Quoted 7 lines · Imre Deak

An IO failure happens if the sink is unplugged. This scenario shouldn't be logged with error level, since it is not a user visible problem. Converting the corresponding error messages to be debug messages also ensures that we don't fail some CI test incorrectly that tests the unplugging while a mode is still active on the given connector (like the kms_chamelium tests imititating such an unplug during being suspended).

Quoted 8 lines
Quoted 4 lines

Leave those link training error messages that are due to an actual transfer rate error (and not an IO error) as-is, as that kind of problem is related to the user's configuration (cable, mode, monitor) and so it is really user visible.

Are there some scenarios that would be warranting a DRM_ERROR? If so, then we should decide on the verbosity based on wether the connector is connected or disconnected, don't you think?

Quoted 6 lines

I don't think we should depend on the correctness of setting the message level correctly based on the live state, since the live state itself is flaky/unreliable based on the timing of the unplug vs. the settling of the live state flag. For instance we could see the AUX IO failing already but live state still indicating that the sink is plugged, so we'd print again an error instead of the correct tuned-down note.

Quoted 4 lines

But in case of AUX failures which we see a lot when AUX power is accidently off or eDP is still not ON or sink is unplugged while the link training was in process, doesnt it make sense to call it as a DRM_ERROR and not just a DEBUG_KMS.

Logging such AUX fails as DEBUG makes sense, since it will be up to a developer to look through the logs if needed; for instance if it leads to failing the actual link training logged with DRM_ERROR or failing the detection when you expect the sink to be there.

Otoh, it's a bad thing to log such AUX fails as DRM_ERROR as will result in failing tests incorrectly when the sink is disconnected and the AUX fails happen as expected.

Quoted 2 lines

For Eg: the CI tests failed due to AUX timeouts should be the actual failures which would be filtered now if we tune it down to DEBUG_KMS.

These will lead to actually failing the detection/link training, which you can depend on failing the tests instead of depending on error messages in dmesg.

Quoted 76 lines

Manasi

Quoted 73 lines
Quoted 58 lines

Martin

Quoted 56 lines

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110390

---
 drivers/gpu/drm/i915/intel_dp_link_training.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/gpu/drm/i915/intel_dp_link_training.c +5 -5
index 9b1fccea966b..392ebeb89ce8 100644
@@ -169,7 +169,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 	if (!intel_dp_reset_link_train(intel_dp,
 				       DP_TRAINING_PATTERN_1 |
 				       DP_LINK_SCRAMBLING_DISABLE)) {
-		DRM_ERROR("failed to enable link training\n");
+		DRM_DEBUG_KMS("failed to enable link training\n");
 		return false;
 	}
 
@@ -193,7 +193,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 		drm_dp_link_train_clock_recovery_delay(intel_dp->dpcd);
 
 		if (!intel_dp_get_link_status(intel_dp, link_status)) {
-			DRM_ERROR("failed to get link status\n");
+			DRM_DEBUG_KMS("failed to get link status\n");
 			return false;
 		}
 
@@ -217,7 +217,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 		/* Update training set as requested by target */
 		intel_get_adjust_train(intel_dp, link_status);
 		if (!intel_dp_update_link_train(intel_dp)) {
-			DRM_ERROR("failed to update link training\n");
+			DRM_DEBUG_KMS("failed to update link training\n");
 			return false;
 		}
 
@@ -295,7 +295,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 	/* channel equalization */
 	if (!intel_dp_set_link_train(intel_dp,
 				     training_pattern)) {
-		DRM_ERROR("failed to start channel equalization\n");
+		DRM_DEBUG_KMS("failed to start channel equalization\n");
 		return false;
 	}
 
@@ -303,7 +303,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 
 		drm_dp_link_train_channel_eq_delay(intel_dp->dpcd);
 		if (!intel_dp_get_link_status(intel_dp, link_status)) {
-			DRM_ERROR("failed to get link status\n");
+			DRM_DEBUG_KMS("failed to get link status\n");
 			break;
 		}
 
Quoted 11 lines

drivers/gpu/drm/i915/intel_dp_link_training.c intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp) · line 333

Quoted 10 lines
drivers/gpu/drm/i915/intel_dp_link_training.c +1 -1
@@ -327,7 +327,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 		/* Update training set as requested by target */
 		intel_get_adjust_train(intel_dp, link_status);
 		if (!intel_dp_update_link_train(intel_dp)) {
-			DRM_ERROR("failed to update link training\n");
+			DRM_DEBUG_KMS("failed to update link training\n");
 			break;
 		}
 	}

_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

Reviewed-by
#6 lore raw
Quoted 41 lines · Imre Deak
Quoted 26 lines · Manasi Navare
Quoted 18 lines · Imre Deak
Quoted 8 lines · Martin Peres
Quoted 7 lines · Imre Deak

An IO failure happens if the sink is unplugged. This scenario shouldn't be logged with error level, since it is not a user visible problem. Converting the corresponding error messages to be debug messages also ensures that we don't fail some CI test incorrectly that tests the unplugging while a mode is still active on the given connector (like the kms_chamelium tests imititating such an unplug during being suspended).

Quoted 8 lines
Quoted 4 lines

Leave those link training error messages that are due to an actual transfer rate error (and not an IO error) as-is, as that kind of problem is related to the user's configuration (cable, mode, monitor) and so it is really user visible.

Are there some scenarios that would be warranting a DRM_ERROR? If so, then we should decide on the verbosity based on wether the connector is connected or disconnected, don't you think?

Quoted 6 lines

I don't think we should depend on the correctness of setting the message level correctly based on the live state, since the live state itself is flaky/unreliable based on the timing of the unplug vs. the settling of the live state flag. For instance we could see the AUX IO failing already but live state still indicating that the sink is plugged, so we'd print again an error instead of the correct tuned-down note.

Quoted 4 lines

But in case of AUX failures which we see a lot when AUX power is accidently off or eDP is still not ON or sink is unplugged while the link training was in process, doesnt it make sense to call it as a DRM_ERROR and not just a DEBUG_KMS.

Logging such AUX fails as DEBUG makes sense, since it will be up to a developer to look through the logs if needed; for instance if it leads to failing the actual link training logged with DRM_ERROR or failing the detection when you expect the sink to be there.

Otoh, it's a bad thing to log such AUX fails as DRM_ERROR as will result in failing tests incorrectly when the sink is disconnected and the AUX fails happen as expected.

Quoted 6 lines
Quoted 2 lines

For Eg: the CI tests failed due to AUX timeouts should be the actual failures which would be filtered now if we tune it down to DEBUG_KMS.

These will lead to actually failing the detection/link training, which you can depend on failing the tests instead of depending on error messages in dmesg.

Okay makes sense. So basically rely on the final result of training only to decide if its a real failure or not.
Got it.
Looks good to me in that case.

Manasi

Quoted 73 lines
Quoted 73 lines

Manasi

Quoted 69 lines
Quoted 69 lines

Martin

Quoted 66 lines

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110390

---
 drivers/gpu/drm/i915/intel_dp_link_training.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/gpu/drm/i915/intel_dp_link_training.c +6 -6
index 9b1fccea966b..392ebeb89ce8 100644
@@ -169,7 +169,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 	if (!intel_dp_reset_link_train(intel_dp,
 				       DP_TRAINING_PATTERN_1 |
 				       DP_LINK_SCRAMBLING_DISABLE)) {
-		DRM_ERROR("failed to enable link training\n");
+		DRM_DEBUG_KMS("failed to enable link training\n");
 		return false;
 	}
 
@@ -193,7 +193,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 		drm_dp_link_train_clock_recovery_delay(intel_dp->dpcd);
 
 		if (!intel_dp_get_link_status(intel_dp, link_status)) {
-			DRM_ERROR("failed to get link status\n");
+			DRM_DEBUG_KMS("failed to get link status\n");
 			return false;
 		}
 
@@ -217,7 +217,7 @@ intel_dp_link_training_clock_recovery(struct intel_dp *intel_dp)
 		/* Update training set as requested by target */
 		intel_get_adjust_train(intel_dp, link_status);
 		if (!intel_dp_update_link_train(intel_dp)) {
-			DRM_ERROR("failed to update link training\n");
+			DRM_DEBUG_KMS("failed to update link training\n");
 			return false;
 		}
 
@@ -295,7 +295,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 	/* channel equalization */
 	if (!intel_dp_set_link_train(intel_dp,
 				     training_pattern)) {
-		DRM_ERROR("failed to start channel equalization\n");
+		DRM_DEBUG_KMS("failed to start channel equalization\n");
 		return false;
 	}
 
@@ -303,7 +303,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 
 		drm_dp_link_train_channel_eq_delay(intel_dp->dpcd);
 		if (!intel_dp_get_link_status(intel_dp, link_status)) {
-			DRM_ERROR("failed to get link status\n");
+			DRM_DEBUG_KMS("failed to get link status\n");
 			break;
 		}
 
@@ -327,7 +327,7 @@ intel_dp_link_training_channel_equalization(struct intel_dp *intel_dp)
 		/* Update training set as requested by target */
 		intel_get_adjust_train(intel_dp, link_status);
 		if (!intel_dp_update_link_train(intel_dp)) {
-			DRM_ERROR("failed to update link training\n");
+			DRM_DEBUG_KMS("failed to update link training\n");
 			break;
 		}
 	}
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

#7 lore raw

✓ Fi.CI.IGT: success for drm/i915: Tune down link train error messages due to IO failure

In reply to Imre Deak
== Series Details ==

== Series Details ==

Series: drm/i915: Tune down link train error messages due to IO failure
URL : https://patchwork.freedesktop.org/series/61039/
State : success

== Summary ==

CI Bug Log - changes from CI_DRM_6132_full -> Patchwork_13079_full
====================================================

Summary
-------

**WARNING**

Minor unknown changes coming with Patchwork_13079_full need to be verified manually.

If you think the reported changes have nothing to do with the changes introduced in Patchwork_13079_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.

Possible new issues
-------------------

Here are the unknown changes that may have been introduced in Patchwork_13079_full:

### IGT changes ###

#### Warnings ####

* igt@prime_vgem@wait-bsd1:
- shard-snb: [INCOMPLETE][1] ([fdo#105411]) -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-snb5/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-snb4/igt@[email protected]

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

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

### IGT changes ###

#### Issues hit ####

* igt@gem_persistent_relocs@forked-interruptible-thrashing:
- shard-iclb: [PASS][3] -> [INCOMPLETE][4] ([fdo#107713])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-iclb4/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-iclb7/igt@[email protected]

* igt@i915_pm_rpm@system-suspend:
- shard-skl: [PASS][5] -> [INCOMPLETE][6] ([fdo#104108] / [fdo#107807])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-skl7/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-skl9/igt@[email protected]
- shard-kbl: [PASS][7] -> [INCOMPLETE][8] ([fdo#103665] / [fdo#107807])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-kbl6/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-kbl4/igt@[email protected]

* igt@kms_cursor_legacy@2x-cursor-vs-flip-atomic:
- shard-hsw: [PASS][9] -> [SKIP][10] ([fdo#109271]) +25 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-hsw4/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-hsw5/igt@[email protected]

* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-skl: [PASS][11] -> [FAIL][12] ([fdo#102670])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-skl3/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-skl6/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html

* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-skl: [PASS][13] -> [INCOMPLETE][14] ([fdo#109507])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-skl2/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-skl5/igt@[email protected]

* igt@kms_flip@plain-flip-fb-recreate-interruptible:
- shard-glk: [PASS][15] -> [FAIL][16] ([fdo#100368])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-glk5/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-glk8/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-mmap-gtt:
- shard-iclb: [PASS][17] -> [FAIL][18] ([fdo#103167])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-mmap-gtt.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-mmap-gtt.html

* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-shrfb-draw-mmap-wc:
- shard-glk: [PASS][19] -> [INCOMPLETE][20] ([fdo#103359] / [k.org#198133])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-glk5/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-shrfb-draw-mmap-wc.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-glk8/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-shrfb-draw-mmap-wc.html

* igt@kms_plane_alpha_blend@pipe-b-constant-alpha-min:
- shard-skl: [PASS][21] -> [FAIL][22] ([fdo#108145])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-skl7/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-skl7/igt@[email protected]

* igt@kms_psr2_su@page_flip:
- shard-iclb: [PASS][23] -> [SKIP][24] ([fdo#109642])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-iclb2/igt@kms_psr2_su@page_flip.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-iclb6/igt@kms_psr2_su@page_flip.html

* igt@kms_setmode@basic:
- shard-kbl: [PASS][25] -> [FAIL][26] ([fdo#99912])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-kbl2/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-kbl1/igt@[email protected]

* igt@kms_vblank@pipe-c-ts-continuation-suspend:
- shard-apl: [PASS][27] -> [DMESG-WARN][28] ([fdo#108566]) +3 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-apl2/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-apl5/igt@[email protected]

#### Possible fixes ####

* igt@gem_softpin@noreloc-s3:
- shard-skl: [INCOMPLETE][29] ([fdo#104108]) -> [PASS][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-skl5/igt@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-skl7/igt@[email protected]

* igt@gem_workarounds@suspend-resume:
- shard-apl: [DMESG-WARN][31] ([fdo#108566]) -> [PASS][32] +5 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-apl3/igt@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-apl6/igt@[email protected]

* igt@kms_flip_tiling@flip-to-y-tiled:
- shard-iclb: [FAIL][33] ([fdo#107931] / [fdo#108134]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-iclb3/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-iclb3/igt@[email protected]

* igt@kms_flip_tiling@flip-x-tiled:
- shard-skl: [FAIL][35] ([fdo#108145] / [fdo#108303]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-skl5/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-skl1/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move:
- shard-iclb: [FAIL][37] ([fdo#103167]) -> [PASS][38] +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-iclb4/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-iclb7/igt@[email protected]

* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-shrfb-draw-mmap-wc:
- shard-hsw: [SKIP][39] ([fdo#109271]) -> [PASS][40] +25 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-hsw5/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-shrfb-draw-mmap-wc.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-hsw6/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-shrfb-draw-mmap-wc.html

* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-spr-indfb-move:
- shard-skl: [FAIL][41] ([fdo#108040]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-skl3/igt@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-skl6/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-skl: [FAIL][43] ([fdo#108145]) -> [PASS][44] +1 similar issue
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-skl3/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-skl6/igt@[email protected]

* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [FAIL][45] ([fdo#108145] / [fdo#110403]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-skl3/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-skl6/igt@[email protected]

* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-iclb: [FAIL][47] ([fdo#103166]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-iclb4/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-iclb7/igt@[email protected]

* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][49] ([fdo#109642]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-iclb8/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-iclb2/igt@[email protected]

* igt@kms_setmode@basic:
- shard-apl: [FAIL][51] ([fdo#99912]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-apl3/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-apl6/igt@[email protected]

#### Warnings ####

* igt@gem_mmap_gtt@forked-big-copy-odd:
- shard-iclb: [INCOMPLETE][53] ([fdo#107713] / [fdo#109100]) -> [TIMEOUT][54] ([fdo#109673]) +1 similar issue
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-iclb2/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-iclb2/igt@[email protected]

* igt@gem_tiled_swapping@non-threaded:
- shard-hsw: [FAIL][55] ([fdo#108686]) -> [INCOMPLETE][56] ([fdo#103540])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-hsw1/igt@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-hsw2/igt@[email protected]

* igt@kms_flip@2x-flip-vs-expired-vblank:
- shard-apl: [SKIP][57] ([fdo#109271]) -> [INCOMPLETE][58] ([fdo#103927])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-apl1/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-apl1/igt@[email protected]

* igt@prime_vgem@busy-bsd1:
- shard-snb: [FAIL][59] -> [INCOMPLETE][60] ([fdo#105411])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6132/shard-snb2/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13079/shard-snb7/igt@[email protected]

[fdo#100368]: https://bugs.freedesktop.org/show_bug.cgi?id=100368
[fdo#102670]: https://bugs.freedesktop.org/show_bug.cgi?id=102670
[fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103359]: https://bugs.freedesktop.org/show_bug.cgi?id=103359
[fdo#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540
[fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108
[fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107807]: https://bugs.freedesktop.org/show_bug.cgi?id=107807
[fdo#107931]: https://bugs.freedesktop.org/show_bug.cgi?id=107931
[fdo#108040]: https://bugs.freedesktop.org/show_bug.cgi?id=108040
[fdo#108134]: https://bugs.freedesktop.org/show_bug.cgi?id=108134
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#108303]: https://bugs.freedesktop.org/show_bug.cgi?id=108303
[fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
[fdo#108686]: https://bugs.freedesktop.org/show_bug.cgi?id=108686
[fdo#109100]: https://bugs.freedesktop.org/show_bug.cgi?id=109100
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109507]: https://bugs.freedesktop.org/show_bug.cgi?id=109507
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#109673]: https://bugs.freedesktop.org/show_bug.cgi?id=109673
[fdo#110403]: https://bugs.freedesktop.org/show_bug.cgi?id=110403
[fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912
[k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133

Participating hosts (10 -> 10)
------------------------------

No changes in participating hosts

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

* Linux: CI_DRM_6132 -> Patchwork_13079

CI_DRM_6132: 78850b480c542b2e10da5a93afac2e13307909cb @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5010: 631f3ac2e78c8d6332afc693bf290ae23d8d5685 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_13079: d43e42399d099994c556ea4077ffc96779030fe8 @ 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_13079/
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx