* [PATCH] drm/i915/display/lspcon: Increase LSPCON mode settle timeout
@ 2022-09-15 0:46 ` Pablo Ceballos
0 siblings, 0 replies; 14+ messages in thread
From: Pablo Ceballos @ 2022-09-15 0:46 UTC (permalink / raw)
To: David Airlie, Daniel Vetter
Cc: Jani Nikula, Joonas Lahtinen, Rodrigo Vivi, Tvrtko Ursulin,
Ville Syrjälä,
Thomas Zimmermann, Javier Martinez Canillas, Sam Ravnborg,
Pablo Ceballos, Maxime Ripard, intel-gfx, dri-devel,
linux-kernel
On some devices the Parade PS175 takes more than 400ms to settle in PCON
mode.
Signed-off-by: Pablo Ceballos <pceballos@google.com>
---
drivers/gpu/drm/i915/display/intel_lspcon.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_lspcon.c b/drivers/gpu/drm/i915/display/intel_lspcon.c
index 15d59de8810e..b4cbade13ee5 100644
--- a/drivers/gpu/drm/i915/display/intel_lspcon.c
+++ b/drivers/gpu/drm/i915/display/intel_lspcon.c
@@ -166,7 +166,7 @@ static enum drm_lspcon_mode lspcon_wait_mode(struct intel_lspcon *lspcon,
drm_dbg_kms(&i915->drm, "Waiting for LSPCON mode %s to settle\n",
lspcon_mode_name(mode));
- wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 400);
+ wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 800);
if (current_mode != mode)
drm_err(&i915->drm, "LSPCON mode hasn't settled\n");
--
2.37.2.789.g6183377224-goog
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [PATCH] drm/i915/display/lspcon: Increase LSPCON mode settle timeout
@ 2022-09-15 0:46 ` Pablo Ceballos
0 siblings, 0 replies; 14+ messages in thread
From: Pablo Ceballos @ 2022-09-15 0:46 UTC (permalink / raw)
To: David Airlie, Daniel Vetter
Cc: Tvrtko Ursulin, dri-devel, intel-gfx, Javier Martinez Canillas,
linux-kernel, Maxime Ripard, Thomas Zimmermann, Rodrigo Vivi,
Sam Ravnborg, Pablo Ceballos
On some devices the Parade PS175 takes more than 400ms to settle in PCON
mode.
Signed-off-by: Pablo Ceballos <pceballos@google.com>
---
drivers/gpu/drm/i915/display/intel_lspcon.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_lspcon.c b/drivers/gpu/drm/i915/display/intel_lspcon.c
index 15d59de8810e..b4cbade13ee5 100644
--- a/drivers/gpu/drm/i915/display/intel_lspcon.c
+++ b/drivers/gpu/drm/i915/display/intel_lspcon.c
@@ -166,7 +166,7 @@ static enum drm_lspcon_mode lspcon_wait_mode(struct intel_lspcon *lspcon,
drm_dbg_kms(&i915->drm, "Waiting for LSPCON mode %s to settle\n",
lspcon_mode_name(mode));
- wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 400);
+ wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 800);
if (current_mode != mode)
drm_err(&i915->drm, "LSPCON mode hasn't settled\n");
--
2.37.2.789.g6183377224-goog
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [Intel-gfx] [PATCH] drm/i915/display/lspcon: Increase LSPCON mode settle timeout
@ 2022-09-15 0:46 ` Pablo Ceballos
0 siblings, 0 replies; 14+ messages in thread
From: Pablo Ceballos @ 2022-09-15 0:46 UTC (permalink / raw)
To: David Airlie, Daniel Vetter
Cc: dri-devel, intel-gfx, Javier Martinez Canillas, linux-kernel,
Maxime Ripard, Thomas Zimmermann, Rodrigo Vivi, Sam Ravnborg,
Pablo Ceballos
On some devices the Parade PS175 takes more than 400ms to settle in PCON
mode.
Signed-off-by: Pablo Ceballos <pceballos@google.com>
---
drivers/gpu/drm/i915/display/intel_lspcon.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_lspcon.c b/drivers/gpu/drm/i915/display/intel_lspcon.c
index 15d59de8810e..b4cbade13ee5 100644
--- a/drivers/gpu/drm/i915/display/intel_lspcon.c
+++ b/drivers/gpu/drm/i915/display/intel_lspcon.c
@@ -166,7 +166,7 @@ static enum drm_lspcon_mode lspcon_wait_mode(struct intel_lspcon *lspcon,
drm_dbg_kms(&i915->drm, "Waiting for LSPCON mode %s to settle\n",
lspcon_mode_name(mode));
- wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 400);
+ wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 800);
if (current_mode != mode)
drm_err(&i915->drm, "LSPCON mode hasn't settled\n");
--
2.37.2.789.g6183377224-goog
^ permalink raw reply related [flat|nested] 14+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/display/lspcon: Increase LSPCON mode settle timeout
2022-09-15 0:46 ` Pablo Ceballos
(?)
(?)
@ 2022-09-19 19:57 ` Patchwork
-1 siblings, 0 replies; 14+ messages in thread
From: Patchwork @ 2022-09-19 19:57 UTC (permalink / raw)
To: Pablo Ceballos; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/display/lspcon: Increase LSPCON mode settle timeout
URL : https://patchwork.freedesktop.org/series/108735/
State : warning
== Summary ==
Error: patch https://patchwork.freedesktop.org/api/1.0/series/108735/revisions/1/mbox/ not found
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915/display/lspcon: Increase LSPCON mode settle timeout
2022-09-15 0:46 ` Pablo Ceballos
` (2 preceding siblings ...)
(?)
@ 2022-09-19 19:58 ` Patchwork
-1 siblings, 0 replies; 14+ messages in thread
From: Patchwork @ 2022-09-19 19:58 UTC (permalink / raw)
To: Pablo Ceballos; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/display/lspcon: Increase LSPCON mode settle timeout
URL : https://patchwork.freedesktop.org/series/108735/
State : warning
== Summary ==
Error: patch https://patchwork.freedesktop.org/api/1.0/series/108735/revisions/1/mbox/ not found
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/display/lspcon: Increase LSPCON mode settle timeout
2022-09-15 0:46 ` Pablo Ceballos
` (3 preceding siblings ...)
(?)
@ 2022-09-19 20:19 ` Patchwork
-1 siblings, 0 replies; 14+ messages in thread
From: Patchwork @ 2022-09-19 20:19 UTC (permalink / raw)
To: Pablo Ceballos; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 5427 bytes --]
== Series Details ==
Series: drm/i915/display/lspcon: Increase LSPCON mode settle timeout
URL : https://patchwork.freedesktop.org/series/108735/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12158 -> Patchwork_108735v1
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_108735v1 absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_108735v1, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v1/index.html
Participating hosts (42 -> 38)
------------------------------
Missing (4): fi-ctg-p8600 fi-hsw-4770 bat-adlp-6 bat-jsl-3
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_108735v1:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@migrate:
- fi-bsw-kefka: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12158/fi-bsw-kefka/igt@i915_selftest@live@migrate.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v1/fi-bsw-kefka/igt@i915_selftest@live@migrate.html
Known issues
------------
Here are the changes found in Patchwork_108735v1 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@prime_vgem@basic-userptr:
- fi-tgl-u2: NOTRUN -> [SKIP][3] ([fdo#109295] / [i915#3301])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v1/fi-tgl-u2/igt@prime_vgem@basic-userptr.html
* igt@runner@aborted:
- fi-bsw-kefka: NOTRUN -> [FAIL][4] ([fdo#109271] / [i915#4312] / [i915#6837])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v1/fi-bsw-kefka/igt@runner@aborted.html
#### Possible fixes ####
* igt@fbdev@write:
- {fi-tgl-mst}: [SKIP][5] ([i915#2582]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12158/fi-tgl-mst/igt@fbdev@write.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v1/fi-tgl-mst/igt@fbdev@write.html
* igt@gem_ctx_create@basic-files:
- {fi-tgl-mst}: [DMESG-WARN][7] -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12158/fi-tgl-mst/igt@gem_ctx_create@basic-files.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v1/fi-tgl-mst/igt@gem_ctx_create@basic-files.html
* igt@gem_exec_suspend@basic-s0@smem:
- {bat-adlm-1}: [DMESG-WARN][9] ([i915#2867]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12158/bat-adlm-1/igt@gem_exec_suspend@basic-s0@smem.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v1/bat-adlm-1/igt@gem_exec_suspend@basic-s0@smem.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions-varying-size:
- fi-bsw-kefka: [FAIL][11] ([i915#6298]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12158/fi-bsw-kefka/igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions-varying-size.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v1/fi-bsw-kefka/igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions-varying-size.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#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#2867]: https://gitlab.freedesktop.org/drm/intel/issues/2867
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#5122]: https://gitlab.freedesktop.org/drm/intel/issues/5122
[i915#5257]: https://gitlab.freedesktop.org/drm/intel/issues/5257
[i915#6257]: https://gitlab.freedesktop.org/drm/intel/issues/6257
[i915#6298]: https://gitlab.freedesktop.org/drm/intel/issues/6298
[i915#6380]: https://gitlab.freedesktop.org/drm/intel/issues/6380
[i915#6434]: https://gitlab.freedesktop.org/drm/intel/issues/6434
[i915#6599]: https://gitlab.freedesktop.org/drm/intel/issues/6599
[i915#6645]: https://gitlab.freedesktop.org/drm/intel/issues/6645
[i915#6724]: https://gitlab.freedesktop.org/drm/intel/issues/6724
[i915#6837]: https://gitlab.freedesktop.org/drm/intel/issues/6837
Build changes
-------------
* Linux: CI_DRM_12158 -> Patchwork_108735v1
CI-20190529: 20190529
CI_DRM_12158: 3bde74f15d452bf788ecab8933ee802b2ee9e673 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6656: 24100c4e181c50e3678aeca9c641b8a43555ad73 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_108735v1: 3bde74f15d452bf788ecab8933ee802b2ee9e673 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
bad249e7d0dc drm/i915/display/lspcon: Increase LSPCON mode settle timeout
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v1/index.html
[-- Attachment #2: Type: text/html, Size: 5537 bytes --]
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH] drm/i915/display/lspcon: Increase LSPCON mode settle timeout
2022-09-15 0:46 ` Pablo Ceballos
(?)
@ 2022-10-04 17:38 ` Jani Nikula
-1 siblings, 0 replies; 14+ messages in thread
From: Jani Nikula @ 2022-10-04 17:38 UTC (permalink / raw)
To: Pablo Ceballos, David Airlie, Daniel Vetter
Cc: Joonas Lahtinen, Rodrigo Vivi, Tvrtko Ursulin,
Ville Syrjälä,
Thomas Zimmermann, Javier Martinez Canillas, Sam Ravnborg,
Pablo Ceballos, Maxime Ripard, intel-gfx, dri-devel,
linux-kernel
On Thu, 15 Sep 2022, Pablo Ceballos <pceballos@google.com> wrote:
> On some devices the Parade PS175 takes more than 400ms to settle in PCON
> mode.
Got any bug report with more info, or any other details to back this up?
This is kind of thin. What's the 800 ms based on?
BR,
Jani.
>
> Signed-off-by: Pablo Ceballos <pceballos@google.com>
> ---
> drivers/gpu/drm/i915/display/intel_lspcon.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_lspcon.c b/drivers/gpu/drm/i915/display/intel_lspcon.c
> index 15d59de8810e..b4cbade13ee5 100644
> --- a/drivers/gpu/drm/i915/display/intel_lspcon.c
> +++ b/drivers/gpu/drm/i915/display/intel_lspcon.c
> @@ -166,7 +166,7 @@ static enum drm_lspcon_mode lspcon_wait_mode(struct intel_lspcon *lspcon,
> drm_dbg_kms(&i915->drm, "Waiting for LSPCON mode %s to settle\n",
> lspcon_mode_name(mode));
>
> - wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 400);
> + wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 800);
> if (current_mode != mode)
> drm_err(&i915->drm, "LSPCON mode hasn't settled\n");
--
Jani Nikula, Intel Open Source Graphics Center
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/display/lspcon: Increase LSPCON mode settle timeout
@ 2022-10-04 17:38 ` Jani Nikula
0 siblings, 0 replies; 14+ messages in thread
From: Jani Nikula @ 2022-10-04 17:38 UTC (permalink / raw)
To: Pablo Ceballos, David Airlie, Daniel Vetter
Cc: intel-gfx, Javier Martinez Canillas, dri-devel, linux-kernel,
Maxime Ripard, Thomas Zimmermann, Rodrigo Vivi, Sam Ravnborg,
Pablo Ceballos
On Thu, 15 Sep 2022, Pablo Ceballos <pceballos@google.com> wrote:
> On some devices the Parade PS175 takes more than 400ms to settle in PCON
> mode.
Got any bug report with more info, or any other details to back this up?
This is kind of thin. What's the 800 ms based on?
BR,
Jani.
>
> Signed-off-by: Pablo Ceballos <pceballos@google.com>
> ---
> drivers/gpu/drm/i915/display/intel_lspcon.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_lspcon.c b/drivers/gpu/drm/i915/display/intel_lspcon.c
> index 15d59de8810e..b4cbade13ee5 100644
> --- a/drivers/gpu/drm/i915/display/intel_lspcon.c
> +++ b/drivers/gpu/drm/i915/display/intel_lspcon.c
> @@ -166,7 +166,7 @@ static enum drm_lspcon_mode lspcon_wait_mode(struct intel_lspcon *lspcon,
> drm_dbg_kms(&i915->drm, "Waiting for LSPCON mode %s to settle\n",
> lspcon_mode_name(mode));
>
> - wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 400);
> + wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 800);
> if (current_mode != mode)
> drm_err(&i915->drm, "LSPCON mode hasn't settled\n");
--
Jani Nikula, Intel Open Source Graphics Center
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH] drm/i915/display/lspcon: Increase LSPCON mode settle timeout
@ 2022-10-04 17:38 ` Jani Nikula
0 siblings, 0 replies; 14+ messages in thread
From: Jani Nikula @ 2022-10-04 17:38 UTC (permalink / raw)
To: Pablo Ceballos, David Airlie, Daniel Vetter
Cc: Tvrtko Ursulin, intel-gfx, Javier Martinez Canillas, dri-devel,
linux-kernel, Maxime Ripard, Thomas Zimmermann, Rodrigo Vivi,
Sam Ravnborg, Pablo Ceballos
On Thu, 15 Sep 2022, Pablo Ceballos <pceballos@google.com> wrote:
> On some devices the Parade PS175 takes more than 400ms to settle in PCON
> mode.
Got any bug report with more info, or any other details to back this up?
This is kind of thin. What's the 800 ms based on?
BR,
Jani.
>
> Signed-off-by: Pablo Ceballos <pceballos@google.com>
> ---
> drivers/gpu/drm/i915/display/intel_lspcon.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_lspcon.c b/drivers/gpu/drm/i915/display/intel_lspcon.c
> index 15d59de8810e..b4cbade13ee5 100644
> --- a/drivers/gpu/drm/i915/display/intel_lspcon.c
> +++ b/drivers/gpu/drm/i915/display/intel_lspcon.c
> @@ -166,7 +166,7 @@ static enum drm_lspcon_mode lspcon_wait_mode(struct intel_lspcon *lspcon,
> drm_dbg_kms(&i915->drm, "Waiting for LSPCON mode %s to settle\n",
> lspcon_mode_name(mode));
>
> - wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 400);
> + wait_for((current_mode = lspcon_get_current_mode(lspcon)) == mode, 800);
> if (current_mode != mode)
> drm_err(&i915->drm, "LSPCON mode hasn't settled\n");
--
Jani Nikula, Intel Open Source Graphics Center
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH] drm/i915/display/lspcon: Increase LSPCON mode settle timeout
2022-10-04 17:38 ` [Intel-gfx] " Jani Nikula
(?)
@ 2022-10-06 22:59 ` Pablo Ceballos
-1 siblings, 0 replies; 14+ messages in thread
From: Pablo Ceballos @ 2022-10-06 22:59 UTC (permalink / raw)
To: Jani Nikula
Cc: David Airlie, Daniel Vetter, Joonas Lahtinen, Rodrigo Vivi,
Tvrtko Ursulin, Ville Syrjälä,
Thomas Zimmermann, Javier Martinez Canillas, Sam Ravnborg,
Maxime Ripard, intel-gfx, dri-devel, linux-kernel
On Tue, Oct 4, 2022 at 10:38 AM Jani Nikula <jani.nikula@linux.intel.com> wrote:
> Got any bug report with more info, or any other details to back this up?
> This is kind of thin. What's the 800 ms based on?
This issue affected several different CometLake-based Chrome OS device
designs. The details of the original report are in the Google partner
issue tracker (issue # 178169843), but I believe this requires a
Google partner account to access:
https://partnerissuetracker.corp.google.com/issues/178169843
The summary is that we were seeing these "*ERROR* LSPCON mode hasn't
settled" messages in the kernel logs followed by the display not
working at all. We increased the timeout to 500ms while investigation
continued and this reduced the number of occurrences of this issue:
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/7b2899fc1a6f9409e8075b3153baaf02c4d1fc75
The problem continued to occur on about 2% of devices even after
increasing the timeout to 500ms. The investigation continued in issue
# 188035814, with engineers from Parade and Intel involved.
Ultimately, the recommendation from Intel engineers was to increase
the timeout further:
https://partnerissuetracker.corp.google.com/issues/188035814
The timeout was then increased to 1000ms:
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/a16cfc2062e768c8e5ad8fa09b8ca127aa1ead9a
I recently ran 100 reboot trials on one device and found that the
median time for the LSPCON mode to settle was 440ms and the max was
444ms. But we know from the original reports that even after we set
the timeout to 500ms the issue continued to happen on some small
percentage of devices. So this is why I picked the larger value of
800ms.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH] drm/i915/display/lspcon: Increase LSPCON mode settle timeout
@ 2022-10-06 22:59 ` Pablo Ceballos
0 siblings, 0 replies; 14+ messages in thread
From: Pablo Ceballos @ 2022-10-06 22:59 UTC (permalink / raw)
To: Jani Nikula
Cc: Tvrtko Ursulin, Thomas Zimmermann, David Airlie, intel-gfx,
Javier Martinez Canillas, dri-devel, linux-kernel, Maxime Ripard,
Rodrigo Vivi, Sam Ravnborg
On Tue, Oct 4, 2022 at 10:38 AM Jani Nikula <jani.nikula@linux.intel.com> wrote:
> Got any bug report with more info, or any other details to back this up?
> This is kind of thin. What's the 800 ms based on?
This issue affected several different CometLake-based Chrome OS device
designs. The details of the original report are in the Google partner
issue tracker (issue # 178169843), but I believe this requires a
Google partner account to access:
https://partnerissuetracker.corp.google.com/issues/178169843
The summary is that we were seeing these "*ERROR* LSPCON mode hasn't
settled" messages in the kernel logs followed by the display not
working at all. We increased the timeout to 500ms while investigation
continued and this reduced the number of occurrences of this issue:
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/7b2899fc1a6f9409e8075b3153baaf02c4d1fc75
The problem continued to occur on about 2% of devices even after
increasing the timeout to 500ms. The investigation continued in issue
# 188035814, with engineers from Parade and Intel involved.
Ultimately, the recommendation from Intel engineers was to increase
the timeout further:
https://partnerissuetracker.corp.google.com/issues/188035814
The timeout was then increased to 1000ms:
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/a16cfc2062e768c8e5ad8fa09b8ca127aa1ead9a
I recently ran 100 reboot trials on one device and found that the
median time for the LSPCON mode to settle was 440ms and the max was
444ms. But we know from the original reports that even after we set
the timeout to 500ms the issue continued to happen on some small
percentage of devices. So this is why I picked the larger value of
800ms.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/display/lspcon: Increase LSPCON mode settle timeout
@ 2022-10-06 22:59 ` Pablo Ceballos
0 siblings, 0 replies; 14+ messages in thread
From: Pablo Ceballos @ 2022-10-06 22:59 UTC (permalink / raw)
To: Jani Nikula
Cc: Thomas Zimmermann, David Airlie, intel-gfx,
Javier Martinez Canillas, dri-devel, linux-kernel, Maxime Ripard,
Daniel Vetter, Rodrigo Vivi, Sam Ravnborg
On Tue, Oct 4, 2022 at 10:38 AM Jani Nikula <jani.nikula@linux.intel.com> wrote:
> Got any bug report with more info, or any other details to back this up?
> This is kind of thin. What's the 800 ms based on?
This issue affected several different CometLake-based Chrome OS device
designs. The details of the original report are in the Google partner
issue tracker (issue # 178169843), but I believe this requires a
Google partner account to access:
https://partnerissuetracker.corp.google.com/issues/178169843
The summary is that we were seeing these "*ERROR* LSPCON mode hasn't
settled" messages in the kernel logs followed by the display not
working at all. We increased the timeout to 500ms while investigation
continued and this reduced the number of occurrences of this issue:
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/7b2899fc1a6f9409e8075b3153baaf02c4d1fc75
The problem continued to occur on about 2% of devices even after
increasing the timeout to 500ms. The investigation continued in issue
# 188035814, with engineers from Parade and Intel involved.
Ultimately, the recommendation from Intel engineers was to increase
the timeout further:
https://partnerissuetracker.corp.google.com/issues/188035814
The timeout was then increased to 1000ms:
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/a16cfc2062e768c8e5ad8fa09b8ca127aa1ead9a
I recently ran 100 reboot trials on one device and found that the
median time for the LSPCON mode to settle was 440ms and the max was
444ms. But we know from the original reports that even after we set
the timeout to 500ms the issue continued to happen on some small
percentage of devices. So this is why I picked the larger value of
800ms.
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display/lspcon: Increase LSPCON mode settle timeout (rev2)
2022-09-15 0:46 ` Pablo Ceballos
` (5 preceding siblings ...)
(?)
@ 2022-10-13 7:50 ` Patchwork
-1 siblings, 0 replies; 14+ messages in thread
From: Patchwork @ 2022-10-13 7:50 UTC (permalink / raw)
To: Pablo Ceballos; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 8969 bytes --]
== Series Details ==
Series: drm/i915/display/lspcon: Increase LSPCON mode settle timeout (rev2)
URL : https://patchwork.freedesktop.org/series/108735/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12239 -> Patchwork_108735v2
====================================================
Summary
-------
**WARNING**
Minor unknown changes coming with Patchwork_108735v2 need to be verified
manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_108735v2, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/index.html
Participating hosts (43 -> 42)
------------------------------
Missing (1): fi-ctg-p8600
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_108735v2:
### IGT changes ###
#### Warnings ####
* igt@runner@aborted:
- fi-kbl-8809g: [FAIL][1] ([i915#4312]) -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/fi-kbl-8809g/igt@runner@aborted.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/fi-kbl-8809g/igt@runner@aborted.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@runner@aborted:
- {fi-tgl-mst}: [FAIL][3] ([i915#4312]) -> [FAIL][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/fi-tgl-mst/igt@runner@aborted.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/fi-tgl-mst/igt@runner@aborted.html
Known issues
------------
Here are the changes found in Patchwork_108735v2 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@module-reload:
- fi-apl-guc: [PASS][5] -> [DMESG-WARN][6] ([i915#180] / [i915#5904] / [i915#62]) +3 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/fi-apl-guc/igt@i915_pm_rpm@module-reload.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/fi-apl-guc/igt@i915_pm_rpm@module-reload.html
* igt@i915_selftest@live@reset:
- fi-apl-guc: [PASS][7] -> [DMESG-WARN][8] ([i915#5904]) +31 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/fi-apl-guc/igt@i915_selftest@live@reset.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/fi-apl-guc/igt@i915_selftest@live@reset.html
* igt@i915_selftest@live@slpc:
- fi-apl-guc: [PASS][9] -> [DMESG-WARN][10] ([i915#5904] / [i915#7174]) +2 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/fi-apl-guc/igt@i915_selftest@live@slpc.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/fi-apl-guc/igt@i915_selftest@live@slpc.html
* igt@kms_addfb_basic@unused-pitches:
- fi-apl-guc: [PASS][11] -> [DMESG-WARN][12] ([i915#165] / [i915#62]) +36 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/fi-apl-guc/igt@kms_addfb_basic@unused-pitches.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/fi-apl-guc/igt@kms_addfb_basic@unused-pitches.html
* igt@kms_busy@basic@flip:
- fi-apl-guc: [PASS][13] -> [DMESG-WARN][14] ([i915#165] / [i915#1982] / [i915#62])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/fi-apl-guc/igt@kms_busy@basic@flip.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/fi-apl-guc/igt@kms_busy@basic@flip.html
* igt@kms_busy@basic@modeset:
- fi-apl-guc: [PASS][15] -> [DMESG-WARN][16] ([i915#62]) +2 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/fi-apl-guc/igt@kms_busy@basic@modeset.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/fi-apl-guc/igt@kms_busy@basic@modeset.html
* igt@kms_flip@basic-flip-vs-dpms@c-dp1:
- fi-apl-guc: [PASS][17] -> [DMESG-WARN][18] ([i915#165] / [i915#180] / [i915#62]) +44 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/fi-apl-guc/igt@kms_flip@basic-flip-vs-dpms@c-dp1.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/fi-apl-guc/igt@kms_flip@basic-flip-vs-dpms@c-dp1.html
* igt@kms_flip@basic-flip-vs-wf_vblank@a-dp1:
- fi-apl-guc: [PASS][19] -> [DMESG-WARN][20] ([i915#165] / [i915#180] / [i915#1982] / [i915#62])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/fi-apl-guc/igt@kms_flip@basic-flip-vs-wf_vblank@a-dp1.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/fi-apl-guc/igt@kms_flip@basic-flip-vs-wf_vblank@a-dp1.html
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s3@smem:
- {bat-rplp-1}: [DMESG-WARN][21] ([i915#2867]) -> [PASS][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/bat-rplp-1/igt@gem_exec_suspend@basic-s3@smem.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/bat-rplp-1/igt@gem_exec_suspend@basic-s3@smem.html
* igt@i915_selftest@live@gt_heartbeat:
- fi-bxt-dsi: [DMESG-FAIL][23] ([i915#5334]) -> [PASS][24]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/fi-bxt-dsi/igt@i915_selftest@live@gt_heartbeat.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/fi-bxt-dsi/igt@i915_selftest@live@gt_heartbeat.html
* igt@i915_selftest@live@reset:
- {bat-rpls-2}: [DMESG-FAIL][25] ([i915#4983] / [i915#5828]) -> [PASS][26]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/bat-rpls-2/igt@i915_selftest@live@reset.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/bat-rpls-2/igt@i915_selftest@live@reset.html
* igt@i915_selftest@live@slpc:
- {bat-rpls-1}: [DMESG-FAIL][27] ([i915#6367]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/bat-rpls-1/igt@i915_selftest@live@slpc.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/bat-rpls-1/igt@i915_selftest@live@slpc.html
* igt@kms_pipe_crc_basic@suspend-read-crc@pipe-d-dp-3:
- {bat-dg2-11}: [FAIL][29] ([i915#6818]) -> [PASS][30]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/bat-dg2-11/igt@kms_pipe_crc_basic@suspend-read-crc@pipe-d-dp-3.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/bat-dg2-11/igt@kms_pipe_crc_basic@suspend-read-crc@pipe-d-dp-3.html
#### Warnings ####
* igt@i915_selftest@live@gt_heartbeat:
- fi-apl-guc: [DMESG-FAIL][31] ([i915#5334]) -> [DMESG-WARN][32] ([i915#5904])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#165]: https://gitlab.freedesktop.org/drm/intel/issues/165
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2867]: https://gitlab.freedesktop.org/drm/intel/issues/2867
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
[i915#5537]: https://gitlab.freedesktop.org/drm/intel/issues/5537
[i915#5828]: https://gitlab.freedesktop.org/drm/intel/issues/5828
[i915#5904]: https://gitlab.freedesktop.org/drm/intel/issues/5904
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367
[i915#6434]: https://gitlab.freedesktop.org/drm/intel/issues/6434
[i915#6559]: https://gitlab.freedesktop.org/drm/intel/issues/6559
[i915#6816]: https://gitlab.freedesktop.org/drm/intel/issues/6816
[i915#6818]: https://gitlab.freedesktop.org/drm/intel/issues/6818
[i915#7174]: https://gitlab.freedesktop.org/drm/intel/issues/7174
Build changes
-------------
* Linux: CI_DRM_12239 -> Patchwork_108735v2
CI-20190529: 20190529
CI_DRM_12239: c8ba40d43d6d1c9e457ebe91543a04a9e85b29f8 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7012: ca6f5bdd537d26692c4b1ca011b8c4f227d95703 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_108735v2: c8ba40d43d6d1c9e457ebe91543a04a9e85b29f8 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
4fb1d1bfd2bf drm/i915/display/lspcon: Increase LSPCON mode settle timeout
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/index.html
[-- Attachment #2: Type: text/html, Size: 10689 bytes --]
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/display/lspcon: Increase LSPCON mode settle timeout (rev2)
2022-09-15 0:46 ` Pablo Ceballos
` (6 preceding siblings ...)
(?)
@ 2022-10-13 9:49 ` Patchwork
-1 siblings, 0 replies; 14+ messages in thread
From: Patchwork @ 2022-10-13 9:49 UTC (permalink / raw)
To: Pablo Ceballos; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 30367 bytes --]
== Series Details ==
Series: drm/i915/display/lspcon: Increase LSPCON mode settle timeout (rev2)
URL : https://patchwork.freedesktop.org/series/108735/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12239_full -> Patchwork_108735v2_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_108735v2_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_108735v2_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Participating hosts (9 -> 9)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_108735v2_full:
### IGT changes ###
#### Possible regressions ####
* igt@drm_import_export@flink:
- shard-tglb: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-tglb2/igt@drm_import_export@flink.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-tglb5/igt@drm_import_export@flink.html
#### Warnings ####
* igt@runner@aborted:
- shard-apl: ([FAIL][3], [FAIL][4], [FAIL][5], [FAIL][6], [FAIL][7]) ([fdo#109271] / [i915#180] / [i915#3002]) -> ([FAIL][8], [FAIL][9], [FAIL][10], [FAIL][11]) ([i915#180] / [i915#3002])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-apl8/igt@runner@aborted.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-apl6/igt@runner@aborted.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-apl1/igt@runner@aborted.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-apl2/igt@runner@aborted.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-apl8/igt@runner@aborted.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl6/igt@runner@aborted.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl7/igt@runner@aborted.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl8/igt@runner@aborted.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl2/igt@runner@aborted.html
- shard-skl: ([FAIL][12], [FAIL][13], [FAIL][14]) ([i915#3002] / [i915#7066]) -> ([FAIL][15], [FAIL][16], [FAIL][17]) ([i915#3002])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-skl9/igt@runner@aborted.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-skl7/igt@runner@aborted.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-skl6/igt@runner@aborted.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl9/igt@runner@aborted.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl9/igt@runner@aborted.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl6/igt@runner@aborted.html
Known issues
------------
Here are the changes found in Patchwork_108735v2_full that come from known issues:
### CI changes ###
#### Issues hit ####
* boot:
- shard-glk: ([PASS][18], [PASS][19], [PASS][20], [PASS][21], [PASS][22], [PASS][23], [PASS][24], [PASS][25], [PASS][26], [PASS][27], [PASS][28], [PASS][29], [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], [FAIL][47], [PASS][48], [PASS][49], [PASS][50], [PASS][51], [PASS][52], [PASS][53], [PASS][54], [PASS][55], [PASS][56], [PASS][57], [PASS][58], [PASS][59], [PASS][60], [PASS][61], [PASS][62], [PASS][63], [PASS][64], [PASS][65], [PASS][66], [PASS][67]) ([i915#4392])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk1/boot.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk1/boot.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk1/boot.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk2/boot.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk2/boot.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk2/boot.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk2/boot.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk3/boot.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk3/boot.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk5/boot.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk5/boot.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk5/boot.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk6/boot.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk6/boot.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk6/boot.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk7/boot.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk7/boot.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk7/boot.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk7/boot.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk8/boot.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk8/boot.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk8/boot.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk9/boot.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk9/boot.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk9/boot.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk8/boot.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk1/boot.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk1/boot.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk1/boot.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk2/boot.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk2/boot.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk2/boot.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk2/boot.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk3/boot.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk3/boot.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk3/boot.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk5/boot.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk5/boot.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk6/boot.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk6/boot.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk6/boot.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk6/boot.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk7/boot.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk9/boot.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk9/boot.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk9/boot.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk8/boot.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk8/boot.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk7/boot.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk7/boot.html
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_exec@basic-nohangcheck:
- shard-tglb: [PASS][68] -> [FAIL][69] ([i915#6268])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-tglb5/igt@gem_ctx_exec@basic-nohangcheck.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-tglb1/igt@gem_ctx_exec@basic-nohangcheck.html
* igt@gem_exec_balancer@parallel-keep-in-fence:
- shard-iclb: [PASS][70] -> [SKIP][71] ([i915#4525])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-iclb2/igt@gem_exec_balancer@parallel-keep-in-fence.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-iclb3/igt@gem_exec_balancer@parallel-keep-in-fence.html
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-tglb: [PASS][72] -> [FAIL][73] ([i915#2842])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-tglb5/igt@gem_exec_fair@basic-none-share@rcs0.html
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-tglb2/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@gem_lmem_swapping@basic:
- shard-skl: NOTRUN -> [SKIP][74] ([fdo#109271] / [i915#4613]) +3 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl9/igt@gem_lmem_swapping@basic.html
* igt@gem_lmem_swapping@verify-random-ccs:
- shard-apl: NOTRUN -> [SKIP][75] ([fdo#109271] / [i915#4613])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl1/igt@gem_lmem_swapping@verify-random-ccs.html
* igt@gem_softpin@evict-single-offset:
- shard-apl: NOTRUN -> [FAIL][76] ([i915#4171])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl1/igt@gem_softpin@evict-single-offset.html
* igt@gem_userptr_blits@dmabuf-sync:
- shard-apl: NOTRUN -> [SKIP][77] ([fdo#109271] / [i915#3323])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl1/igt@gem_userptr_blits@dmabuf-sync.html
* igt@gen7_exec_parse@basic-allowed:
- shard-apl: NOTRUN -> [SKIP][78] ([fdo#109271]) +48 similar issues
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl1/igt@gen7_exec_parse@basic-allowed.html
* igt@i915_pm_sseu@full-enable:
- shard-skl: [PASS][79] -> [FAIL][80] ([i915#3524])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-skl1/igt@i915_pm_sseu@full-enable.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl1/igt@i915_pm_sseu@full-enable.html
* igt@i915_selftest@live@gt_heartbeat:
- shard-skl: [PASS][81] -> [DMESG-FAIL][82] ([i915#5334])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-skl10/igt@i915_selftest@live@gt_heartbeat.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl7/igt@i915_selftest@live@gt_heartbeat.html
* igt@kms_async_flips@alternate-sync-async-flip@pipe-b-edp-1:
- shard-skl: [PASS][83] -> [FAIL][84] ([i915#2521])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-skl9/igt@kms_async_flips@alternate-sync-async-flip@pipe-b-edp-1.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl7/igt@kms_async_flips@alternate-sync-async-flip@pipe-b-edp-1.html
* igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_mc_ccs:
- shard-skl: NOTRUN -> [SKIP][85] ([fdo#109271] / [i915#3886]) +8 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl10/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc:
- shard-glk: NOTRUN -> [SKIP][86] ([fdo#109271] / [i915#3886])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk8/igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-crc-sprite-planes-basic-4_tiled_dg2_rc_ccs:
- shard-glk: NOTRUN -> [SKIP][87] ([fdo#109271]) +28 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk8/igt@kms_ccs@pipe-c-crc-sprite-planes-basic-4_tiled_dg2_rc_ccs.html
* igt@kms_chamelium@hdmi-edid-change-during-suspend:
- shard-apl: NOTRUN -> [SKIP][88] ([fdo#109271] / [fdo#111827]) +1 similar issue
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl1/igt@kms_chamelium@hdmi-edid-change-during-suspend.html
* igt@kms_chamelium@hdmi-hpd-storm:
- shard-glk: NOTRUN -> [SKIP][89] ([fdo#109271] / [fdo#111827])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk8/igt@kms_chamelium@hdmi-hpd-storm.html
* igt@kms_color@ctm-0-25:
- shard-skl: NOTRUN -> [SKIP][90] ([fdo#109271] / [i915#3546])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl10/igt@kms_color@ctm-0-25.html
* igt@kms_color_chamelium@ctm-limited-range:
- shard-skl: NOTRUN -> [SKIP][91] ([fdo#109271] / [fdo#111827]) +11 similar issues
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl6/igt@kms_color_chamelium@ctm-limited-range.html
* igt@kms_content_protection@lic@pipe-a-dp-1:
- shard-apl: NOTRUN -> [INCOMPLETE][92] ([i915#7121] / [i915#7173])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl1/igt@kms_content_protection@lic@pipe-a-dp-1.html
* igt@kms_cursor_crc@cursor-suspend@pipe-a-dp-1:
- shard-apl: [PASS][93] -> [DMESG-WARN][94] ([i915#180]) +1 similar issue
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-apl3/igt@kms_cursor_crc@cursor-suspend@pipe-a-dp-1.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl2/igt@kms_cursor_crc@cursor-suspend@pipe-a-dp-1.html
* igt@kms_fbcon_fbt@psr-suspend:
- shard-skl: NOTRUN -> [FAIL][95] ([i915#4767])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl10/igt@kms_fbcon_fbt@psr-suspend.html
* igt@kms_flip@plain-flip-ts-check-interruptible@b-edp1:
- shard-skl: NOTRUN -> [FAIL][96] ([i915#2122])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl9/igt@kms_flip@plain-flip-ts-check-interruptible@b-edp1.html
* igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-32bpp-4tiledg2rcccs-downscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][97] ([i915#2672]) +1 similar issue
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-iclb3/igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-32bpp-4tiledg2rcccs-downscaling@pipe-a-default-mode.html
* igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-downscaling@pipe-a-valid-mode:
- shard-iclb: NOTRUN -> [SKIP][98] ([i915#2587] / [i915#2672]) +3 similar issues
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-iclb8/igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-downscaling@pipe-a-valid-mode.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][99] ([i915#2672] / [i915#3555]) +1 similar issue
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-default-mode.html
* igt@kms_frontbuffer_tracking@fbcpsr-suspend:
- shard-skl: NOTRUN -> [SKIP][100] ([fdo#109271]) +249 similar issues
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl10/igt@kms_frontbuffer_tracking@fbcpsr-suspend.html
* igt@kms_plane_alpha_blend@alpha-basic@pipe-a-edp-1:
- shard-skl: NOTRUN -> [FAIL][101] ([i915#4573]) +5 similar issues
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl6/igt@kms_plane_alpha_blend@alpha-basic@pipe-a-edp-1.html
* igt@kms_plane_scaling@planes-downscale-factor-0-5@pipe-a-edp-1:
- shard-iclb: [PASS][102] -> [SKIP][103] ([i915#5235]) +2 similar issues
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-iclb6/igt@kms_plane_scaling@planes-downscale-factor-0-5@pipe-a-edp-1.html
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-iclb2/igt@kms_plane_scaling@planes-downscale-factor-0-5@pipe-a-edp-1.html
* igt@kms_psr2_sf@cursor-plane-move-continuous-sf:
- shard-apl: NOTRUN -> [SKIP][104] ([fdo#109271] / [i915#658]) +1 similar issue
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl1/igt@kms_psr2_sf@cursor-plane-move-continuous-sf.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area:
- shard-skl: NOTRUN -> [SKIP][105] ([fdo#109271] / [i915#658]) +1 similar issue
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl10/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area.html
* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [PASS][106] -> [SKIP][107] ([fdo#109441])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-iclb3/igt@kms_psr@psr2_primary_page_flip.html
* igt@kms_sysfs_edid_timing:
- shard-skl: NOTRUN -> [FAIL][108] ([i915#6493])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl9/igt@kms_sysfs_edid_timing.html
* igt@kms_writeback@writeback-pixel-formats:
- shard-skl: NOTRUN -> [SKIP][109] ([fdo#109271] / [i915#2437]) +1 similar issue
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl7/igt@kms_writeback@writeback-pixel-formats.html
* igt@perf@non-zero-reason:
- shard-skl: NOTRUN -> [TIMEOUT][110] ([i915#6943] / [i915#7065])
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl9/igt@perf@non-zero-reason.html
* igt@perf@polling-parameterized:
- shard-iclb: [PASS][111] -> [FAIL][112] ([i915#5639])
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-iclb3/igt@perf@polling-parameterized.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-iclb8/igt@perf@polling-parameterized.html
* igt@sysfs_clients@pidname:
- shard-skl: NOTRUN -> [SKIP][113] ([fdo#109271] / [i915#2994]) +1 similar issue
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl9/igt@sysfs_clients@pidname.html
#### Possible fixes ####
* igt@gem_ctx_isolation@preservation-s3@bcs0:
- shard-skl: [INCOMPLETE][114] ([i915#4793] / [i915#4939]) -> [PASS][115]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-skl7/igt@gem_ctx_isolation@preservation-s3@bcs0.html
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl10/igt@gem_ctx_isolation@preservation-s3@bcs0.html
* igt@gem_exec_balancer@parallel-out-fence:
- shard-iclb: [SKIP][116] ([i915#4525]) -> [PASS][117]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-iclb7/igt@gem_exec_balancer@parallel-out-fence.html
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-iclb1/igt@gem_exec_balancer@parallel-out-fence.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [FAIL][118] ([i915#2842]) -> [PASS][119]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-tglb1/igt@gem_exec_fair@basic-pace-share@rcs0.html
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-tglb5/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_sync@basic-store-all:
- shard-skl: [FAIL][120] -> [PASS][121]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-skl3/igt@gem_sync@basic-store-all.html
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl10/igt@gem_sync@basic-store-all.html
* igt@gem_workarounds@suspend-resume-context:
- shard-apl: [DMESG-WARN][122] ([i915#180] / [i915#1982]) -> [PASS][123]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-apl8/igt@gem_workarounds@suspend-resume-context.html
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl1/igt@gem_workarounds@suspend-resume-context.html
* igt@kms_async_flips@alternate-sync-async-flip@pipe-c-edp-1:
- shard-skl: [FAIL][124] ([i915#2521]) -> [PASS][125]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-skl9/igt@kms_async_flips@alternate-sync-async-flip@pipe-c-edp-1.html
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl7/igt@kms_async_flips@alternate-sync-async-flip@pipe-c-edp-1.html
* igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size:
- shard-glk: [FAIL][126] ([i915#2346]) -> [PASS][127] +1 similar issue
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk5/igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size.html
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk7/igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size.html
* igt@kms_flip@flip-vs-blocking-wf-vblank@a-edp1:
- shard-skl: [FAIL][128] ([i915#2122]) -> [PASS][129] +1 similar issue
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-skl3/igt@kms_flip@flip-vs-blocking-wf-vblank@a-edp1.html
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl9/igt@kms_flip@flip-vs-blocking-wf-vblank@a-edp1.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1:
- shard-skl: [FAIL][130] ([i915#79]) -> [PASS][131]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-skl1/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl10/igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1.html
* igt@kms_flip_scaled_crc@flip-64bpp-linear-to-16bpp-linear-downscaling@pipe-a-default-mode:
- shard-iclb: [SKIP][132] ([i915#3555]) -> [PASS][133] +1 similar issue
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-linear-to-16bpp-linear-downscaling@pipe-a-default-mode.html
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-iclb3/igt@kms_flip_scaled_crc@flip-64bpp-linear-to-16bpp-linear-downscaling@pipe-a-default-mode.html
* igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-5@pipe-c-edp-1:
- shard-iclb: [SKIP][134] ([i915#5235]) -> [PASS][135] +2 similar issues
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-iclb2/igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-5@pipe-c-edp-1.html
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-iclb3/igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-5@pipe-c-edp-1.html
* igt@kms_psr@psr2_primary_blt:
- shard-iclb: [SKIP][136] ([fdo#109441]) -> [PASS][137] +1 similar issue
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-iclb1/igt@kms_psr@psr2_primary_blt.html
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-iclb2/igt@kms_psr@psr2_primary_blt.html
* igt@kms_vblank@pipe-c-ts-continuation-suspend:
- shard-apl: [DMESG-WARN][138] ([i915#180]) -> [PASS][139]
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-apl8/igt@kms_vblank@pipe-c-ts-continuation-suspend.html
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl8/igt@kms_vblank@pipe-c-ts-continuation-suspend.html
* igt@perf@stress-open-close:
- shard-glk: [INCOMPLETE][140] ([i915#5213]) -> [PASS][141]
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-glk6/igt@perf@stress-open-close.html
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-glk8/igt@perf@stress-open-close.html
#### Warnings ####
* igt@dmabuf@all@dma_fence_chain:
- shard-skl: [INCOMPLETE][142] ([i915#6949]) -> [INCOMPLETE][143] ([i915#6949] / [i915#7165])
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-skl6/igt@dmabuf@all@dma_fence_chain.html
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-skl9/igt@dmabuf@all@dma_fence_chain.html
* igt@kms_content_protection@legacy@pipe-a-dp-1:
- shard-apl: [INCOMPLETE][144] ([i915#1319] / [i915#7121]) -> [INCOMPLETE][145] ([i915#1319] / [i915#7121] / [i915#7173])
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-apl7/igt@kms_content_protection@legacy@pipe-a-dp-1.html
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl3/igt@kms_content_protection@legacy@pipe-a-dp-1.html
* igt@kms_content_protection@srm@pipe-a-dp-1:
- shard-apl: [INCOMPLETE][146] ([i915#7121]) -> [INCOMPLETE][147] ([i915#7121] / [i915#7173]) +2 similar issues
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-apl1/igt@kms_content_protection@srm@pipe-a-dp-1.html
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-apl7/igt@kms_content_protection@srm@pipe-a-dp-1.html
* igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-fully-sf:
- shard-iclb: [SKIP][148] ([i915#658]) -> [SKIP][149] ([i915#2920])
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-iclb1/igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-fully-sf.html
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-iclb2/igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-fully-sf.html
* igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-sf:
- shard-iclb: [SKIP][150] ([i915#2920]) -> [SKIP][151] ([i915#658]) +1 similar issue
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12239/shard-iclb2/igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-sf.html
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108735v2/shard-iclb3/igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-sf.html
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437
[i915#2521]: https://gitlab.freedesktop.org/drm/intel/issues/2521
[i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[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#3323]: https://gitlab.freedesktop.org/drm/intel/issues/3323
[i915#3524]: https://gitlab.freedesktop.org/drm/intel/issues/3524
[i915#3546]: https://gitlab.freedesktop.org/drm/intel/issues/3546
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#4171]: https://gitlab.freedesktop.org/drm/intel/issues/4171
[i915#4392]: https://gitlab.freedesktop.org/drm/intel/issues/4392
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#4573]: https://gitlab.freedesktop.org/drm/intel/issues/4573
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4767]: https://gitlab.freedesktop.org/drm/intel/issues/4767
[i915#4793]: https://gitlab.freedesktop.org/drm/intel/issues/4793
[i915#4939]: https://gitlab.freedesktop.org/drm/intel/issues/4939
[i915#5213]: https://gitlab.freedesktop.org/drm/intel/issues/5213
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
[i915#5639]: https://gitlab.freedesktop.org/drm/intel/issues/5639
[i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268
[i915#6493]: https://gitlab.freedesktop.org/drm/intel/issues/6493
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#6943]: https://gitlab.freedesktop.org/drm/intel/issues/6943
[i915#6949]: https://gitlab.freedesktop.org/drm/intel/issues/6949
[i915#7065]: https://gitlab.freedesktop.org/drm/intel/issues/7065
[i915#7066]: https://gitlab.freedesktop.org/drm/intel/issues/7066
[i915#7121]: https://gitlab.freedesktop.org/drm/intel/issues/7121
[i915#7165]: https://gitlab.freedesktop.org/drm/intel/issues/7165
[i915#7173]: https://gitlab.freedesktop.org/drm/intel/issues/7173
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
Build changes
-------------
* Linux: CI_DRM_12239 -> Patchwork_108735v2
CI-20190529: 20190529
CI_DRM_12239: c8ba40d43d6d1c9e457ebe91543a04a9e85b29f8 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7012: ca6f5bdd537d26692c4b1ca011b8c4f227d95703 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_108735v2: c8ba40d43d6d1c9e457ebe91543a04a9e85b29f8 @ 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_108735v2/index.html
[-- Attachment #2: Type: text/html, Size: 35864 bytes --]
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2022-10-13 9:49 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-15 0:46 [PATCH] drm/i915/display/lspcon: Increase LSPCON mode settle timeout Pablo Ceballos
2022-09-15 0:46 ` [Intel-gfx] " Pablo Ceballos
2022-09-15 0:46 ` Pablo Ceballos
2022-09-19 19:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-09-19 19:58 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-09-19 20:19 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-10-04 17:38 ` [PATCH] " Jani Nikula
2022-10-04 17:38 ` Jani Nikula
2022-10-04 17:38 ` [Intel-gfx] " Jani Nikula
2022-10-06 22:59 ` Pablo Ceballos
2022-10-06 22:59 ` [Intel-gfx] " Pablo Ceballos
2022-10-06 22:59 ` Pablo Ceballos
2022-10-13 7:50 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display/lspcon: Increase LSPCON mode settle timeout (rev2) Patchwork
2022-10-13 9:49 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.