* [Intel-gfx] [PATCH] drm/i915: Call i915_gem_suspend() only after display is turned off
@ 2022-06-17 19:06 José Roberto de Souza
2022-06-17 19:28 ` Matt Roper
` (2 more replies)
0 siblings, 3 replies; 8+ messages in thread
From: José Roberto de Souza @ 2022-06-17 19:06 UTC (permalink / raw)
To: intel-gfx
Gem buffers could still be in use by display after i915_gem_suspend()
is executed so there is chances that i915_gem_flush_free_objects()
will be being executed at the same time that
intel_runtime_pm_driver_release() is executed printing warnings about
wakerefs will being held.
So here only calling i915_gem_suspend() and by consequence
i915_gem_drain_freed_objects() only after display is down making
sure all buffers are freed.
Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
---
drivers/gpu/drm/i915/i915_driver.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
index d26dcca7e654a..4227675dd1cfe 100644
--- a/drivers/gpu/drm/i915/i915_driver.c
+++ b/drivers/gpu/drm/i915/i915_driver.c
@@ -1067,8 +1067,6 @@ void i915_driver_shutdown(struct drm_i915_private *i915)
intel_runtime_pm_disable(&i915->runtime_pm);
intel_power_domains_disable(i915);
- i915_gem_suspend(i915);
-
if (HAS_DISPLAY(i915)) {
drm_kms_helper_poll_disable(&i915->drm);
@@ -1085,6 +1083,8 @@ void i915_driver_shutdown(struct drm_i915_private *i915)
intel_dmc_ucode_suspend(i915);
+ i915_gem_suspend(i915);
+
/*
* The only requirement is to reboot with display DC states disabled,
* for now leaving all display power wells in the INIT power domain
--
2.36.1
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915: Call i915_gem_suspend() only after display is turned off
2022-06-17 19:06 [Intel-gfx] [PATCH] drm/i915: Call i915_gem_suspend() only after display is turned off José Roberto de Souza
@ 2022-06-17 19:28 ` Matt Roper
2022-06-21 17:03 ` Souza, Jose
2022-06-17 21:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-06-18 12:05 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2 siblings, 1 reply; 8+ messages in thread
From: Matt Roper @ 2022-06-17 19:28 UTC (permalink / raw)
To: José Roberto de Souza; +Cc: intel-gfx
On Fri, Jun 17, 2022 at 12:06:29PM -0700, José Roberto de Souza wrote:
> Gem buffers could still be in use by display after i915_gem_suspend()
> is executed so there is chances that i915_gem_flush_free_objects()
> will be being executed at the same time that
> intel_runtime_pm_driver_release() is executed printing warnings about
> wakerefs will being held.
By the same logic do we need to adjust i915_driver_remove() too?
Matt
>
> So here only calling i915_gem_suspend() and by consequence
> i915_gem_drain_freed_objects() only after display is down making
> sure all buffers are freed.
>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> ---
> drivers/gpu/drm/i915/i915_driver.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> index d26dcca7e654a..4227675dd1cfe 100644
> --- a/drivers/gpu/drm/i915/i915_driver.c
> +++ b/drivers/gpu/drm/i915/i915_driver.c
> @@ -1067,8 +1067,6 @@ void i915_driver_shutdown(struct drm_i915_private *i915)
> intel_runtime_pm_disable(&i915->runtime_pm);
> intel_power_domains_disable(i915);
>
> - i915_gem_suspend(i915);
> -
> if (HAS_DISPLAY(i915)) {
> drm_kms_helper_poll_disable(&i915->drm);
>
> @@ -1085,6 +1083,8 @@ void i915_driver_shutdown(struct drm_i915_private *i915)
>
> intel_dmc_ucode_suspend(i915);
>
> + i915_gem_suspend(i915);
> +
> /*
> * The only requirement is to reboot with display DC states disabled,
> * for now leaving all display power wells in the INIT power domain
> --
> 2.36.1
>
--
Matt Roper
Graphics Software Engineer
VTT-OSGC Platform Enablement
Intel Corporation
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Call i915_gem_suspend() only after display is turned off
2022-06-17 19:06 [Intel-gfx] [PATCH] drm/i915: Call i915_gem_suspend() only after display is turned off José Roberto de Souza
2022-06-17 19:28 ` Matt Roper
@ 2022-06-17 21:11 ` Patchwork
2022-06-18 12:05 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2022-06-17 21:11 UTC (permalink / raw)
To: José Roberto de Souza; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 7922 bytes --]
== Series Details ==
Series: drm/i915: Call i915_gem_suspend() only after display is turned off
URL : https://patchwork.freedesktop.org/series/105306/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11776 -> Patchwork_105306v1
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/index.html
Participating hosts (35 -> 35)
------------------------------
Additional (1): fi-cml-u2
Missing (1): fi-bdw-samus
Known issues
------------
Here are the changes found in Patchwork_105306v1 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_fence@basic-busy@bcs0:
- fi-cml-u2: NOTRUN -> [SKIP][1] ([i915#1208]) +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-cml-u2/igt@gem_exec_fence@basic-busy@bcs0.html
* igt@gem_huc_copy@huc-copy:
- fi-cml-u2: NOTRUN -> [SKIP][2] ([i915#2190])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-cml-u2/igt@gem_huc_copy@huc-copy.html
* igt@gem_lmem_swapping@verify-random:
- fi-cml-u2: NOTRUN -> [SKIP][3] ([i915#4613]) +3 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-cml-u2/igt@gem_lmem_swapping@verify-random.html
* igt@i915_selftest@live@hangcheck:
- fi-hsw-g3258: [PASS][4] -> [INCOMPLETE][5] ([i915#3303] / [i915#4785])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/fi-hsw-g3258/igt@i915_selftest@live@hangcheck.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-hsw-g3258/igt@i915_selftest@live@hangcheck.html
* igt@i915_selftest@live@requests:
- fi-pnv-d510: [PASS][6] -> [DMESG-FAIL][7] ([i915#4528])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/fi-pnv-d510/igt@i915_selftest@live@requests.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-pnv-d510/igt@i915_selftest@live@requests.html
* igt@i915_suspend@basic-s3-without-i915:
- fi-rkl-11600: [PASS][8] -> [INCOMPLETE][9] ([i915#5982])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/fi-rkl-11600/igt@i915_suspend@basic-s3-without-i915.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-rkl-11600/igt@i915_suspend@basic-s3-without-i915.html
* igt@kms_chamelium@vga-hpd-fast:
- fi-cml-u2: NOTRUN -> [SKIP][10] ([fdo#109284] / [fdo#111827]) +8 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-cml-u2/igt@kms_chamelium@vga-hpd-fast.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy:
- fi-cml-u2: NOTRUN -> [SKIP][11] ([fdo#109278]) +1 similar issue
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-cml-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html
* igt@kms_flip@basic-flip-vs-modeset@a-edp1:
- fi-tgl-u2: [PASS][12] -> [DMESG-WARN][13] ([i915#402])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/fi-tgl-u2/igt@kms_flip@basic-flip-vs-modeset@a-edp1.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-tgl-u2/igt@kms_flip@basic-flip-vs-modeset@a-edp1.html
* igt@kms_force_connector_basic@force-load-detect:
- fi-cml-u2: NOTRUN -> [SKIP][14] ([fdo#109285])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-cml-u2/igt@kms_force_connector_basic@force-load-detect.html
* igt@kms_frontbuffer_tracking@basic:
- fi-cml-u2: NOTRUN -> [DMESG-WARN][15] ([i915#4269])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-cml-u2/igt@kms_frontbuffer_tracking@basic.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-cml-u2: NOTRUN -> [SKIP][16] ([fdo#109278] / [i915#533])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-cml-u2/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
* igt@kms_setmode@basic-clone-single-crtc:
- fi-cml-u2: NOTRUN -> [SKIP][17] ([i915#3555])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-cml-u2/igt@kms_setmode@basic-clone-single-crtc.html
* igt@prime_vgem@basic-userptr:
- fi-cml-u2: NOTRUN -> [SKIP][18] ([fdo#109295] / [i915#3301])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-cml-u2/igt@prime_vgem@basic-userptr.html
* igt@runner@aborted:
- fi-pnv-d510: NOTRUN -> [FAIL][19] ([fdo#109271] / [i915#2403] / [i915#4312])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-pnv-d510/igt@runner@aborted.html
- fi-hsw-g3258: NOTRUN -> [FAIL][20] ([fdo#109271] / [i915#4312])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-hsw-g3258/igt@runner@aborted.html
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s0@smem:
- {fi-ehl-2}: [DMESG-WARN][21] ([i915#5122]) -> [PASS][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/fi-ehl-2/igt@gem_exec_suspend@basic-s0@smem.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-ehl-2/igt@gem_exec_suspend@basic-s0@smem.html
#### Warnings ####
* igt@i915_selftest@live@hangcheck:
- fi-hsw-4770: [INCOMPLETE][23] ([i915#3303] / [i915#4785]) -> [INCOMPLETE][24] ([i915#4785])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/fi-hsw-4770/igt@i915_selftest@live@hangcheck.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#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1208]: https://gitlab.freedesktop.org/drm/intel/issues/1208
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2403]: https://gitlab.freedesktop.org/drm/intel/issues/2403
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3303]: https://gitlab.freedesktop.org/drm/intel/issues/3303
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#4269]: https://gitlab.freedesktop.org/drm/intel/issues/4269
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4528]: https://gitlab.freedesktop.org/drm/intel/issues/4528
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4785]: https://gitlab.freedesktop.org/drm/intel/issues/4785
[i915#5122]: https://gitlab.freedesktop.org/drm/intel/issues/5122
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5982]: https://gitlab.freedesktop.org/drm/intel/issues/5982
Build changes
-------------
* Linux: CI_DRM_11776 -> Patchwork_105306v1
CI-20190529: 20190529
CI_DRM_11776: ac17a5249380aaabe5d1eaebd9b3a2eedc08ccdc @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6536: e3de4d32b7a509635fbff4d5131c05a7767699f7 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_105306v1: ac17a5249380aaabe5d1eaebd9b3a2eedc08ccdc @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
f933129bd4d9 drm/i915: Call i915_gem_suspend() only after display is turned off
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/index.html
[-- Attachment #2: Type: text/html, Size: 9356 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Call i915_gem_suspend() only after display is turned off
2022-06-17 19:06 [Intel-gfx] [PATCH] drm/i915: Call i915_gem_suspend() only after display is turned off José Roberto de Souza
2022-06-17 19:28 ` Matt Roper
2022-06-17 21:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
@ 2022-06-18 12:05 ` Patchwork
2 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2022-06-18 12:05 UTC (permalink / raw)
To: José Roberto de Souza; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 29204 bytes --]
== Series Details ==
Series: drm/i915: Call i915_gem_suspend() only after display is turned off
URL : https://patchwork.freedesktop.org/series/105306/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11776_full -> Patchwork_105306v1_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_105306v1_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_105306v1_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_105306v1_full:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@coherency:
- shard-skl: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl6/igt@i915_selftest@live@coherency.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl9/igt@i915_selftest@live@coherency.html
Known issues
------------
Here are the changes found in Patchwork_105306v1_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@preservation-s3@bcs0:
- shard-skl: [PASS][3] -> [INCOMPLETE][4] ([i915#4793])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl6/igt@gem_ctx_isolation@preservation-s3@bcs0.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl7/igt@gem_ctx_isolation@preservation-s3@bcs0.html
* igt@gem_eio@unwedge-stress:
- shard-skl: [PASS][5] -> [TIMEOUT][6] ([i915#3063])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl1/igt@gem_eio@unwedge-stress.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl6/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_balancer@parallel-keep-in-fence:
- shard-iclb: [PASS][7] -> [SKIP][8] ([i915#4525])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb4/igt@gem_exec_balancer@parallel-keep-in-fence.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb3/igt@gem_exec_balancer@parallel-keep-in-fence.html
* igt@gem_exec_balancer@parallel-ordering:
- shard-kbl: NOTRUN -> [FAIL][9] ([i915#6117])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl6/igt@gem_exec_balancer@parallel-ordering.html
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: NOTRUN -> [FAIL][10] ([i915#6141])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl4/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-kbl: [PASS][11] -> [FAIL][12] ([i915#2842])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-kbl6/igt@gem_exec_fair@basic-none-rrul@rcs0.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl3/igt@gem_exec_fair@basic-none-rrul@rcs0.html
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-iclb: [PASS][13] -> [FAIL][14] ([i915#2842])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb6/igt@gem_exec_fair@basic-none-share@rcs0.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb3/igt@gem_exec_fair@basic-none-share@rcs0.html
- shard-apl: [PASS][15] -> [SKIP][16] ([fdo#109271])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-apl1/igt@gem_exec_fair@basic-none-share@rcs0.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-apl2/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@gem_exec_fair@basic-none-vip@rcs0:
- shard-glk: [PASS][17] -> [FAIL][18] ([i915#2842])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-glk5/igt@gem_exec_fair@basic-none-vip@rcs0.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-glk9/igt@gem_exec_fair@basic-none-vip@rcs0.html
* igt@gem_exec_fair@basic-none@bcs0:
- shard-tglb: [PASS][19] -> [FAIL][20] ([i915#2842]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-tglb2/igt@gem_exec_fair@basic-none@bcs0.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-tglb8/igt@gem_exec_fair@basic-none@bcs0.html
* igt@gem_exec_suspend@basic-s3@smem:
- shard-apl: [PASS][21] -> [DMESG-WARN][22] ([i915#180]) +2 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-apl6/igt@gem_exec_suspend@basic-s3@smem.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-apl6/igt@gem_exec_suspend@basic-s3@smem.html
* igt@gem_lmem_swapping@parallel-multi:
- shard-kbl: NOTRUN -> [SKIP][23] ([fdo#109271] / [i915#4613]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl7/igt@gem_lmem_swapping@parallel-multi.html
* igt@gem_pread@exhaustion:
- shard-kbl: NOTRUN -> [WARN][24] ([i915#2658])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl4/igt@gem_pread@exhaustion.html
* igt@gen9_exec_parse@allowed-single:
- shard-apl: [PASS][25] -> [DMESG-WARN][26] ([i915#5566] / [i915#716])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-apl8/igt@gen9_exec_parse@allowed-single.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-apl1/igt@gen9_exec_parse@allowed-single.html
* igt@i915_suspend@forcewake:
- shard-skl: [PASS][27] -> [INCOMPLETE][28] ([i915#4817])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl6/igt@i915_suspend@forcewake.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl1/igt@i915_suspend@forcewake.html
* igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-async-flip:
- shard-skl: NOTRUN -> [FAIL][29] ([i915#3763])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl10/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-async-flip.html
* igt@kms_ccs@pipe-c-crc-primary-basic-y_tiled_gen12_rc_ccs_cc:
- shard-kbl: NOTRUN -> [SKIP][30] ([fdo#109271] / [i915#3886]) +11 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl4/igt@kms_ccs@pipe-c-crc-primary-basic-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-missing-ccs-buffer-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][31] ([fdo#109271] / [i915#3886])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-apl3/igt@kms_ccs@pipe-c-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html
* igt@kms_chamelium@hdmi-audio:
- shard-kbl: NOTRUN -> [SKIP][32] ([fdo#109271] / [fdo#111827]) +17 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl4/igt@kms_chamelium@hdmi-audio.html
* igt@kms_color_chamelium@pipe-a-ctm-limited-range:
- shard-skl: NOTRUN -> [SKIP][33] ([fdo#109271] / [fdo#111827]) +1 similar issue
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl4/igt@kms_color_chamelium@pipe-a-ctm-limited-range.html
* igt@kms_color_chamelium@pipe-b-ctm-green-to-red:
- shard-apl: NOTRUN -> [SKIP][34] ([fdo#109271] / [fdo#111827])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-apl2/igt@kms_color_chamelium@pipe-b-ctm-green-to-red.html
* igt@kms_cursor_crc@pipe-c-cursor-max-size-onscreen:
- shard-kbl: NOTRUN -> [SKIP][35] ([fdo#109271]) +201 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl4/igt@kms_cursor_crc@pipe-c-cursor-max-size-onscreen.html
* igt@kms_cursor_legacy@flip-vs-cursor-varying-size:
- shard-skl: [PASS][36] -> [FAIL][37] ([i915#2346])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl9/igt@kms_cursor_legacy@flip-vs-cursor-varying-size.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl4/igt@kms_cursor_legacy@flip-vs-cursor-varying-size.html
* igt@kms_cursor_legacy@pipe-d-single-bo:
- shard-kbl: NOTRUN -> [SKIP][38] ([fdo#109271] / [i915#533])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl7/igt@kms_cursor_legacy@pipe-d-single-bo.html
* igt@kms_fbcon_fbt@psr-suspend:
- shard-skl: [PASS][39] -> [FAIL][40] ([i915#4767])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl7/igt@kms_fbcon_fbt@psr-suspend.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl4/igt@kms_fbcon_fbt@psr-suspend.html
* igt@kms_flip@flip-vs-suspend-interruptible@b-dp1:
- shard-apl: NOTRUN -> [DMESG-WARN][41] ([i915#180]) +2 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-apl2/igt@kms_flip@flip-vs-suspend-interruptible@b-dp1.html
* igt@kms_flip@flip-vs-suspend@a-edp1:
- shard-skl: [PASS][42] -> [INCOMPLETE][43] ([i915#4839])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl4/igt@kms_flip@flip-vs-suspend@a-edp1.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl1/igt@kms_flip@flip-vs-suspend@a-edp1.html
* igt@kms_frontbuffer_tracking@psr-indfb-scaledprimary:
- shard-skl: [PASS][44] -> [DMESG-WARN][45] ([i915#1982])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl10/igt@kms_frontbuffer_tracking@psr-indfb-scaledprimary.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl10/igt@kms_frontbuffer_tracking@psr-indfb-scaledprimary.html
* igt@kms_hdr@bpc-switch-dpms@pipe-a-dp-1:
- shard-kbl: NOTRUN -> [FAIL][46] ([i915#1188])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl6/igt@kms_hdr@bpc-switch-dpms@pipe-a-dp-1.html
* igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes:
- shard-kbl: [PASS][47] -> [DMESG-WARN][48] ([i915#180]) +3 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-kbl4/igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl6/igt@kms_plane@plane-panning-bottom-right-suspend@pipe-a-planes.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
- shard-kbl: NOTRUN -> [FAIL][49] ([fdo#108145] / [i915#265])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl7/igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb.html
* igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-b-edp-1:
- shard-iclb: [PASS][50] -> [SKIP][51] ([i915#5235]) +2 similar issues
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb8/igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-b-edp-1.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb2/igt@kms_plane_scaling@planes-upscale-20x20-downscale-factor-0-5@pipe-b-edp-1.html
* igt@kms_psr2_sf@overlay-plane-update-continuous-sf:
- shard-kbl: NOTRUN -> [SKIP][52] ([fdo#109271] / [i915#658]) +2 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl6/igt@kms_psr2_sf@overlay-plane-update-continuous-sf.html
* igt@kms_psr@psr2_sprite_plane_onoff:
- shard-iclb: [PASS][53] -> [SKIP][54] ([fdo#109441]) +2 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb2/igt@kms_psr@psr2_sprite_plane_onoff.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb8/igt@kms_psr@psr2_sprite_plane_onoff.html
* igt@kms_psr_stress_test@flip-primary-invalidate-overlay:
- shard-iclb: [PASS][55] -> [SKIP][56] ([i915#5519])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb3/igt@kms_psr_stress_test@flip-primary-invalidate-overlay.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb7/igt@kms_psr_stress_test@flip-primary-invalidate-overlay.html
* igt@kms_writeback@writeback-check-output:
- shard-kbl: NOTRUN -> [SKIP][57] ([fdo#109271] / [i915#2437])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl7/igt@kms_writeback@writeback-check-output.html
- shard-apl: NOTRUN -> [SKIP][58] ([fdo#109271] / [i915#2437])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-apl3/igt@kms_writeback@writeback-check-output.html
* igt@prime_nv_pcopy@test3_4:
- shard-apl: NOTRUN -> [SKIP][59] ([fdo#109271]) +40 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-apl2/igt@prime_nv_pcopy@test3_4.html
* igt@prime_vgem@fence-read-hang:
- shard-skl: NOTRUN -> [SKIP][60] ([fdo#109271]) +5 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl10/igt@prime_vgem@fence-read-hang.html
* igt@sysfs_clients@fair-7:
- shard-kbl: NOTRUN -> [SKIP][61] ([fdo#109271] / [i915#2994]) +2 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl7/igt@sysfs_clients@fair-7.html
- shard-apl: NOTRUN -> [SKIP][62] ([fdo#109271] / [i915#2994]) +1 similar issue
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-apl3/igt@sysfs_clients@fair-7.html
#### Possible fixes ####
* igt@gem_ctx_persistence@many-contexts:
- shard-kbl: [INCOMPLETE][63] ([i915#3593]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-kbl3/igt@gem_ctx_persistence@many-contexts.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl4/igt@gem_ctx_persistence@many-contexts.html
* igt@gem_exec_balancer@parallel-out-fence:
- shard-iclb: [SKIP][65] ([i915#4525]) -> [PASS][66] +2 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb5/igt@gem_exec_balancer@parallel-out-fence.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb4/igt@gem_exec_balancer@parallel-out-fence.html
* igt@gem_exec_fair@basic-none@vcs0:
- shard-kbl: [FAIL][67] ([i915#2842]) -> [PASS][68] +3 similar issues
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-kbl7/igt@gem_exec_fair@basic-none@vcs0.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl4/igt@gem_exec_fair@basic-none@vcs0.html
- shard-apl: [FAIL][69] ([i915#2842]) -> [PASS][70] +1 similar issue
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-apl7/igt@gem_exec_fair@basic-none@vcs0.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-apl4/igt@gem_exec_fair@basic-none@vcs0.html
* igt@gem_exec_fair@basic-pace@vcs0:
- shard-glk: [FAIL][71] ([i915#2842]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-glk1/igt@gem_exec_fair@basic-pace@vcs0.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-glk9/igt@gem_exec_fair@basic-pace@vcs0.html
* igt@gem_exec_fair@basic-pace@vcs1:
- shard-tglb: [FAIL][73] ([i915#2842]) -> [PASS][74] +2 similar issues
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-tglb1/igt@gem_exec_fair@basic-pace@vcs1.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-tglb6/igt@gem_exec_fair@basic-pace@vcs1.html
* igt@gem_exec_whisper@basic-queues-all:
- shard-glk: [DMESG-WARN][75] ([i915#118]) -> [PASS][76] +1 similar issue
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-glk4/igt@gem_exec_whisper@basic-queues-all.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-glk4/igt@gem_exec_whisper@basic-queues-all.html
* igt@gem_huc_copy@huc-copy:
- shard-tglb: [SKIP][77] ([i915#2190]) -> [PASS][78]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-tglb7/igt@gem_huc_copy@huc-copy.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-tglb5/igt@gem_huc_copy@huc-copy.html
* igt@gen9_exec_parse@allowed-single:
- shard-skl: [DMESG-WARN][79] ([i915#5566] / [i915#716]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl10/igt@gen9_exec_parse@allowed-single.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl10/igt@gen9_exec_parse@allowed-single.html
* igt@i915_module_load@reload-with-fault-injection:
- shard-skl: [DMESG-WARN][81] ([i915#1982]) -> [PASS][82] +1 similar issue
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl1/igt@i915_module_load@reload-with-fault-injection.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl6/igt@i915_module_load@reload-with-fault-injection.html
* igt@i915_pm_dc@dc6-dpms:
- shard-iclb: [FAIL][83] ([i915#454]) -> [PASS][84]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb3/igt@i915_pm_dc@dc6-dpms.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb5/igt@i915_pm_dc@dc6-dpms.html
* igt@i915_pm_dc@dc9-dpms:
- shard-iclb: [SKIP][85] ([i915#4281]) -> [PASS][86]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb3/igt@i915_pm_dc@dc9-dpms.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb7/igt@i915_pm_dc@dc9-dpms.html
* igt@i915_selftest@live@hangcheck:
- shard-tglb: [DMESG-WARN][87] ([i915#5591]) -> [PASS][88]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-tglb2/igt@i915_selftest@live@hangcheck.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-tglb1/igt@i915_selftest@live@hangcheck.html
* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-apl: [DMESG-WARN][89] ([i915#180]) -> [PASS][90] +1 similar issue
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-apl8/igt@i915_suspend@fence-restore-tiled2untiled.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-apl2/igt@i915_suspend@fence-restore-tiled2untiled.html
* igt@kms_async_flips@alternate-sync-async-flip@pipe-c-edp-1:
- shard-skl: [FAIL][91] ([i915#2521]) -> [PASS][92]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl10/igt@kms_async_flips@alternate-sync-async-flip@pipe-c-edp-1.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl10/igt@kms_async_flips@alternate-sync-async-flip@pipe-c-edp-1.html
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-kbl: [DMESG-WARN][93] ([i915#180]) -> [PASS][94] +4 similar issues
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-kbl6/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl4/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
* igt@kms_flip@2x-plain-flip-fb-recreate-interruptible@ab-hdmi-a1-hdmi-a2:
- shard-glk: [FAIL][95] ([i915#2122]) -> [PASS][96]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-glk9/igt@kms_flip@2x-plain-flip-fb-recreate-interruptible@ab-hdmi-a1-hdmi-a2.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-glk6/igt@kms_flip@2x-plain-flip-fb-recreate-interruptible@ab-hdmi-a1-hdmi-a2.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1:
- shard-skl: [FAIL][97] ([i915#79]) -> [PASS][98]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl10/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl10/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1.html
* igt@kms_flip@plain-flip-fb-recreate@a-edp1:
- shard-skl: [FAIL][99] ([i915#2122]) -> [PASS][100] +3 similar issues
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl10/igt@kms_flip@plain-flip-fb-recreate@a-edp1.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl10/igt@kms_flip@plain-flip-fb-recreate@a-edp1.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling:
- shard-iclb: [SKIP][101] ([i915#3701]) -> [PASS][102] +1 similar issue
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb8/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling.html
* igt@kms_hdr@bpc-switch@pipe-a-dp-1:
- shard-kbl: [FAIL][103] ([i915#1188]) -> [PASS][104]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-kbl3/igt@kms_hdr@bpc-switch@pipe-a-dp-1.html
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-kbl1/igt@kms_hdr@bpc-switch@pipe-a-dp-1.html
* igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-pixel-formats@pipe-b-edp-1:
- shard-iclb: [SKIP][105] ([i915#5176]) -> [PASS][106] +1 similar issue
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb3/igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-pixel-formats@pipe-b-edp-1.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb5/igt@kms_plane_scaling@plane-scaler-with-clipping-clamping-pixel-formats@pipe-b-edp-1.html
* igt@kms_plane_scaling@planes-downscale-factor-0-5@pipe-a-edp-1:
- shard-iclb: [SKIP][107] ([i915#5235]) -> [PASS][108] +2 similar issues
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb2/igt@kms_plane_scaling@planes-downscale-factor-0-5@pipe-a-edp-1.html
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb6/igt@kms_plane_scaling@planes-downscale-factor-0-5@pipe-a-edp-1.html
* igt@kms_psr2_su@frontbuffer-xrgb8888:
- shard-iclb: [SKIP][109] ([fdo#109642] / [fdo#111068] / [i915#658]) -> [PASS][110]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb6/igt@kms_psr2_su@frontbuffer-xrgb8888.html
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb2/igt@kms_psr2_su@frontbuffer-xrgb8888.html
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [SKIP][111] ([fdo#109441]) -> [PASS][112] +2 similar issues
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb8/igt@kms_psr@psr2_primary_mmap_cpu.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_psr_stress_test@flip-primary-invalidate-overlay:
- shard-tglb: [SKIP][113] ([i915#5519]) -> [PASS][114]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-tglb6/igt@kms_psr_stress_test@flip-primary-invalidate-overlay.html
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-tglb3/igt@kms_psr_stress_test@flip-primary-invalidate-overlay.html
#### Warnings ####
* igt@gem_exec_balancer@parallel-ordering:
- shard-iclb: [SKIP][115] ([i915#4525]) -> [FAIL][116] ([i915#6117])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb5/igt@gem_exec_balancer@parallel-ordering.html
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb4/igt@gem_exec_balancer@parallel-ordering.html
* igt@gem_exec_fair@basic-none@rcs0:
- shard-tglb: [SKIP][117] ([i915#2848]) -> [FAIL][118] ([i915#2842])
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-tglb2/igt@gem_exec_fair@basic-none@rcs0.html
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-tglb8/igt@gem_exec_fair@basic-none@rcs0.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-spr-indfb-draw-pwrite:
- shard-skl: [SKIP][119] ([fdo#109271] / [i915#1888]) -> [SKIP][120] ([fdo#109271])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-skl7/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-spr-indfb-draw-pwrite.html
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-skl4/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-spr-indfb-draw-pwrite.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area:
- shard-iclb: [SKIP][121] ([fdo#111068] / [i915#658]) -> [SKIP][122] ([i915#2920])
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11776/shard-iclb8/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area.html
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105306v1/shard-iclb2/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area.html
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#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#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2848]: https://gitlab.freedesktop.org/drm/intel/issues/2848
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[i915#3063]: https://gitlab.freedesktop.org/drm/intel/issues/3063
[i915#3593]: https://gitlab.freedesktop.org/drm/intel/issues/3593
[i915#3701]: https://gitlab.freedesktop.org/drm/intel/issues/3701
[i915#3763]: https://gitlab.freedesktop.org/drm/intel/issues/3763
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#4281]: https://gitlab.freedesktop.org/drm/intel/issues/4281
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[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#4817]: https://gitlab.freedesktop.org/drm/intel/issues/4817
[i915#4839]: https://gitlab.freedesktop.org/drm/intel/issues/4839
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5519]: https://gitlab.freedesktop.org/drm/intel/issues/5519
[i915#5566]: https://gitlab.freedesktop.org/drm/intel/issues/5566
[i915#5591]: https://gitlab.freedesktop.org/drm/intel/issues/5591
[i915#6117]: https://gitlab.freedesktop.org/drm/intel/issues/6117
[i915#6141]: https://gitlab.freedesktop.org/drm/intel/issues/6141
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
Build changes
-------------
* Linux: CI_DRM_11776 -> Patchwork_105306v1
CI-20190529: 20190529
CI_DRM_11776: ac17a5249380aaabe5d1eaebd9b3a2eedc08ccdc @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6536: e3de4d32b7a509635fbff4d5131c05a7767699f7 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_105306v1: ac17a5249380aaabe5d1eaebd9b3a2eedc08ccdc @ 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_105306v1/index.html
[-- Attachment #2: Type: text/html, Size: 34732 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915: Call i915_gem_suspend() only after display is turned off
2022-06-17 19:28 ` Matt Roper
@ 2022-06-21 17:03 ` Souza, Jose
2022-06-22 22:19 ` Matt Roper
0 siblings, 1 reply; 8+ messages in thread
From: Souza, Jose @ 2022-06-21 17:03 UTC (permalink / raw)
To: Roper, Matthew D; +Cc: intel-gfx
On Fri, 2022-06-17 at 12:28 -0700, Matt Roper wrote:
> On Fri, Jun 17, 2022 at 12:06:29PM -0700, José Roberto de Souza wrote:
> > Gem buffers could still be in use by display after i915_gem_suspend()
> > is executed so there is chances that i915_gem_flush_free_objects()
> > will be being executed at the same time that
> > intel_runtime_pm_driver_release() is executed printing warnings about
> > wakerefs will being held.
>
> By the same logic do we need to adjust i915_driver_remove() too?
Nope, all display buffers are freed in i915_driver_unregister() call chain:
i915_driver_remove()
i915_driver_unregister()
intel_display_driver_unregister()
drm_atomic_helper_shutdown()
i915_gem_suspend()
i915_gem_drain_freed_objects()
Only FBC compressed framebuffer is freed after that but that will not cause any warnings as it is allocated from stolen memory.
>
>
> Matt
>
> >
> > So here only calling i915_gem_suspend() and by consequence
> > i915_gem_drain_freed_objects() only after display is down making
> > sure all buffers are freed.
> >
> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_driver.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> > index d26dcca7e654a..4227675dd1cfe 100644
> > --- a/drivers/gpu/drm/i915/i915_driver.c
> > +++ b/drivers/gpu/drm/i915/i915_driver.c
> > @@ -1067,8 +1067,6 @@ void i915_driver_shutdown(struct drm_i915_private *i915)
> > intel_runtime_pm_disable(&i915->runtime_pm);
> > intel_power_domains_disable(i915);
> >
> > - i915_gem_suspend(i915);
> > -
> > if (HAS_DISPLAY(i915)) {
> > drm_kms_helper_poll_disable(&i915->drm);
> >
> > @@ -1085,6 +1083,8 @@ void i915_driver_shutdown(struct drm_i915_private *i915)
> >
> > intel_dmc_ucode_suspend(i915);
> >
> > + i915_gem_suspend(i915);
> > +
> > /*
> > * The only requirement is to reboot with display DC states disabled,
> > * for now leaving all display power wells in the INIT power domain
> > --
> > 2.36.1
> >
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915: Call i915_gem_suspend() only after display is turned off
2022-06-21 17:03 ` Souza, Jose
@ 2022-06-22 22:19 ` Matt Roper
2022-06-23 14:48 ` Souza, Jose
0 siblings, 1 reply; 8+ messages in thread
From: Matt Roper @ 2022-06-22 22:19 UTC (permalink / raw)
To: Souza, Jose; +Cc: intel-gfx
On Tue, Jun 21, 2022 at 10:03:04AM -0700, Souza, Jose wrote:
> On Fri, 2022-06-17 at 12:28 -0700, Matt Roper wrote:
> > On Fri, Jun 17, 2022 at 12:06:29PM -0700, José Roberto de Souza wrote:
> > > Gem buffers could still be in use by display after i915_gem_suspend()
> > > is executed so there is chances that i915_gem_flush_free_objects()
> > > will be being executed at the same time that
> > > intel_runtime_pm_driver_release() is executed printing warnings about
> > > wakerefs will being held.
> >
> > By the same logic do we need to adjust i915_driver_remove() too?
>
> Nope, all display buffers are freed in i915_driver_unregister() call chain:
>
>
> i915_driver_remove()
> i915_driver_unregister()
> intel_display_driver_unregister()
> drm_atomic_helper_shutdown()
> i915_gem_suspend()
> i915_gem_drain_freed_objects()
>
>
> Only FBC compressed framebuffer is freed after that but that will not cause any warnings as it is allocated from stolen memory.
Okay sounds good; thanks for checking.
I'm still having a bit of trouble understanding your description of the
issue in the commit message though:
"...so there is chances that i915_gem_flush_free_objects() will
be being executed at the same time that
intel_runtime_pm_driver_release()..."
I'm not super familiar with the driver teardown paths, or the memory
management cleanup details. Intuitively it makes sense that we should
clean up memory management (GEM) only after we've torn down display so
that all objects that were used by framebuffers are out of circulation.
But from a cursory view, it looks like i915_gem_suspend() is mostly
concerned with quiescing the GT and cleaning up PPGTT (which doesn't
impact display since all of its buffers are in the GGTT).
Is the problem arising from i915->mm.free_work still doing asynchronous
work to actually release the unused objects at the same time we're
tearing down runtime PM later? If so does swapping the order of the
gem_suspend and display disable here actually prevent that from
happening or does it just make the race less likely by helping some
objects free up earlier?
Matt
>
> >
> >
> > Matt
> >
> > >
> > > So here only calling i915_gem_suspend() and by consequence
> > > i915_gem_drain_freed_objects() only after display is down making
> > > sure all buffers are freed.
> > >
> > > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > > ---
> > > drivers/gpu/drm/i915/i915_driver.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> > > index d26dcca7e654a..4227675dd1cfe 100644
> > > --- a/drivers/gpu/drm/i915/i915_driver.c
> > > +++ b/drivers/gpu/drm/i915/i915_driver.c
> > > @@ -1067,8 +1067,6 @@ void i915_driver_shutdown(struct drm_i915_private *i915)
> > > intel_runtime_pm_disable(&i915->runtime_pm);
> > > intel_power_domains_disable(i915);
> > >
> > > - i915_gem_suspend(i915);
> > > -
> > > if (HAS_DISPLAY(i915)) {
> > > drm_kms_helper_poll_disable(&i915->drm);
> > >
> > > @@ -1085,6 +1083,8 @@ void i915_driver_shutdown(struct drm_i915_private *i915)
> > >
> > > intel_dmc_ucode_suspend(i915);
> > >
> > > + i915_gem_suspend(i915);
> > > +
> > > /*
> > > * The only requirement is to reboot with display DC states disabled,
> > > * for now leaving all display power wells in the INIT power domain
> > > --
> > > 2.36.1
> > >
> >
>
--
Matt Roper
Graphics Software Engineer
VTT-OSGC Platform Enablement
Intel Corporation
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915: Call i915_gem_suspend() only after display is turned off
2022-06-22 22:19 ` Matt Roper
@ 2022-06-23 14:48 ` Souza, Jose
2022-06-23 18:06 ` Matt Roper
0 siblings, 1 reply; 8+ messages in thread
From: Souza, Jose @ 2022-06-23 14:48 UTC (permalink / raw)
To: Roper, Matthew D; +Cc: intel-gfx
On Wed, 2022-06-22 at 15:19 -0700, Matt Roper wrote:
> On Tue, Jun 21, 2022 at 10:03:04AM -0700, Souza, Jose wrote:
> > On Fri, 2022-06-17 at 12:28 -0700, Matt Roper wrote:
> > > On Fri, Jun 17, 2022 at 12:06:29PM -0700, José Roberto de Souza wrote:
> > > > Gem buffers could still be in use by display after i915_gem_suspend()
> > > > is executed so there is chances that i915_gem_flush_free_objects()
> > > > will be being executed at the same time that
> > > > intel_runtime_pm_driver_release() is executed printing warnings about
> > > > wakerefs will being held.
> > >
> > > By the same logic do we need to adjust i915_driver_remove() too?
> >
> > Nope, all display buffers are freed in i915_driver_unregister() call chain:
> >
> >
> > i915_driver_remove()
> > i915_driver_unregister()
> > intel_display_driver_unregister()
> > drm_atomic_helper_shutdown()
> > i915_gem_suspend()
> > i915_gem_drain_freed_objects()
> >
> >
> > Only FBC compressed framebuffer is freed after that but that will not cause any warnings as it is allocated from stolen memory.
>
> Okay sounds good; thanks for checking.
>
> I'm still having a bit of trouble understanding your description of the
> issue in the commit message though:
>
> "...so there is chances that i915_gem_flush_free_objects() will
> be being executed at the same time that
> intel_runtime_pm_driver_release()..."
>
> I'm not super familiar with the driver teardown paths, or the memory
> management cleanup details. Intuitively it makes sense that we should
> clean up memory management (GEM) only after we've torn down display so
> that all objects that were used by framebuffers are out of circulation.
> But from a cursory view, it looks like i915_gem_suspend() is mostly
> concerned with quiescing the GT and cleaning up PPGTT (which doesn't
> impact display since all of its buffers are in the GGTT).
>
> Is the problem arising from i915->mm.free_work still doing asynchronous
> work to actually release the unused objects at the same time we're
> tearing down runtime PM later? If so does swapping the order of the
> gem_suspend and display disable here actually prevent that from
> happening or does it just make the race less likely by helping some
> objects free up earlier?
So when the last reference of a gem object is removed it is added to the mm.free_list list and mm.free_work is queued to actually free the object.
i915_gem_drain_freed_objects() flushes the mm.free_work.
If any other gem object has its last reference removed after i915_gem_suspend()/i915_gem_drain_freed_objects() the warning in
intel_runtime_pm_driver_release() can happen as the mm.free_work could be running at the same time.
But when pci_driver.remove() is called, probably all file descriptors attached to this device have been closed and the functions called after
i915_gem_suspend() will not free any gem object, so I don't believe we will have any more warnings.
>
>
> Matt
>
> >
> > >
> > >
> > > Matt
> > >
> > > >
> > > > So here only calling i915_gem_suspend() and by consequence
> > > > i915_gem_drain_freed_objects() only after display is down making
> > > > sure all buffers are freed.
> > > >
> > > > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > > > ---
> > > > drivers/gpu/drm/i915/i915_driver.c | 4 ++--
> > > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> > > > index d26dcca7e654a..4227675dd1cfe 100644
> > > > --- a/drivers/gpu/drm/i915/i915_driver.c
> > > > +++ b/drivers/gpu/drm/i915/i915_driver.c
> > > > @@ -1067,8 +1067,6 @@ void i915_driver_shutdown(struct drm_i915_private *i915)
> > > > intel_runtime_pm_disable(&i915->runtime_pm);
> > > > intel_power_domains_disable(i915);
> > > >
> > > > - i915_gem_suspend(i915);
> > > > -
> > > > if (HAS_DISPLAY(i915)) {
> > > > drm_kms_helper_poll_disable(&i915->drm);
> > > >
> > > > @@ -1085,6 +1083,8 @@ void i915_driver_shutdown(struct drm_i915_private *i915)
> > > >
> > > > intel_dmc_ucode_suspend(i915);
> > > >
> > > > + i915_gem_suspend(i915);
> > > > +
> > > > /*
> > > > * The only requirement is to reboot with display DC states disabled,
> > > > * for now leaving all display power wells in the INIT power domain
> > > > --
> > > > 2.36.1
> > > >
> > >
> >
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915: Call i915_gem_suspend() only after display is turned off
2022-06-23 14:48 ` Souza, Jose
@ 2022-06-23 18:06 ` Matt Roper
0 siblings, 0 replies; 8+ messages in thread
From: Matt Roper @ 2022-06-23 18:06 UTC (permalink / raw)
To: Souza, Jose; +Cc: intel-gfx
On Thu, Jun 23, 2022 at 07:48:32AM -0700, Souza, Jose wrote:
> On Wed, 2022-06-22 at 15:19 -0700, Matt Roper wrote:
> > On Tue, Jun 21, 2022 at 10:03:04AM -0700, Souza, Jose wrote:
> > > On Fri, 2022-06-17 at 12:28 -0700, Matt Roper wrote:
> > > > On Fri, Jun 17, 2022 at 12:06:29PM -0700, José Roberto de Souza wrote:
> > > > > Gem buffers could still be in use by display after i915_gem_suspend()
> > > > > is executed so there is chances that i915_gem_flush_free_objects()
> > > > > will be being executed at the same time that
> > > > > intel_runtime_pm_driver_release() is executed printing warnings about
> > > > > wakerefs will being held.
> > > >
> > > > By the same logic do we need to adjust i915_driver_remove() too?
> > >
> > > Nope, all display buffers are freed in i915_driver_unregister() call chain:
> > >
> > >
> > > i915_driver_remove()
> > > i915_driver_unregister()
> > > intel_display_driver_unregister()
> > > drm_atomic_helper_shutdown()
> > > i915_gem_suspend()
> > > i915_gem_drain_freed_objects()
> > >
> > >
> > > Only FBC compressed framebuffer is freed after that but that will not cause any warnings as it is allocated from stolen memory.
> >
> > Okay sounds good; thanks for checking.
> >
> > I'm still having a bit of trouble understanding your description of the
> > issue in the commit message though:
> >
> > "...so there is chances that i915_gem_flush_free_objects() will
> > be being executed at the same time that
> > intel_runtime_pm_driver_release()..."
> >
> > I'm not super familiar with the driver teardown paths, or the memory
> > management cleanup details. Intuitively it makes sense that we should
> > clean up memory management (GEM) only after we've torn down display so
> > that all objects that were used by framebuffers are out of circulation.
> > But from a cursory view, it looks like i915_gem_suspend() is mostly
> > concerned with quiescing the GT and cleaning up PPGTT (which doesn't
> > impact display since all of its buffers are in the GGTT).
> >
> > Is the problem arising from i915->mm.free_work still doing asynchronous
> > work to actually release the unused objects at the same time we're
> > tearing down runtime PM later? If so does swapping the order of the
> > gem_suspend and display disable here actually prevent that from
> > happening or does it just make the race less likely by helping some
> > objects free up earlier?
>
> So when the last reference of a gem object is removed it is added to the mm.free_list list and mm.free_work is queued to actually free the object.
> i915_gem_drain_freed_objects() flushes the mm.free_work.
>
> If any other gem object has its last reference removed after i915_gem_suspend()/i915_gem_drain_freed_objects() the warning in
> intel_runtime_pm_driver_release() can happen as the mm.free_work could be running at the same time.
>
> But when pci_driver.remove() is called, probably all file descriptors attached to this device have been closed and the functions called after
> i915_gem_suspend() will not free any gem object, so I don't believe we will have any more warnings.
Okay, thanks for explaining, makes sense. You might want to add some of
this extra explanation to the commit message too for future reference,
but either way,
Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
>
> >
> >
> > Matt
> >
> > >
> > > >
> > > >
> > > > Matt
> > > >
> > > > >
> > > > > So here only calling i915_gem_suspend() and by consequence
> > > > > i915_gem_drain_freed_objects() only after display is down making
> > > > > sure all buffers are freed.
> > > > >
> > > > > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > > > > ---
> > > > > drivers/gpu/drm/i915/i915_driver.c | 4 ++--
> > > > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > > > >
> > > > > diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> > > > > index d26dcca7e654a..4227675dd1cfe 100644
> > > > > --- a/drivers/gpu/drm/i915/i915_driver.c
> > > > > +++ b/drivers/gpu/drm/i915/i915_driver.c
> > > > > @@ -1067,8 +1067,6 @@ void i915_driver_shutdown(struct drm_i915_private *i915)
> > > > > intel_runtime_pm_disable(&i915->runtime_pm);
> > > > > intel_power_domains_disable(i915);
> > > > >
> > > > > - i915_gem_suspend(i915);
> > > > > -
> > > > > if (HAS_DISPLAY(i915)) {
> > > > > drm_kms_helper_poll_disable(&i915->drm);
> > > > >
> > > > > @@ -1085,6 +1083,8 @@ void i915_driver_shutdown(struct drm_i915_private *i915)
> > > > >
> > > > > intel_dmc_ucode_suspend(i915);
> > > > >
> > > > > + i915_gem_suspend(i915);
> > > > > +
> > > > > /*
> > > > > * The only requirement is to reboot with display DC states disabled,
> > > > > * for now leaving all display power wells in the INIT power domain
> > > > > --
> > > > > 2.36.1
> > > > >
> > > >
> > >
> >
>
--
Matt Roper
Graphics Software Engineer
VTT-OSGC Platform Enablement
Intel Corporation
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2022-06-23 18:06 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-17 19:06 [Intel-gfx] [PATCH] drm/i915: Call i915_gem_suspend() only after display is turned off José Roberto de Souza
2022-06-17 19:28 ` Matt Roper
2022-06-21 17:03 ` Souza, Jose
2022-06-22 22:19 ` Matt Roper
2022-06-23 14:48 ` Souza, Jose
2022-06-23 18:06 ` Matt Roper
2022-06-17 21:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-06-18 12:05 ` [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.