dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled()
Subsystems (2)
PATCH 1/1 dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled()
If a dma_fence_array is reported signaled by a call to dma_fence_is_signaled(), it may leak the PENDING_ERROR status.
Fix this by clearing the PENDING_ERROR status if we return true in dma_fence_array_signaled().
--- drivers/dma-buf/dma-fence-array.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/dma-buf/dma-fence-array.c +5 -1
@@ -104,7 +104,11 @@ static bool dma_fence_array_signaled(struct dma_fence *fence) {struct dma_fence_array *array =to_dma_fence_array (fence); -return atomic_read (&array->num_pending) <=0 ; +if (atomic_read (&array->num_pending) >0 ) +return false; + +dma_fence_array_clear_pending_error (array); +return true; }static void dma_fence_array_release (struct dma_fence *fence)
Signature · 1 line
2.31.1
Am 29.11.21 um 08:35 schrieb Thomas Hellström:
Quoted 11 lines
If a
dma_fence_arrayis reported signaled by a call todma_fence_is_signaled(), it may leak thePENDING_ERRORstatus.Fix this by clearing the
PENDING_ERRORstatus if we return true indma_fence_array_signaled().Fixes 1f70b8b812f3 ("dma-fence: Propagate errors to dma-fence-array container")Cc Christian König <[email protected]>Cc Chris Wilson <[email protected]>Signed-off-by Thomas Hellström <[email protected]>
Quoted 21 lines
--- drivers/dma-buf/dma-fence-array.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)drivers/dma-buf/dma-fence-array.c +5
-1@@ -104,7 +104,11 @@ static bool dma_fence_array_signaled(struct dma_fence *fence) {struct dma_fence_array *array =to_dma_fence_array (fence); -return atomic_read (&array->num_pending) <=0 ; +if (atomic_read (&array->num_pending) >0 ) +return false; + +dma_fence_array_clear_pending_error (array); +return true; }static void dma_fence_array_release (struct dma_fence *fence)
Hi, Christian,
Quoted 7 lines · Christian König
Am 29.11.21 um 08:35 schrieb Thomas Hellström:
Quoted 6 lines
If a
dma_fence_arrayis reported signaled by a call todma_fence_is_signaled(), it may leak thePENDING_ERRORstatus.Fix this by clearing the
PENDING_ERRORstatus if we return true indma_fence_array_signaled().
Quoted 8 lines
Quoted 6 lines
Fixes 1f70b8b812f3 ("dma-fence: Propagate errors to dma-fence-array container")
Cc Christian König <[email protected]>Cc Chris Wilson <[email protected]>Signed-off-by Thomas Hellström <[email protected]>Reviewed-by Christian König <[email protected]>
How are the dma-buf / dma-fence patches typically merged? If i915 is the only fence->error user, could we take this through drm-intel to avoid a backmerge for upcoming i915 work?
/Thomas
Quoted 25 lines
Quoted 24 lines
---
drivers/dma-buf/dma-fence-array.c| 6 +++++-1 file changed, 5 insertions(+), 1 deletion(-)drivers/dma- renamed from drivers/dma-buf/dma-fence-array.c +0
-0
buf/dma-fence-array.c
indexd3fbd950be94..3e07f961e2f3100644drivers/dma-buf/dma-fence-array.c +0
-0@@ -104,7 +104,11 @@ static bool dma_fence_array_signaled(struct dma_fence *fence) { struct dma_fence_array *array = to_dma_fence_array(fence);
- returnatomic_read(&array->num_pending)<= 0; + if (atomic_read(&array->num_pending)> 0)
+ return false;
+
+ dma_fence_array_clear_pending_error(array); + return true;
}
static voiddma_fence_array_release(struct dma_fence *fence)
Am 29.11.21 um 13:23 schrieb Thomas Hellström:
Quoted 16 lines
Hi, Christian,
Quoted 13 lines · Christian König
Am 29.11.21 um 08:35 schrieb Thomas Hellström:
Quoted 12 lines
If a
dma_fence_arrayis reported signaled by a call todma_fence_is_signaled(), it may leak thePENDING_ERRORstatus.Fix this by clearing the
PENDING_ERRORstatus if we return true indma_fence_array_signaled().Fixes 1f70b8b812f3 ("dma-fence: Propagate errors to dma-fence-array container")
Cc Christian König <[email protected]>Cc Chris Wilson <[email protected]>Signed-off-by Thomas Hellström <[email protected]>
Quoted 4 lines
Quoted 1 line
Reviewed-by Christian König <[email protected]>How are the dma-buf / dma-fence patches typically merged? If i915 is the only
fence->erroruser, could we take this through drm-intel to avoid a backmerge for upcoming i915 work?
Well that one here looks like a bugfix to me, so either through drm-misc-fixes ore some i915 -fixes branch sounds fine to me.
If you have any new development based on that a backmerge of the -fixes into your -next branch is unavoidable anyway.
Regards,
Christian.
Quoted 28 lines
/Thomas
Quoted 23 lines
Quoted 23 lines
--- drivers/dma-buf/dma-fence-array.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)drivers/dma- renamed from drivers/dma-buf/dma-fence-array.c +0
-0
buf/dma-fence-array.c
indexd3fbd950be94..3e07f961e2f3100644drivers/dma-buf/dma-fence-array.c +5
-1@@ -104,7 +104,11 @@ static bool dma_fence_array_signaled(struct dma_fence *fence) { struct dma_fence_array *array = to_dma_fence_array(fence); - return atomic_read(&array->num_pending) <= 0; + if (atomic_read(&array->num_pending) > 0) + return false; + + dma_fence_array_clear_pending_error(array); + return true; }static void
dma_fence_array_release(struct dma_fence *fence)
Quoted 25 lines · Christian König
Am 29.11.21 um 13:23 schrieb Thomas Hellström:
Quoted 18 lines
Hi, Christian,
Quoted 15 lines · Christian König
Am 29.11.21 um 08:35 schrieb Thomas Hellström:
Quoted 14 lines
If a
dma_fence_arrayis reported signaled by a call todma_fence_is_signaled(), it may leak thePENDING_ERRORstatus.Fix this by clearing the
PENDING_ERRORstatus if we return true indma_fence_array_signaled().Fixes 1f70b8b812f3 ("dma-fence: Propagate errors to dma-fence-array container")
Cc: [email protected]
Cc: Christian König <[email protected]>
Cc: Chris Wilson <[email protected]>
Signed-off-by: Thomas Hellström <[email protected]>Quoted 5 lines
Quoted 1 line
Reviewed-by Christian König <[email protected]>How are the dma-buf / dma-fence patches typically merged? If i915 is
the onlyfence->erroruser, could we take this through drm-intel to avoid a backmerge for upcoming i915 work?
Quoted 6 lines
Well that one here looks like a bugfix to me, so either through drm-misc-fixes ore some i915 -fixes branch sounds fine to me.
If you have any new development based on that a backmerge of the - fixes
into your -next branch is unavoidable anyway.
Ok, I'll check with Joonas if I can take it through drm-intel-gt-next, since fixes are cherry-picked from that one. Patch will then appear in both the -fixes and the -next branch.
Thanks,
/Thomas
Quoted 35 lines
Regards,
Christian.Quoted 30 lines
/Thomas
Quoted 25 lines
Quoted 25 lines
---
drivers/dma-buf/dma-fence-array.c| 6 +++++-1 file changed, 5 insertions(+), 1 deletion(-)drivers/dma- renamed from drivers/dma-buf/dma-fence-array.c +0
-0
buf/dma-fence-array.c
indexd3fbd950be94..3e07f961e2f3100644drivers/dma-buf/dma-fence-array.c +0
-0@@ -104,7 +104,11 @@ static booldma_fence_array_signaled(struct
dma_fence*fence)
{
structdma_fence_array*array =to_dma_fence_array(fence);
- returnatomic_read(&array->num_pending)<= 0; + if (atomic_read(&array->num_pending)> 0)
+ return false;
+
+ dma_fence_array_clear_pending_error(array);
+ return true;
}
static voiddma_fence_array_release(struct dma_fence *fence)
Am 29.11.21 um 13:46 schrieb Thomas Hellström:
Quoted 28 lines · Christian König
Quoted 27 lines
Am 29.11.21 um 13:23 schrieb Thomas Hellström:
Quoted 18 lines
Hi, Christian,
Quoted 15 lines · Christian König
Am 29.11.21 um 08:35 schrieb Thomas Hellström:
Quoted 14 lines
If a
dma_fence_arrayis reported signaled by a call todma_fence_is_signaled(), it may leak thePENDING_ERRORstatus.Fix this by clearing the
PENDING_ERRORstatus if we return true indma_fence_array_signaled().Fixes 1f70b8b812f3 ("dma-fence: Propagate errors to dma-fence-array container")
Cc: [email protected]
Cc: Christian König <[email protected]>
Cc: Chris Wilson <[email protected]>
Signed-off-by: Thomas Hellström <[email protected]>Quoted 5 lines
Quoted 1 line
Reviewed-by Christian König <[email protected]>How are the dma-buf / dma-fence patches typically merged? If i915 is
the onlyfence->erroruser, could we take this through drm-intel to avoid a backmerge for upcoming i915 work?Well that one here looks like a bugfix to me, so either through drm-misc-fixes ore some i915 -fixes branch sounds fine to me.
Quoted 6 lines
Quoted 3 lines
If you have any new development based on that a backmerge of the - fixes
into your -next branch is unavoidable anyway.Ok, I'll check with Joonas if I can take it through drm-intel-gt-next, since fixes are cherry-picked from that one. Patch will then appear in both the -fixes and the -next branch.
Well exactly that's the stuff Daniel told me to avoid :)
But maybe your i915 workflow is somehow better handling that than the AMD workflow.
Christian.
Quoted 37 lines
Thanks,
/ThomasQuoted 31 lines
Regards,
Christian.Quoted 28 lines
/Thomas
Quoted 25 lines
Quoted 25 lines
--- drivers/dma-buf/dma-fence-array.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)drivers/dma- renamed from drivers/dma-buf/dma-fence-array.c +0
-0
buf/dma-fence-array.c
indexd3fbd950be94..3e07f961e2f3100644drivers/dma-buf/dma-fence-array.c +0
-0@@ -104,7 +104,11 @@ static booldma_fence_array_signaled(struct
dma_fence*fence)
{
structdma_fence_array*array =to_dma_fence_array(fence);- return
atomic_read(&array->num_pending)<= 0; + if (atomic_read(&array->num_pending)> 0) + return false;
+
+ dma_fence_array_clear_pending_error(array); + return true;
}static void
dma_fence_array_release(struct dma_fence *fence)
(Switching to my @linux.intel.com address)
Quoting Christian König (2021-11-29 14:55:37)
Quoted 32 lines
Am 29.11.21 um 13:46 schrieb Thomas Hellström:
Quoted 31 lines · Christian König
Quoted 30 lines
Am 29.11.21 um 13:23 schrieb Thomas Hellström:
Quoted 18 lines
Hi, Christian,
Quoted 15 lines · Christian König
Am 29.11.21 um 08:35 schrieb Thomas Hellström:
Quoted 14 lines
If a
dma_fence_arrayis reported signaled by a call todma_fence_is_signaled(), it may leak thePENDING_ERRORstatus.Fix this by clearing the
PENDING_ERRORstatus if we return true indma_fence_array_signaled().Fixes 1f70b8b812f3 ("dma-fence: Propagate errors to dma-fence-array container")
Cc: [email protected]
Cc: Christian König <[email protected]>
Cc: Chris Wilson <[email protected]>
Signed-off-by: Thomas Hellström <[email protected]>Quoted 5 lines
Quoted 1 line
Reviewed-by Christian König <[email protected]>How are the dma-buf / dma-fence patches typically merged? If i915 is
the onlyfence->erroruser, could we take this through drm-intel to avoid a backmerge for upcoming i915 work?Well that one here looks like a bugfix to me, so either through drm-misc-fixes ore some i915 -fixes branch sounds fine to me.
If you have any new development based on that a backmerge of the - fixes
into your -next branch is unavoidable anyway.
Quoted 8 lines
Quoted 3 lines
Ok, I'll check with Joonas if I can take it through drm-intel-gt-next, since fixes are cherry-picked from that one. Patch will then appear in both the -fixes and the -next branch.
Well exactly that's the stuff Daniel told me to avoid :)
But maybe your i915 workflow is somehow better handling that than the AMD workflow.
If it's a bugfix to a patch that merged through drm-misc-next, I'd always be inclined to merge the fixup using the same process (which would be drm-next-fixes).
In i915 we do always merge the patches to -next first, and never do a backmerge of -fixes (as it's a cherry-picked branch) so the workflows differ there.
Here the time between the fixup and the previous patch is so long that either way is fine with. So feel free to apply to drm-intel-gt-next.
Regards, Joonas
Quoted 40 lines
Christian.
Quoted 37 lines
Thanks,
/ThomasQuoted 31 lines
Regards,
Christian.Quoted 28 lines
/Thomas
Quoted 25 lines
Quoted 25 lines
--- drivers/dma-buf/dma-fence-array.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)drivers/dma- renamed from drivers/dma-buf/dma-fence-array.c +0
-0
buf/dma-fence-array.c
indexd3fbd950be94..3e07f961e2f3100644drivers/dma-buf/dma-fence-array.c +0
-0@@ -104,7 +104,11 @@ static booldma_fence_array_signaled(struct
dma_fence*fence)
{
structdma_fence_array*array =to_dma_fence_array(fence);- return
atomic_read(&array->num_pending)<= 0; + if (atomic_read(&array->num_pending)> 0) + return false;
+
+ dma_fence_array_clear_pending_error(array); + return true;
}static void
dma_fence_array_release(struct dma_fence *fence)
Quoted 48 lines · Joonas Lahtinen
(Switching to my @linux.intel.com address)
Quoting Christian König (2021-11-29 14:55:37)
Quoted 32 lines
Am 29.11.21 um 13:46 schrieb Thomas Hellström:
Quoted 31 lines · Christian König
Quoted 30 lines
Am 29.11.21 um 13:23 schrieb Thomas Hellström:
Quoted 18 lines
Hi, Christian,
Quoted 15 lines · Christian König
Am 29.11.21 um 08:35 schrieb Thomas Hellström:
Quoted 14 lines
If a
dma_fence_arrayis reported signaled by a call todma_fence_is_signaled(), it may leak thePENDING_ERRORstatus.Fix this by clearing the
PENDING_ERRORstatus if we return true indma_fence_array_signaled().Fixes 1f70b8b812f3 ("dma-fence: Propagate errors to dma-fence-array container")
Cc: [email protected]
Cc: Christian König <[email protected]>
Cc: Chris Wilson <[email protected]>
Signed-off-by: Thomas Hellström <[email protected]>Quoted 5 lines
Quoted 1 line
Reviewed-by Christian König <[email protected]>How are the dma-buf / dma-fence patches typically merged? If i915 is
the onlyfence->erroruser, could we take this through drm-intel to avoid a backmerge for upcoming i915 work?Well that one here looks like a bugfix to me, so either through drm-misc-fixes ore some i915 -fixes branch sounds fine to me.
If you have any new development based on that a backmerge of the - fixes
into your -next branch is unavoidable anyway.Quoted 8 lines
Quoted 3 lines
Ok, I'll check with Joonas if I can take it through drm-intel-gt-next, since fixes are cherry-picked from that one. Patch will then appear in both the -fixes and the -next branch.
Well exactly that's the stuff Daniel told me to avoid :)
But maybe your i915 workflow is somehow better handling that than the AMD workflow.
If it's a bugfix to a patch that merged through drm-misc-next, I'd always be inclined to merge the fixup using the same process (which would be drm-next-fixes).
Quoted 6 lines
In i915 we do always merge the patches to -next first, and never do a backmerge of -fixes (as it's a cherry-picked branch) so the workflows differ there.
Here the time between the fixup and the previous patch is so long that either way is fine with. So feel free to apply to drm-intel-gt-next.
To make this clear and avoid confusion: drm-misc and drm-intel work differently for bugfixes.
drm-intel has paid maintainers who take care of cherry-picking and testing and making sure nothing is lost.
drm-misc is all volunteers, so committers need to make sure stuff ends up in the right place.
Hence different rules.
-Daniel
Quoted 47 lines
Regards, Joonas
Quoted 40 lines
Christian.
Quoted 37 lines
Thanks,
/ThomasQuoted 31 lines
Regards,
Christian.Quoted 28 lines
/Thomas
Quoted 25 lines
Quoted 25 lines
--- drivers/dma-buf/dma-fence-array.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)drivers/dma- renamed from drivers/dma-buf/dma-fence-array.c +0
-0
buf/dma-fence-array.c
indexd3fbd950be94..3e07f961e2f3100644drivers/dma-buf/dma-fence-array.c +0
-0@@ -104,7 +104,11 @@ static booldma_fence_array_signaled(struct
dma_fence*fence)
{
structdma_fence_array*array =to_dma_fence_array(fence);- return
atomic_read(&array->num_pending)<= 0; + if (atomic_read(&array->num_pending)> 0) + return false;
+
+ dma_fence_array_clear_pending_error(array); + return true;
}static void
dma_fence_array_release(struct dma_fence *fence)_______________________________________________
Linaro-mm-sig mailing list
[email protected]
https://lists.linaro.org/mailman/listinfo/linaro-mm-sig
Signature · 3 lines
Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled()
In reply to Thomas Hellström== Series Details ==
== Series Details ==
Series: dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled()
URL : https://patchwork.freedesktop.org/series/97362/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10935 -> Patchwork_21692
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/index.html
Participating hosts (36 -> 32)
------------------------------
Additional (1): fi-skl-6600u
Missing (5): fi-kbl-soraka bat-dg1-6 bat-adlp-6 bat-jsl-2 bat-jsl-1
Known issues
------------
Here are the changes found in Patchwork_21692 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_cs_nop@sync-fork-gfx0:
- fi-skl-6600u: NOTRUN -> [SKIP][1] ([fdo#109271]) +23 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/fi-skl-6600u/igt@amdgpu/[email protected]
* igt@gem_huc_copy@huc-copy:
- fi-skl-6600u: NOTRUN -> [SKIP][2] ([fdo#109271] / [i915#2190])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/fi-skl-6600u/igt@[email protected]
* igt@gem_lmem_swapping@verify-random:
- fi-skl-6600u: NOTRUN -> [SKIP][3] ([fdo#109271] / [i915#4613]) +3 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/fi-skl-6600u/igt@[email protected]
* igt@kms_chamelium@vga-edid-read:
- fi-skl-6600u: NOTRUN -> [SKIP][4] ([fdo#109271] / [fdo#111827]) +8 similar issues
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/fi-skl-6600u/igt@[email protected]
* igt@kms_frontbuffer_tracking@basic:
- fi-cml-u2: [PASS][5] -> [DMESG-WARN][6] ([i915#4269])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/fi-cml-u2/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/fi-cml-u2/igt@[email protected]
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-skl-6600u: NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#533])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/fi-skl-6600u/igt@[email protected]
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#4269]: https://gitlab.freedesktop.org/drm/intel/issues/4269
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
Build changes
-------------
* Linux: CI_DRM_10935 -> Patchwork_21692
CI-20190529: 20190529
CI_DRM_10935: 5c0966fffb522e45d76063065b3b915cff246b23 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6293: bf11f87c27ad1cec3e60bd31c23080d19aa093f3 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_21692: be15ec0983143cfc7011d2be1e3ea3be5970a80d @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
be15ec098314 dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled()
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/index.html
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled()
In reply to Thomas Hellström== Series Details ==
== Series Details ==
Series: dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled()
URL : https://patchwork.freedesktop.org/series/97362/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_10935_full -> Patchwork_21692_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Known issues
------------
Here are the changes found in Patchwork_21692_full that come from known issues:
### CI changes ###
#### Possible fixes ####
* boot:
- shard-glk: ([PASS][1], [FAIL][2], [PASS][3], [PASS][4], [PASS][5], [PASS][6], [PASS][7], [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], [PASS][13], [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19], [PASS][20], [PASS][21], [PASS][22], [PASS][23], [PASS][24], [PASS][25]) ([i915#4392]) -> ([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], [PASS][47], [PASS][48], [PASS][49], [PASS][50])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk9/boot.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk9/boot.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk9/boot.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk8/boot.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk8/boot.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk8/boot.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk7/boot.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk7/boot.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk6/boot.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk6/boot.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk6/boot.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk5/boot.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk5/boot.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk5/boot.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk4/boot.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk4/boot.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk4/boot.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk3/boot.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk3/boot.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk2/boot.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk2/boot.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk2/boot.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk1/boot.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk1/boot.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk1/boot.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk9/boot.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk9/boot.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk9/boot.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk8/boot.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk8/boot.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk8/boot.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk7/boot.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk7/boot.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk6/boot.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk6/boot.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk6/boot.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk5/boot.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk5/boot.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk4/boot.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk4/boot.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk4/boot.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk3/boot.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk3/boot.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk3/boot.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk2/boot.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk2/boot.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk2/boot.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk1/boot.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk1/boot.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk1/boot.html
### IGT changes ###
#### Issues hit ####
* igt@gem_create@create-massive:
- shard-kbl: NOTRUN -> [DMESG-WARN][51] ([i915#3002])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl3/igt@[email protected]
- shard-tglb: NOTRUN -> [DMESG-WARN][52] ([i915#3002])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb1/igt@[email protected]
* igt@gem_ctx_isolation@preservation-s3@bcs0:
- shard-tglb: [PASS][53] -> [INCOMPLETE][54] ([i915#456])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-tglb6/igt@gem_ctx_isolation@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb7/igt@gem_ctx_isolation@[email protected]
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-kbl: [PASS][55] -> [FAIL][56] ([i915#2842])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-kbl6/igt@gem_exec_fair@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl6/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@bcs0:
- shard-iclb: [PASS][57] -> [FAIL][58] ([i915#2842])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-iclb2/igt@gem_exec_fair@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-iclb4/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-kbl: [PASS][59] -> [SKIP][60] ([fdo#109271])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-kbl7/igt@gem_exec_fair@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl3/igt@gem_exec_fair@[email protected]
- shard-tglb: [PASS][61] -> [FAIL][62] ([i915#2842]) +1 similar issue
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-tglb8/igt@gem_exec_fair@[email protected]
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb1/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [PASS][63] -> [FAIL][64] ([i915#2849])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-iclb7/igt@gem_exec_fair@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-iclb6/igt@gem_exec_fair@[email protected]
* igt@gem_lmem_swapping@heavy-multi:
- shard-apl: NOTRUN -> [SKIP][65] ([fdo#109271] / [i915#4613]) +2 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl2/igt@[email protected]
* igt@gem_lmem_swapping@heavy-verify-multi:
- shard-glk: NOTRUN -> [SKIP][66] ([fdo#109271] / [i915#4613])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk8/igt@[email protected]
* igt@gem_lmem_swapping@smem-oom:
- shard-kbl: NOTRUN -> [SKIP][67] ([fdo#109271] / [i915#4613]) +2 similar issues
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl1/igt@[email protected]
* igt@gem_pxp@verify-pxp-key-change-after-suspend-resume:
- shard-tglb: NOTRUN -> [SKIP][68] ([i915#4270])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb8/igt@[email protected]
* igt@gem_userptr_blits@input-checking:
- shard-skl: NOTRUN -> [DMESG-WARN][69] ([i915#3002])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-skl6/igt@[email protected]
* igt@gem_userptr_blits@vma-merge:
- shard-apl: NOTRUN -> [FAIL][70] ([i915#3318])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl1/igt@[email protected]
* igt@gen9_exec_parse@allowed-single:
- shard-skl: [PASS][71] -> [DMESG-WARN][72] ([i915#1436] / [i915#716])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-skl7/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-skl4/igt@[email protected]
* igt@i915_pm_rpm@system-suspend-execbuf:
- shard-tglb: [PASS][73] -> [INCOMPLETE][74] ([i915#2411] / [i915#456] / [i915#750])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-tglb8/igt@[email protected]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb7/igt@[email protected]
* igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-180-hflip:
- shard-apl: NOTRUN -> [SKIP][75] ([fdo#109271] / [i915#3777]) +2 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl1/igt@[email protected]
* igt@kms_big_fb@y-tiled-32bpp-rotate-0:
- shard-glk: [PASS][76] -> [DMESG-WARN][77] ([i915#118])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk4/igt@[email protected]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk2/igt@[email protected]
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip:
- shard-kbl: NOTRUN -> [SKIP][78] ([fdo#109271] / [i915#3777]) +1 similar issue
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl1/igt@[email protected]
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip:
- shard-kbl: NOTRUN -> [SKIP][79] ([fdo#109271]) +94 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl7/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-hflip:
- shard-skl: NOTRUN -> [SKIP][80] ([fdo#109271] / [i915#3777])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-skl6/igt@[email protected]
* igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
- shard-skl: NOTRUN -> [SKIP][81] ([fdo#109271] / [i915#3886]) +1 similar issue
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-skl6/igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-b-missing-ccs-buffer-y_tiled_gen12_mc_ccs:
- shard-glk: NOTRUN -> [SKIP][82] ([fdo#109271] / [i915#3886]) +1 similar issue
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk8/igt@kms_ccs@pipe-b-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][83] ([i915#3689]) +1 similar issue
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb8/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_ccs.html
* igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs:
- shard-kbl: NOTRUN -> [SKIP][84] ([fdo#109271] / [i915#3886]) +3 similar issues
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl3/igt@kms_ccs@pipe-b-random-ccs-data-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc:
- shard-apl: NOTRUN -> [SKIP][85] ([fdo#109271] / [i915#3886]) +4 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl6/igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-random-ccs-data-y_tiled_gen12_rc_ccs_cc:
- shard-snb: NOTRUN -> [SKIP][86] ([fdo#109271]) +7 similar issues
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-snb5/igt@kms_ccs@pipe-c-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_cdclk@mode-transition:
- shard-apl: NOTRUN -> [SKIP][87] ([fdo#109271]) +122 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl2/igt@[email protected]
* igt@kms_cdclk@plane-scaling:
- shard-tglb: NOTRUN -> [SKIP][88] ([i915#3742])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb8/igt@[email protected]
* igt@kms_chamelium@hdmi-hpd-enable-disable-mode:
- shard-snb: NOTRUN -> [SKIP][89] ([fdo#109271] / [fdo#111827])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-snb5/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-ctm-blue-to-red:
- shard-kbl: NOTRUN -> [SKIP][90] ([fdo#109271] / [fdo#111827]) +7 similar issues
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl3/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-ctm-limited-range:
- shard-apl: NOTRUN -> [SKIP][91] ([fdo#109271] / [fdo#111827]) +8 similar issues
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl2/igt@[email protected]
* igt@kms_color_chamelium@pipe-c-ctm-blue-to-red:
- shard-glk: NOTRUN -> [SKIP][92] ([fdo#109271] / [fdo#111827]) +2 similar issues
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk8/igt@[email protected]
* igt@kms_color_chamelium@pipe-c-gamma:
- shard-tglb: NOTRUN -> [SKIP][93] ([fdo#109284] / [fdo#111827])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb8/igt@[email protected]
* igt@kms_content_protection@atomic-dpms:
- shard-kbl: NOTRUN -> [TIMEOUT][94] ([i915#1319])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl6/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-apl: NOTRUN -> [TIMEOUT][95] ([i915#1319]) +1 similar issue
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl1/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-32x32-sliding:
- shard-tglb: NOTRUN -> [SKIP][96] ([i915#3319])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb8/igt@[email protected]
* igt@kms_flip@2x-busy-flip:
- shard-tglb: NOTRUN -> [SKIP][97] ([fdo#111825]) +4 similar issues
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb8/igt@[email protected]
* igt@kms_flip@2x-flip-vs-expired-vblank@ab-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][98] -> [FAIL][99] ([i915#79])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk9/igt@kms_flip@[email protected]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk1/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
- shard-kbl: [PASS][100] -> [DMESG-WARN][101] ([i915#180]) +5 similar issues
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-kbl3/igt@kms_flip@[email protected]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl6/igt@kms_flip@[email protected]
- shard-apl: [PASS][102] -> [DMESG-WARN][103] ([i915#180]) +2 similar issues
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-apl6/igt@kms_flip@[email protected]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl4/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend@a-edp1:
- shard-tglb: [PASS][104] -> [INCOMPLETE][105] ([i915#2411] / [i915#456])
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-tglb3/igt@kms_flip@[email protected]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb7/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-ts-check-interruptible@c-edp1:
- shard-skl: [PASS][106] -> [FAIL][107] ([i915#2122])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-skl7/igt@kms_flip@[email protected]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-skl10/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbc-2p-pri-indfb-multidraw:
- shard-glk: [PASS][108] -> [FAIL][109] ([i915#1888] / [i915#2546])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-glk5/igt@[email protected]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk6/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-suspend:
- shard-glk: NOTRUN -> [SKIP][110] ([fdo#109271]) +30 similar issues
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk8/igt@[email protected]
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- shard-kbl: NOTRUN -> [SKIP][111] ([fdo#109271] / [i915#533])
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl7/igt@[email protected]
* igt@kms_pipe_crc_basic@read-crc-pipe-d:
- shard-glk: NOTRUN -> [SKIP][112] ([fdo#109271] / [i915#533])
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk8/igt@[email protected]
* igt@kms_pipe_crc_basic@read-crc-pipe-d-frame-sequence:
- shard-apl: NOTRUN -> [SKIP][113] ([fdo#109271] / [i915#533])
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl6/igt@[email protected]
* igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes:
- shard-kbl: [PASS][114] -> [INCOMPLETE][115] ([i915#3614])
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-kbl1/igt@kms_plane@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl4/igt@kms_plane@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
- shard-apl: NOTRUN -> [FAIL][116] ([fdo#108145] / [i915#265]) +2 similar issues
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl2/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-constant-alpha-min:
- shard-skl: [PASS][117] -> [FAIL][118] ([fdo#108145] / [i915#265])
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-skl9/igt@[email protected]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-skl7/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-alpha-7efc:
- shard-kbl: NOTRUN -> [FAIL][119] ([fdo#108145] / [i915#265])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl7/igt@[email protected]
* igt@kms_plane_lowres@pipe-d-tiling-none:
- shard-tglb: NOTRUN -> [SKIP][120] ([i915#3536])
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb8/igt@[email protected]
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-3:
- shard-apl: NOTRUN -> [SKIP][121] ([fdo#109271] / [i915#658]) +2 similar issues
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl1/igt@[email protected]
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-1:
- shard-kbl: NOTRUN -> [SKIP][122] ([fdo#109271] / [i915#658]) +1 similar issue
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl1/igt@[email protected]
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-4:
- shard-glk: NOTRUN -> [SKIP][123] ([fdo#109271] / [i915#658])
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-glk8/igt@[email protected]
* igt@kms_psr@psr2_no_drrs:
- shard-tglb: NOTRUN -> [FAIL][124] ([i915#132] / [i915#3467]) +1 similar issue
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb8/igt@kms_psr@psr2_no_drrs.html
* igt@kms_psr@psr2_primary_mmap_gtt:
- shard-skl: NOTRUN -> [SKIP][125] ([fdo#109271]) +8 similar issues
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-skl6/igt@kms_psr@psr2_primary_mmap_gtt.html
* igt@kms_psr@psr2_sprite_mmap_gtt:
- shard-iclb: [PASS][126] -> [SKIP][127] ([fdo#109441]) +1 similar issue
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-iclb4/igt@kms_psr@psr2_sprite_mmap_gtt.html
* igt@kms_writeback@writeback-check-output:
- shard-apl: NOTRUN -> [SKIP][128] ([fdo#109271] / [i915#2437]) +1 similar issue
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl2/igt@[email protected]
- shard-kbl: NOTRUN -> [SKIP][129] ([fdo#109271] / [i915#2437])
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl7/igt@[email protected]
* igt@nouveau_crc@pipe-b-source-outp-complete:
- shard-tglb: NOTRUN -> [SKIP][130] ([i915#2530])
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb8/igt@[email protected]
* igt@sysfs_clients@pidname:
- shard-apl: NOTRUN -> [SKIP][131] ([fdo#109271] / [i915#2994]) +1 similar issue
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl2/igt@[email protected]
* igt@sysfs_clients@recycle-many:
- shard-kbl: NOTRUN -> [SKIP][132] ([fdo#109271] / [i915#2994]) +1 similar issue
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl1/igt@[email protected]
* igt@sysfs_heartbeat_interval@mixed@rcs0:
- shard-skl: [PASS][133] -> [FAIL][134] ([i915#1731]) +1 similar issue
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-skl9/igt@sysfs_heartbeat_interval@[email protected]
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-skl7/igt@sysfs_heartbeat_interval@[email protected]
#### Possible fixes ####
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-iclb: [FAIL][135] ([i915#2842]) -> [PASS][136]
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-iclb1/igt@gem_exec_fair@[email protected]
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-iclb3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@bcs0:
- shard-tglb: [FAIL][137] ([i915#2842]) -> [PASS][138] +1 similar issue
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-tglb8/igt@gem_exec_fair@[email protected]
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb1/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@vcs0:
- shard-kbl: [FAIL][139] ([i915#2842]) -> [PASS][140]
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-kbl7/igt@gem_exec_fair@[email protected]
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-kbl3/igt@gem_exec_fair@[email protected]
* igt@gem_workarounds@suspend-resume-context:
- shard-tglb: [INCOMPLETE][141] ([i915#456]) -> [PASS][142]
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-tglb7/igt@[email protected]
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb1/igt@[email protected]
* igt@i915_pm_rpm@pm-tiling:
- {shard-rkl}: ([SKIP][143], [SKIP][144]) ([fdo#109308]) -> [PASS][145]
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-rkl-4/igt@[email protected]
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-rkl-2/igt@[email protected]
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-rkl-6/igt@[email protected]
* igt@i915_selftest@live@hangcheck:
- shard-snb: [INCOMPLETE][146] ([i915#3921]) -> [PASS][147]
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-snb6/igt@i915_selftest@[email protected]
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-snb5/igt@i915_selftest@[email protected]
* igt@kms_big_fb@y-tiled-64bpp-rotate-180:
- {shard-rkl}: ([SKIP][148], [SKIP][149]) ([i915#1845]) -> [PASS][150]
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-rkl-4/igt@[email protected]
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-rkl-2/igt@[email protected]
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-rkl-6/igt@[email protected]
* igt@kms_color@pipe-a-ctm-0-75:
- {shard-rkl}: [SKIP][151] ([i915#1149] / [i915#4098]) -> [PASS][152]
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-rkl-4/igt@[email protected]
[152]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-rkl-6/igt@[email protected]
* igt@kms_color@pipe-b-ctm-max:
- {shard-rkl}: [SKIP][153] ([i915#1149] / [i915#1849] / [i915#4070]) -> [PASS][154]
[153]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-rkl-2/igt@[email protected]
[154]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-rkl-6/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-64x21-onscreen:
- {shard-rkl}: [SKIP][155] ([fdo#112022] / [i915#4070]) -> [PASS][156] +1 similar issue
[155]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-rkl-2/igt@[email protected]
[156]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-rkl-6/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- {shard-rkl}: [SKIP][157] ([fdo#112022]) -> [PASS][158]
[157]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-rkl-4/igt@[email protected]
[158]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-rkl-6/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-apl: [DMESG-WARN][159] ([i915#180]) -> [PASS][160] +4 similar issues
[159]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-apl8/igt@[email protected]
[160]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-apl2/igt@[email protected]
- shard-tglb: [INCOMPLETE][161] ([i915#2411] / [i915#456]) -> [PASS][162]
[161]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-tglb7/igt@[email protected]
[162]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb8/igt@[email protected]
* igt@kms_cursor_crc@pipe-d-cursor-suspend:
- shard-tglb: [INCOMPLETE][163] ([i915#4211]) -> [PASS][164]
[163]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-tglb7/igt@[email protected]
[164]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-tglb8/igt@[email protected]
* igt@kms_cursor_edge_walk@pipe-b-64x64-right-edge:
- {shard-rkl}: [SKIP][165] ([i915#1849] / [i915#4070]) -> [PASS][166]
[165]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_10935/shard-rkl-2/igt@[email protected]
[166]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/shard-rkl-6/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21692/index.html