* [Intel-gfx] [PATCH 0/2] Fix issues in skl_pcode_request
@ 2022-04-08 12:51 Stanislav Lisovskiy
2022-04-08 12:51 ` [Intel-gfx] [PATCH 1/2] drm/i915: Fix skl_pcode_try_request function Stanislav Lisovskiy
` (8 more replies)
0 siblings, 9 replies; 17+ messages in thread
From: Stanislav Lisovskiy @ 2022-04-08 12:51 UTC (permalink / raw)
To: intel-gfx
Couple of crucial fixes for skl_pcode_request function.
1) Correctly handle the error and do retires until timeout
2) Return PCode request status, when failure happens
Stanislav Lisovskiy (2):
drm/i915: Fix skl_pcode_try_request function
drm/i915: Swap ret and status returned from skl_pcode_request
drivers/gpu/drm/i915/intel_pcode.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.24.1.485.gad05a3d8e5
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Intel-gfx] [PATCH 1/2] drm/i915: Fix skl_pcode_try_request function
2022-04-08 12:51 [Intel-gfx] [PATCH 0/2] Fix issues in skl_pcode_request Stanislav Lisovskiy
@ 2022-04-08 12:51 ` Stanislav Lisovskiy
2022-04-08 15:46 ` Ville Syrjälä
2022-04-08 12:52 ` [Intel-gfx] [PATCH 2/2] drm/i915: Swap ret and status returned from skl_pcode_request Stanislav Lisovskiy
` (7 subsequent siblings)
8 siblings, 1 reply; 17+ messages in thread
From: Stanislav Lisovskiy @ 2022-04-08 12:51 UTC (permalink / raw)
To: intel-gfx
Currently skl_pcode_try_request function doesn't
properly handle return value it gets from
snb_pcode_rw, but treats status != 0 as success,
returning true, which basically doesn't allow
to use retry/timeout mechanisms if PCode happens
to be busy and returns EGAIN or some other status
code not equal to 0.
We saw this on real hw and also tried simulating this
by always returning -EAGAIN from snb_pcode_rw for 6 times, which
currently will just result in false success, while it should
have tried until timeout is reached:
[ 22.357729] i915 0000:00:02.0: [drm:intel_cdclk_dump_config [i915]] Changing CDCLK to
307200 kHz, VCO 614400 kHz, ref 38400 kHz, bypass 19200 kHz, voltage level 0
[ 22.357831] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 1
[ 22.357892] i915 0000:00:02.0: [drm:skl_pcode_request [i915]] Success, exiting
[ 22.357936] i915 0000:00:02.0: [drm] ERROR Failed to inform PCU about cdclk change (err -11, freq 307200)
We see en error because higher level api, still notices that status was wrong,
however we still did try only once.
We fix it by requiring _both_ the status to be 0 and
request/reply match for success(true) and function
should return failure(false) if either status turns
out to be EAGAIN, EBUSY or whatever or reply/request
masks do not match.
So now we see this in the logs:
[ 22.318667] i915 0000:00:02.0: [drm:intel_cdclk_dump_config [i915]] Changing CDCLK to
307200 kHz, VCO 614400 kHz, ref 38400 kHz, bypass 19200 kHz, voltage level 0
[ 22.318782] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 1
[ 22.318849] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 2
[ 22.319006] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 3
[ 22.319091] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 4
[ 22.319158] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 5
[ 22.319224] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 6
Reviewed-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
---
drivers/gpu/drm/i915/intel_pcode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_pcode.c b/drivers/gpu/drm/i915/intel_pcode.c
index 391a37492ce5..fb6c43e8a02f 100644
--- a/drivers/gpu/drm/i915/intel_pcode.c
+++ b/drivers/gpu/drm/i915/intel_pcode.c
@@ -136,7 +136,7 @@ static bool skl_pcode_try_request(struct drm_i915_private *i915, u32 mbox,
{
*status = __snb_pcode_rw(i915, mbox, &request, NULL, 500, 0, true);
- return *status || ((request & reply_mask) == reply);
+ return (*status == 0) && ((request & reply_mask) == reply);
}
/**
--
2.24.1.485.gad05a3d8e5
^ permalink raw reply related [flat|nested] 17+ messages in thread
* [Intel-gfx] [PATCH 2/2] drm/i915: Swap ret and status returned from skl_pcode_request
2022-04-08 12:51 [Intel-gfx] [PATCH 0/2] Fix issues in skl_pcode_request Stanislav Lisovskiy
2022-04-08 12:51 ` [Intel-gfx] [PATCH 1/2] drm/i915: Fix skl_pcode_try_request function Stanislav Lisovskiy
@ 2022-04-08 12:52 ` Stanislav Lisovskiy
2022-04-08 17:41 ` Govindapillai, Vinod
2022-04-11 8:13 ` Stanislav Lisovskiy
2022-04-08 13:29 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix issues in skl_pcode_request Patchwork
` (6 subsequent siblings)
8 siblings, 2 replies; 17+ messages in thread
From: Stanislav Lisovskiy @ 2022-04-08 12:52 UTC (permalink / raw)
To: intel-gfx
If ret isn't zero, it is almost for sure ETIMEDOUT, because
we use it in wait_for macro which does continuous retries
until timeout is reached. If we still ran out of time and
retries, we most likely would be interested in getting status,
to understand what was the actual error propagated from PCode,
rather than to find out that we had a time out, which is anyway
quite obvious, if the function fails.
Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
---
drivers/gpu/drm/i915/intel_pcode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_pcode.c b/drivers/gpu/drm/i915/intel_pcode.c
index fb6c43e8a02f..a68eaf510784 100644
--- a/drivers/gpu/drm/i915/intel_pcode.c
+++ b/drivers/gpu/drm/i915/intel_pcode.c
@@ -202,7 +202,7 @@ int skl_pcode_request(struct drm_i915_private *i915, u32 mbox, u32 request,
out:
mutex_unlock(&i915->sb_lock);
- return ret ? ret : status;
+ return ret ? status : ret;
#undef COND
}
--
2.24.1.485.gad05a3d8e5
^ permalink raw reply related [flat|nested] 17+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix issues in skl_pcode_request
2022-04-08 12:51 [Intel-gfx] [PATCH 0/2] Fix issues in skl_pcode_request Stanislav Lisovskiy
2022-04-08 12:51 ` [Intel-gfx] [PATCH 1/2] drm/i915: Fix skl_pcode_try_request function Stanislav Lisovskiy
2022-04-08 12:52 ` [Intel-gfx] [PATCH 2/2] drm/i915: Swap ret and status returned from skl_pcode_request Stanislav Lisovskiy
@ 2022-04-08 13:29 ` Patchwork
2022-04-08 14:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
` (5 subsequent siblings)
8 siblings, 0 replies; 17+ messages in thread
From: Patchwork @ 2022-04-08 13:29 UTC (permalink / raw)
To: Stanislav Lisovskiy; +Cc: intel-gfx
== Series Details ==
Series: Fix issues in skl_pcode_request
URL : https://patchwork.freedesktop.org/series/102410/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
6934e112b8f9 drm/i915: Fix skl_pcode_try_request function
-:25: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#25:
We see en error because higher level api, still notices that status was wrong,
total: 0 errors, 1 warnings, 0 checks, 8 lines checked
96be4bb1275c drm/i915: Swap ret and status returned from skl_pcode_request
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for Fix issues in skl_pcode_request
2022-04-08 12:51 [Intel-gfx] [PATCH 0/2] Fix issues in skl_pcode_request Stanislav Lisovskiy
` (2 preceding siblings ...)
2022-04-08 13:29 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix issues in skl_pcode_request Patchwork
@ 2022-04-08 14:01 ` Patchwork
2022-04-08 15:18 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
` (4 subsequent siblings)
8 siblings, 0 replies; 17+ messages in thread
From: Patchwork @ 2022-04-08 14:01 UTC (permalink / raw)
To: Stanislav Lisovskiy; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 8187 bytes --]
== Series Details ==
Series: Fix issues in skl_pcode_request
URL : https://patchwork.freedesktop.org/series/102410/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11477 -> Patchwork_22827
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/index.html
Participating hosts (47 -> 37)
------------------------------
Additional (1): fi-bxt-dsi
Missing (11): fi-bdw-samus fi-bdw-5557u shard-tglu bat-dg1-6 bat-dg2-8 bat-dg2-9 fi-bsw-cyan bat-adlp-6 bat-adlp-4 bat-rpls-2 bat-jsl-1
Known issues
------------
Here are the changes found in Patchwork_22827 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@core_hotunplug@unbind-rebind:
- fi-bxt-dsi: NOTRUN -> [DMESG-WARN][1] ([i915#5437])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-bxt-dsi/igt@core_hotunplug@unbind-rebind.html
- fi-cml-u2: NOTRUN -> [DMESG-WARN][2] ([i915#5437])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-cml-u2/igt@core_hotunplug@unbind-rebind.html
* igt@gem_huc_copy@huc-copy:
- fi-cml-u2: NOTRUN -> [SKIP][3] ([i915#2190])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-cml-u2/igt@gem_huc_copy@huc-copy.html
- fi-bxt-dsi: NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#2190])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-bxt-dsi/igt@gem_huc_copy@huc-copy.html
* igt@gem_lmem_swapping@parallel-random-engines:
- fi-cml-u2: NOTRUN -> [SKIP][5] ([i915#4613]) +3 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-cml-u2/igt@gem_lmem_swapping@parallel-random-engines.html
* igt@gem_lmem_swapping@verify-random:
- fi-bxt-dsi: NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#4613]) +3 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-bxt-dsi/igt@gem_lmem_swapping@verify-random.html
* igt@i915_selftest@live@requests:
- fi-blb-e6850: [PASS][7] -> [DMESG-FAIL][8] ([i915#4528])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/fi-blb-e6850/igt@i915_selftest@live@requests.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-blb-e6850/igt@i915_selftest@live@requests.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-bxt-dsi: NOTRUN -> [SKIP][9] ([fdo#109271] / [fdo#111827]) +8 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-bxt-dsi/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_chamelium@dp-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_22827/fi-cml-u2/igt@kms_chamelium@dp-hpd-fast.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-cml-u2: NOTRUN -> [SKIP][11] ([fdo#109278]) +1 similar issue
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-cml-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
* igt@kms_flip@basic-flip-vs-wf_vblank@a-edp1:
- fi-tgl-u2: [PASS][12] -> [DMESG-WARN][13] ([i915#402])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/fi-tgl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@a-edp1.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-tgl-u2/igt@kms_flip@basic-flip-vs-wf_vblank@a-edp1.html
* igt@kms_force_connector_basic@force-load-detect:
- fi-bxt-dsi: NOTRUN -> [SKIP][14] ([fdo#109271]) +13 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-bxt-dsi/igt@kms_force_connector_basic@force-load-detect.html
- fi-cml-u2: NOTRUN -> [SKIP][15] ([fdo#109285])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-cml-u2/igt@kms_force_connector_basic@force-load-detect.html
- fi-kbl-guc: NOTRUN -> [SKIP][16] ([fdo#109271])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-kbl-guc/igt@kms_force_connector_basic@force-load-detect.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-cml-u2: NOTRUN -> [SKIP][17] ([fdo#109278] / [i915#533])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-cml-u2/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
- fi-bxt-dsi: NOTRUN -> [SKIP][18] ([fdo#109271] / [i915#533])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-bxt-dsi/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
* igt@kms_setmode@basic-clone-single-crtc:
- fi-cml-u2: NOTRUN -> [SKIP][19] ([i915#3555])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-cml-u2/igt@kms_setmode@basic-clone-single-crtc.html
* igt@prime_vgem@basic-userptr:
- fi-cml-u2: NOTRUN -> [SKIP][20] ([i915#3301])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-cml-u2/igt@prime_vgem@basic-userptr.html
* igt@runner@aborted:
- fi-cml-u2: NOTRUN -> [FAIL][21] ([i915#4312] / [i915#5257])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-cml-u2/igt@runner@aborted.html
- fi-bxt-dsi: NOTRUN -> [FAIL][22] ([i915#4312] / [i915#5257])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-bxt-dsi/igt@runner@aborted.html
- fi-blb-e6850: NOTRUN -> [FAIL][23] ([fdo#109271] / [i915#2403] / [i915#4312])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-blb-e6850/igt@runner@aborted.html
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s3@smem:
- fi-cml-u2: [INCOMPLETE][24] -> [PASS][25]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/fi-cml-u2/igt@gem_exec_suspend@basic-s3@smem.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-cml-u2/igt@gem_exec_suspend@basic-s3@smem.html
#### Warnings ####
* igt@core_hotunplug@unbind-rebind:
- fi-kbl-7567u: [DMESG-WARN][26] -> [DMESG-WARN][27] ([i915#5437])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/fi-kbl-7567u/igt@core_hotunplug@unbind-rebind.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/fi-kbl-7567u/igt@core_hotunplug@unbind-rebind.html
[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#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[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#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[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#5257]: https://gitlab.freedesktop.org/drm/intel/issues/5257
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5437]: https://gitlab.freedesktop.org/drm/intel/issues/5437
Build changes
-------------
* Linux: CI_DRM_11477 -> Patchwork_22827
CI-20190529: 20190529
CI_DRM_11477: 3e999ce5dcc2d39d18f6eedeaa3237246eae629c @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6415: c3b690bd5f7fb1fb7ed786ab0f3b815930a6a55f @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_22827: 96be4bb1275c1587d408e096c574206a05c447c4 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
96be4bb1275c drm/i915: Swap ret and status returned from skl_pcode_request
6934e112b8f9 drm/i915: Fix skl_pcode_try_request function
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/index.html
[-- Attachment #2: Type: text/html, Size: 10368 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Intel-gfx] ✓ Fi.CI.IGT: success for Fix issues in skl_pcode_request
2022-04-08 12:51 [Intel-gfx] [PATCH 0/2] Fix issues in skl_pcode_request Stanislav Lisovskiy
` (3 preceding siblings ...)
2022-04-08 14:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
@ 2022-04-08 15:18 ` Patchwork
2022-04-11 8:11 ` [Intel-gfx] [PATCH 2/2] drm/i915: Swap ret and status returned from skl_pcode_request Stanislav Lisovskiy
` (3 subsequent siblings)
8 siblings, 0 replies; 17+ messages in thread
From: Patchwork @ 2022-04-08 15:18 UTC (permalink / raw)
To: Stanislav Lisovskiy; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 30255 bytes --]
== Series Details ==
Series: Fix issues in skl_pcode_request
URL : https://patchwork.freedesktop.org/series/102410/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11477_full -> Patchwork_22827_full
====================================================
Summary
-------
**WARNING**
Minor unknown changes coming with Patchwork_22827_full need to be verified
manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_22827_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Participating hosts (11 -> 10)
------------------------------
Missing (1): shard-tglu
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_22827_full:
### IGT changes ###
#### Warnings ####
* igt@gem_exec_balancer@parallel-ordering:
- shard-iclb: [SKIP][1] ([i915#4525]) -> [DMESG-FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb7/igt@gem_exec_balancer@parallel-ordering.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb4/igt@gem_exec_balancer@parallel-ordering.html
Known issues
------------
Here are the changes found in Patchwork_22827_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_fair@basic-none@vcs0:
- shard-kbl: NOTRUN -> [FAIL][3] ([i915#2842]) +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-kbl6/igt@gem_exec_fair@basic-none@vcs0.html
- shard-apl: NOTRUN -> [FAIL][4] ([i915#2842])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-apl4/igt@gem_exec_fair@basic-none@vcs0.html
* igt@gem_exec_fair@basic-none@vcs1:
- shard-iclb: NOTRUN -> [FAIL][5] ([i915#2842])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb1/igt@gem_exec_fair@basic-none@vcs1.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [PASS][6] -> [FAIL][7] ([i915#2842])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-glk4/igt@gem_exec_fair@basic-pace-share@rcs0.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-glk9/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_fair@basic-pace@vcs0:
- shard-kbl: [PASS][8] -> [FAIL][9] ([i915#2842])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-kbl4/igt@gem_exec_fair@basic-pace@vcs0.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-kbl3/igt@gem_exec_fair@basic-pace@vcs0.html
* igt@gem_exec_suspend@basic-s0@smem:
- shard-snb: [PASS][10] -> [SKIP][11] ([fdo#109271])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-snb5/igt@gem_exec_suspend@basic-s0@smem.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-snb6/igt@gem_exec_suspend@basic-s0@smem.html
* igt@gem_exec_suspend@basic-s4-devices@smem:
- shard-iclb: [PASS][12] -> [DMESG-WARN][13] ([i915#4391]) +1 similar issue
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb3/igt@gem_exec_suspend@basic-s4-devices@smem.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb7/igt@gem_exec_suspend@basic-s4-devices@smem.html
* igt@gem_lmem_swapping@random:
- shard-skl: NOTRUN -> [SKIP][14] ([fdo#109271] / [i915#4613]) +1 similar issue
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl4/igt@gem_lmem_swapping@random.html
* igt@gem_lmem_swapping@random-engines:
- shard-iclb: NOTRUN -> [SKIP][15] ([i915#4613])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@gem_lmem_swapping@random-engines.html
* igt@gem_pxp@create-regular-context-1:
- shard-iclb: NOTRUN -> [SKIP][16] ([i915#4270])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@gem_pxp@create-regular-context-1.html
* igt@gem_render_copy@yf-tiled-to-vebox-yf-tiled:
- shard-iclb: NOTRUN -> [SKIP][17] ([i915#768])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@gem_render_copy@yf-tiled-to-vebox-yf-tiled.html
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: NOTRUN -> [WARN][18] ([i915#2684])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb8/igt@i915_pm_rc6_residency@rc6-idle.html
* igt@i915_pm_rpm@pc8-residency:
- shard-iclb: NOTRUN -> [SKIP][19] ([fdo#109293] / [fdo#109506])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb8/igt@i915_pm_rpm@pc8-residency.html
* igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-0:
- shard-iclb: NOTRUN -> [SKIP][20] ([i915#5286])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-0.html
* igt@kms_big_fb@linear-64bpp-rotate-270:
- shard-iclb: NOTRUN -> [SKIP][21] ([fdo#110725] / [fdo#111614])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb8/igt@kms_big_fb@linear-64bpp-rotate-270.html
* igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-async-flip:
- shard-skl: NOTRUN -> [FAIL][22] ([i915#3743])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl8/igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-async-flip.html
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip:
- shard-skl: NOTRUN -> [SKIP][23] ([fdo#109271] / [i915#3777]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl4/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip-async-flip.html
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip:
- shard-kbl: NOTRUN -> [SKIP][24] ([fdo#109271] / [i915#3777]) +1 similar issue
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-kbl6/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip.html
- shard-apl: NOTRUN -> [SKIP][25] ([fdo#109271] / [i915#3777]) +2 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-apl4/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-hflip.html
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][26] ([fdo#109271] / [i915#3886])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-apl4/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs.html
- shard-kbl: NOTRUN -> [SKIP][27] ([fdo#109271] / [i915#3886])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-kbl6/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc:
- shard-iclb: NOTRUN -> [SKIP][28] ([fdo#109278] / [i915#3886]) +1 similar issue
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb8/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-b-bad-aux-stride-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][29] ([fdo#109271] / [i915#3886]) +4 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl8/igt@kms_ccs@pipe-b-bad-aux-stride-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-random-ccs-data-y_tiled_gen12_rc_ccs:
- shard-apl: NOTRUN -> [SKIP][30] ([fdo#109271]) +30 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-apl2/igt@kms_ccs@pipe-c-random-ccs-data-y_tiled_gen12_rc_ccs.html
* igt@kms_chamelium@dp-audio-edid:
- shard-skl: NOTRUN -> [SKIP][31] ([fdo#109271] / [fdo#111827]) +4 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl8/igt@kms_chamelium@dp-audio-edid.html
* igt@kms_chamelium@dp-hpd-with-enabled-mode:
- shard-iclb: NOTRUN -> [SKIP][32] ([fdo#109284] / [fdo#111827])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@kms_chamelium@dp-hpd-with-enabled-mode.html
* igt@kms_color_chamelium@pipe-a-ctm-blue-to-red:
- shard-kbl: NOTRUN -> [SKIP][33] ([fdo#109271] / [fdo#111827])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-kbl6/igt@kms_color_chamelium@pipe-a-ctm-blue-to-red.html
- shard-apl: NOTRUN -> [SKIP][34] ([fdo#109271] / [fdo#111827])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-apl4/igt@kms_color_chamelium@pipe-a-ctm-blue-to-red.html
* igt@kms_content_protection@mei_interface:
- shard-iclb: NOTRUN -> [SKIP][35] ([fdo#109300] / [fdo#111066])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@kms_content_protection@mei_interface.html
* igt@kms_cursor_crc@pipe-b-cursor-32x10-offscreen:
- shard-tglb: NOTRUN -> [SKIP][36] ([i915#3359])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-tglb6/igt@kms_cursor_crc@pipe-b-cursor-32x10-offscreen.html
* igt@kms_cursor_legacy@cursora-vs-flipb-varying-size:
- shard-iclb: NOTRUN -> [SKIP][37] ([fdo#109274] / [fdo#109278])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb8/igt@kms_cursor_legacy@cursora-vs-flipb-varying-size.html
* igt@kms_cursor_legacy@pipe-d-torture-bo:
- shard-skl: NOTRUN -> [SKIP][38] ([fdo#109271] / [i915#533]) +1 similar issue
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl4/igt@kms_cursor_legacy@pipe-d-torture-bo.html
* igt@kms_dp_tiled_display@basic-test-pattern:
- shard-iclb: NOTRUN -> [SKIP][39] ([i915#426])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@kms_dp_tiled_display@basic-test-pattern.html
* igt@kms_draw_crc@draw-method-xrgb8888-render-4tiled:
- shard-iclb: NOTRUN -> [SKIP][40] ([i915#5287])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb8/igt@kms_draw_crc@draw-method-xrgb8888-render-4tiled.html
* igt@kms_flip@2x-flip-vs-expired-vblank:
- shard-iclb: NOTRUN -> [SKIP][41] ([fdo#109274]) +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@kms_flip@2x-flip-vs-expired-vblank.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling:
- shard-iclb: [PASS][42] -> [SKIP][43] ([i915#3701])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb5/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytile-downscaling.html
* igt@kms_frontbuffer_tracking@fbc-1p-shrfb-fliptrack-mmap-gtt:
- shard-skl: NOTRUN -> [SKIP][44] ([fdo#109271]) +102 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl4/igt@kms_frontbuffer_tracking@fbc-1p-shrfb-fliptrack-mmap-gtt.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-shrfb-draw-render:
- shard-tglb: NOTRUN -> [SKIP][45] ([fdo#109280] / [fdo#111825])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-tglb6/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-shrfb-draw-render.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-draw-render:
- shard-iclb: NOTRUN -> [SKIP][46] ([fdo#109280]) +8 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-cur-indfb-draw-render.html
* igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-wc:
- shard-kbl: NOTRUN -> [SKIP][47] ([fdo#109271]) +21 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-kbl6/igt@kms_frontbuffer_tracking@psr-rgb101010-draw-mmap-wc.html
* igt@kms_hdr@bpc-switch-suspend@bpc-switch-suspend-dp-1-pipe-a:
- shard-apl: [PASS][48] -> [DMESG-WARN][49] ([i915#180]) +2 similar issues
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-apl1/igt@kms_hdr@bpc-switch-suspend@bpc-switch-suspend-dp-1-pipe-a.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-apl1/igt@kms_hdr@bpc-switch-suspend@bpc-switch-suspend-dp-1-pipe-a.html
* igt@kms_pipe_b_c_ivb@enable-pipe-c-while-b-has-3-lanes:
- shard-iclb: NOTRUN -> [SKIP][50] ([fdo#109289])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb8/igt@kms_pipe_b_c_ivb@enable-pipe-c-while-b-has-3-lanes.html
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [PASS][51] -> [FAIL][52] ([fdo#108145] / [i915#265]) +1 similar issue
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-skl9/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl9/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: NOTRUN -> [FAIL][53] ([fdo#108145] / [i915#265]) +1 similar issue
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl4/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html
* igt@kms_psr2_sf@plane-move-sf-dmg-area:
- shard-iclb: NOTRUN -> [SKIP][54] ([fdo#111068] / [i915#658])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@kms_psr2_sf@plane-move-sf-dmg-area.html
* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [PASS][55] -> [SKIP][56] ([fdo#109441]) +1 similar issue
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb7/igt@kms_psr@psr2_primary_page_flip.html
* igt@kms_psr@psr2_sprite_mmap_cpu:
- shard-iclb: NOTRUN -> [SKIP][57] ([fdo#109441])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb8/igt@kms_psr@psr2_sprite_mmap_cpu.html
* igt@kms_rotation_crc@primary-4-tiled-reflect-x-180:
- shard-iclb: NOTRUN -> [SKIP][58] ([i915#5289])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb8/igt@kms_rotation_crc@primary-4-tiled-reflect-x-180.html
* igt@kms_scaling_modes@scaling-mode-none@edp-1-pipe-c:
- shard-iclb: NOTRUN -> [SKIP][59] ([i915#5030]) +2 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@kms_scaling_modes@scaling-mode-none@edp-1-pipe-c.html
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-kbl: [PASS][60] -> [INCOMPLETE][61] ([i915#3614])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-kbl1/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-kbl4/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
* igt@kms_vblank@pipe-d-ts-continuation-idle-hang:
- shard-iclb: NOTRUN -> [SKIP][62] ([fdo#109278]) +13 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@kms_vblank@pipe-d-ts-continuation-idle-hang.html
* igt@kms_vrr@flip-basic:
- shard-tglb: NOTRUN -> [SKIP][63] ([fdo#109502])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-tglb6/igt@kms_vrr@flip-basic.html
* igt@kms_writeback@writeback-invalid-parameters:
- shard-skl: NOTRUN -> [SKIP][64] ([fdo#109271] / [i915#2437])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl8/igt@kms_writeback@writeback-invalid-parameters.html
* igt@perf@polling:
- shard-skl: NOTRUN -> [FAIL][65] ([i915#1542])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl4/igt@perf@polling.html
* igt@prime_nv_test@i915_nv_sharing:
- shard-iclb: NOTRUN -> [SKIP][66] ([fdo#109291]) +1 similar issue
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@prime_nv_test@i915_nv_sharing.html
* igt@syncobj_timeline@transfer-timeline-point:
- shard-apl: NOTRUN -> [DMESG-FAIL][67] ([i915#5098])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-apl2/igt@syncobj_timeline@transfer-timeline-point.html
* igt@sysfs_clients@pidname:
- shard-iclb: NOTRUN -> [SKIP][68] ([i915#2994])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb3/igt@sysfs_clients@pidname.html
#### Possible fixes ####
* igt@gem_eio@in-flight-contexts-immediate:
- shard-tglb: [TIMEOUT][69] ([i915#3063]) -> [PASS][70] +1 similar issue
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-tglb7/igt@gem_eio@in-flight-contexts-immediate.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-tglb1/igt@gem_eio@in-flight-contexts-immediate.html
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: [FAIL][71] ([i915#2846]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-kbl6/igt@gem_exec_fair@basic-deadline.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-kbl1/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-apl: [FAIL][73] ([i915#2842]) -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-apl2/igt@gem_exec_fair@basic-none-solo@rcs0.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-apl6/igt@gem_exec_fair@basic-none-solo@rcs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-tglb: [FAIL][75] ([i915#2842]) -> [PASS][76]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-tglb8/igt@gem_exec_fair@basic-pace-share@rcs0.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-tglb3/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_flush@basic-uc-set-default:
- shard-snb: [SKIP][77] ([fdo#109271]) -> [PASS][78] +2 similar issues
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-snb6/igt@gem_exec_flush@basic-uc-set-default.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-snb4/igt@gem_exec_flush@basic-uc-set-default.html
* igt@gem_spin_batch@engines@vcs0:
- shard-apl: [FAIL][79] ([i915#2898]) -> [PASS][80]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-apl3/igt@gem_spin_batch@engines@vcs0.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-apl3/igt@gem_spin_batch@engines@vcs0.html
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][81] ([i915#454]) -> [PASS][82]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb8/igt@i915_pm_dc@dc6-psr.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb5/igt@i915_pm_dc@dc6-psr.html
* igt@kms_cursor_crc@pipe-c-cursor-suspend:
- shard-skl: [INCOMPLETE][83] -> [PASS][84]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-skl6/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl8/igt@kms_cursor_crc@pipe-c-cursor-suspend.html
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-glk: [FAIL][85] ([i915#2346] / [i915#533]) -> [PASS][86]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-glk4/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-glk9/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2:
- shard-glk: [FAIL][87] ([i915#79]) -> [PASS][88]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-glk7/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-glk9/igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@ab-hdmi-a1-hdmi-a2.html
* igt@kms_flip@blocking-wf_vblank@a-edp1:
- shard-skl: [FAIL][89] ([i915#2122]) -> [PASS][90]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-skl3/igt@kms_flip@blocking-wf_vblank@a-edp1.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl1/igt@kms_flip@blocking-wf_vblank@a-edp1.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1:
- shard-skl: [FAIL][91] ([i915#79]) -> [PASS][92]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-skl9/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1.html
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl9/igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1.html
* igt@kms_flip@flip-vs-suspend-interruptible@c-dp1:
- shard-apl: [DMESG-WARN][93] ([i915#180]) -> [PASS][94] +1 similar issue
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-apl8/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-apl4/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html
- shard-kbl: [INCOMPLETE][95] ([i915#636]) -> [PASS][96]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-kbl3/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-kbl6/igt@kms_flip@flip-vs-suspend-interruptible@c-dp1.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-64bpp-ytile-upscaling:
- shard-glk: [FAIL][97] ([i915#4911]) -> [PASS][98]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-glk8/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-64bpp-ytile-upscaling.html
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-glk2/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-64bpp-ytile-upscaling.html
* igt@kms_plane_scaling@downscale-with-pixel-format-factor-0-5@pipe-c-edp-1-downscale-with-pixel-format:
- shard-iclb: [SKIP][99] ([i915#5176]) -> [PASS][100] +2 similar issues
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb2/igt@kms_plane_scaling@downscale-with-pixel-format-factor-0-5@pipe-c-edp-1-downscale-with-pixel-format.html
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb1/igt@kms_plane_scaling@downscale-with-pixel-format-factor-0-5@pipe-c-edp-1-downscale-with-pixel-format.html
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [SKIP][101] ([fdo#109441]) -> [PASS][102] +1 similar issue
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb5/igt@kms_psr@psr2_cursor_mmap_cpu.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
* igt@kms_psr_stress_test@invalidate-primary-flip-overlay:
- shard-tglb: [SKIP][103] ([i915#5519]) -> [PASS][104]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-tglb3/igt@kms_psr_stress_test@invalidate-primary-flip-overlay.html
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-tglb8/igt@kms_psr_stress_test@invalidate-primary-flip-overlay.html
* igt@perf@short-reads:
- shard-skl: [FAIL][105] ([i915#51]) -> [PASS][106]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-skl8/igt@perf@short-reads.html
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl5/igt@perf@short-reads.html
* igt@sysfs_heartbeat_interval@mixed@bcs0:
- shard-skl: [FAIL][107] ([i915#1731]) -> [PASS][108]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-skl3/igt@sysfs_heartbeat_interval@mixed@bcs0.html
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl8/igt@sysfs_heartbeat_interval@mixed@bcs0.html
* igt@sysfs_heartbeat_interval@mixed@rcs0:
- shard-skl: [WARN][109] ([i915#4055]) -> [PASS][110]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-skl3/igt@sysfs_heartbeat_interval@mixed@rcs0.html
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl8/igt@sysfs_heartbeat_interval@mixed@rcs0.html
#### Warnings ####
* igt@gem_eio@unwedge-stress:
- shard-tglb: [TIMEOUT][111] ([i915#3063] / [i915#3648]) -> [FAIL][112] ([i915#232])
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-tglb6/igt@gem_eio@unwedge-stress.html
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-tglb2/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_balancer@parallel-out-fence:
- shard-iclb: [DMESG-WARN][113] -> [SKIP][114] ([i915#4525]) +1 similar issue
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb4/igt@gem_exec_balancer@parallel-out-fence.html
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb8/igt@gem_exec_balancer@parallel-out-fence.html
* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-iclb: [FAIL][115] ([i915#2842]) -> [FAIL][116] ([i915#2852])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb5/igt@gem_exec_fair@basic-none-rrul@rcs0.html
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb2/igt@gem_exec_fair@basic-none-rrul@rcs0.html
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-iclb: [FAIL][117] ([i915#2842]) -> [DMESG-FAIL][118] ([i915#2842] / [i915#4391])
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb3/igt@gem_exec_fair@basic-pace@rcs0.html
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb7/igt@gem_exec_fair@basic-pace@rcs0.html
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-kbl: [SKIP][119] ([fdo#109271]) -> [FAIL][120] ([i915#2842])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-kbl4/igt@gem_exec_fair@basic-pace@vecs0.html
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-kbl3/igt@gem_exec_fair@basic-pace@vecs0.html
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [FAIL][121] ([i915#2849]) -> [FAIL][122] ([i915#2842])
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb4/igt@gem_exec_fair@basic-throttle@rcs0.html
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb8/igt@gem_exec_fair@basic-throttle@rcs0.html
* igt@gen9_exec_parse@allowed-single:
- shard-glk: [DMESG-WARN][123] ([i915#5566]) -> [DMESG-WARN][124] ([i915#5566] / [i915#716])
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-glk6/igt@gen9_exec_parse@allowed-single.html
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-glk8/igt@gen9_exec_parse@allowed-single.html
- shard-apl: [DMESG-WARN][125] ([i915#5566] / [i915#716]) -> [DMESG-WARN][126] ([i915#5566])
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-apl7/igt@gen9_exec_parse@allowed-single.html
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-apl4/igt@gen9_exec_parse@allowed-single.html
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-iclb: [SKIP][127] ([i915#588]) -> [SKIP][128] ([i915#658])
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb2/igt@i915_pm_dc@dc3co-vpb-simulation.html
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb1/igt@i915_pm_dc@dc3co-vpb-simulation.html
* igt@kms_color_chamelium@pipe-c-ctm-0-5:
- shard-skl: [SKIP][129] ([fdo#109271] / [fdo#111827]) -> [SKIP][130] ([fdo#109271] / [fdo#111827] / [i915#1888])
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-skl10/igt@kms_color_chamelium@pipe-c-ctm-0-5.html
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl7/igt@kms_color_chamelium@pipe-c-ctm-0-5.html
* igt@kms_psr2_sf@cursor-plane-move-continuous-sf:
- shard-iclb: [SKIP][131] ([i915#658]) -> [SKIP][132] ([i915#2920])
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb5/igt@kms_psr2_sf@cursor-plane-move-continuous-sf.html
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb2/igt@kms_psr2_sf@cursor-plane-move-continuous-sf.html
* igt@kms_psr2_sf@overlay-plane-update-continuous-sf:
- shard-iclb: [SKIP][133] ([i915#2920]) -> [SKIP][134] ([fdo#111068] / [i915#658]) +1 similar issue
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-iclb2/igt@kms_psr2_sf@overlay-plane-update-continuous-sf.html
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-iclb7/igt@kms_psr2_sf@overlay-plane-update-continuous-sf.html
* igt@runner@aborted:
- shard-skl: ([FAIL][135], [FAIL][136], [FAIL][137], [FAIL][138]) ([i915#3002] / [i915#4312] / [i915#5257]) -> ([FAIL][139], [FAIL][140], [FAIL][141], [FAIL][142], [FAIL][143]) ([i915#2029] / [i915#3002] / [i915#4312] / [i915#5257])
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-skl6/igt@runner@aborted.html
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-skl7/igt@runner@aborted.html
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-skl8/igt@runner@aborted.html
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11477/shard-skl9/igt@runner@aborted.html
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/shard-skl3/igt@runner@aborted.html
[140]: https://intel-gfx-ci.01.org/tree/drm
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22827/index.html
[-- Attachment #2: Type: text/html, Size: 33322 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Intel-gfx] [PATCH 1/2] drm/i915: Fix skl_pcode_try_request function
2022-04-08 12:51 ` [Intel-gfx] [PATCH 1/2] drm/i915: Fix skl_pcode_try_request function Stanislav Lisovskiy
@ 2022-04-08 15:46 ` Ville Syrjälä
2022-04-08 15:59 ` Ville Syrjälä
2022-04-08 17:39 ` Lisovskiy, Stanislav
0 siblings, 2 replies; 17+ messages in thread
From: Ville Syrjälä @ 2022-04-08 15:46 UTC (permalink / raw)
To: Stanislav Lisovskiy; +Cc: intel-gfx
On Fri, Apr 08, 2022 at 03:51:59PM +0300, Stanislav Lisovskiy wrote:
> Currently skl_pcode_try_request function doesn't
> properly handle return value it gets from
> snb_pcode_rw, but treats status != 0 as success,
> returning true, which basically doesn't allow
> to use retry/timeout mechanisms if PCode happens
> to be busy and returns EGAIN or some other status
> code not equal to 0.
>
> We saw this on real hw and also tried simulating this
> by always returning -EAGAIN from snb_pcode_rw for 6 times, which
> currently will just result in false success, while it should
> have tried until timeout is reached:
>
> [ 22.357729] i915 0000:00:02.0: [drm:intel_cdclk_dump_config [i915]] Changing CDCLK to
> 307200 kHz, VCO 614400 kHz, ref 38400 kHz, bypass 19200 kHz, voltage level 0
> [ 22.357831] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 1
> [ 22.357892] i915 0000:00:02.0: [drm:skl_pcode_request [i915]] Success, exiting
> [ 22.357936] i915 0000:00:02.0: [drm] ERROR Failed to inform PCU about cdclk change (err -11, freq 307200)
>
> We see en error because higher level api, still notices that status was wrong,
> however we still did try only once.
>
> We fix it by requiring _both_ the status to be 0 and
> request/reply match for success(true) and function
> should return failure(false) if either status turns
> out to be EAGAIN, EBUSY or whatever or reply/request
> masks do not match.
>
> So now we see this in the logs:
>
> [ 22.318667] i915 0000:00:02.0: [drm:intel_cdclk_dump_config [i915]] Changing CDCLK to
> 307200 kHz, VCO 614400 kHz, ref 38400 kHz, bypass 19200 kHz, voltage level 0
> [ 22.318782] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 1
> [ 22.318849] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 2
> [ 22.319006] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 3
> [ 22.319091] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 4
> [ 22.319158] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 5
> [ 22.319224] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 6
>
> Reviewed-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> ---
> drivers/gpu/drm/i915/intel_pcode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_pcode.c b/drivers/gpu/drm/i915/intel_pcode.c
> index 391a37492ce5..fb6c43e8a02f 100644
> --- a/drivers/gpu/drm/i915/intel_pcode.c
> +++ b/drivers/gpu/drm/i915/intel_pcode.c
> @@ -136,7 +136,7 @@ static bool skl_pcode_try_request(struct drm_i915_private *i915, u32 mbox,
> {
> *status = __snb_pcode_rw(i915, mbox, &request, NULL, 500, 0, true);
>
> - return *status || ((request & reply_mask) == reply);
> + return (*status == 0) && ((request & reply_mask) == reply);
The problem with this is that now we'll keep pointlessly banging it
even if it returns a real error.
We should never really see that -EAGAIN since it indicates that our
timeout is too short. So the real fix should be to increase that
timeout. But I guess we could do a belt-and-suspenders approach
where we also keep repeating on -EGAIN. But I'm thinking -EAGAIN
should WARN as well to make sure we notice that our timeout is wrong.
> }
>
> /**
> --
> 2.24.1.485.gad05a3d8e5
--
Ville Syrjälä
Intel
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Intel-gfx] [PATCH 1/2] drm/i915: Fix skl_pcode_try_request function
2022-04-08 15:46 ` Ville Syrjälä
@ 2022-04-08 15:59 ` Ville Syrjälä
2022-04-08 17:49 ` Lisovskiy, Stanislav
2022-04-08 17:39 ` Lisovskiy, Stanislav
1 sibling, 1 reply; 17+ messages in thread
From: Ville Syrjälä @ 2022-04-08 15:59 UTC (permalink / raw)
To: Stanislav Lisovskiy; +Cc: intel-gfx
On Fri, Apr 08, 2022 at 06:46:00PM +0300, Ville Syrjälä wrote:
> On Fri, Apr 08, 2022 at 03:51:59PM +0300, Stanislav Lisovskiy wrote:
> > Currently skl_pcode_try_request function doesn't
> > properly handle return value it gets from
> > snb_pcode_rw, but treats status != 0 as success,
> > returning true, which basically doesn't allow
> > to use retry/timeout mechanisms if PCode happens
> > to be busy and returns EGAIN or some other status
> > code not equal to 0.
> >
> > We saw this on real hw and also tried simulating this
> > by always returning -EAGAIN from snb_pcode_rw for 6 times, which
> > currently will just result in false success, while it should
> > have tried until timeout is reached:
> >
> > [ 22.357729] i915 0000:00:02.0: [drm:intel_cdclk_dump_config [i915]] Changing CDCLK to
> > 307200 kHz, VCO 614400 kHz, ref 38400 kHz, bypass 19200 kHz, voltage level 0
> > [ 22.357831] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 1
> > [ 22.357892] i915 0000:00:02.0: [drm:skl_pcode_request [i915]] Success, exiting
> > [ 22.357936] i915 0000:00:02.0: [drm] ERROR Failed to inform PCU about cdclk change (err -11, freq 307200)
> >
> > We see en error because higher level api, still notices that status was wrong,
> > however we still did try only once.
> >
> > We fix it by requiring _both_ the status to be 0 and
> > request/reply match for success(true) and function
> > should return failure(false) if either status turns
> > out to be EAGAIN, EBUSY or whatever or reply/request
> > masks do not match.
> >
> > So now we see this in the logs:
> >
> > [ 22.318667] i915 0000:00:02.0: [drm:intel_cdclk_dump_config [i915]] Changing CDCLK to
> > 307200 kHz, VCO 614400 kHz, ref 38400 kHz, bypass 19200 kHz, voltage level 0
> > [ 22.318782] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 1
Hmm. That is weird. The timestamp difference is only ~100 usec even
though we are supposed to use that 500 usec timeout. So did some
previous pcode access already timeout and leave the mailbox busy
before we even do this request, or what is going on?
> > [ 22.318849] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 2
> > [ 22.319006] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 3
> > [ 22.319091] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 4
> > [ 22.319158] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 5
> > [ 22.319224] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 6
> >
> > Reviewed-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> > Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_pcode.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_pcode.c b/drivers/gpu/drm/i915/intel_pcode.c
> > index 391a37492ce5..fb6c43e8a02f 100644
> > --- a/drivers/gpu/drm/i915/intel_pcode.c
> > +++ b/drivers/gpu/drm/i915/intel_pcode.c
> > @@ -136,7 +136,7 @@ static bool skl_pcode_try_request(struct drm_i915_private *i915, u32 mbox,
> > {
> > *status = __snb_pcode_rw(i915, mbox, &request, NULL, 500, 0, true);
> >
> > - return *status || ((request & reply_mask) == reply);
> > + return (*status == 0) && ((request & reply_mask) == reply);
>
> The problem with this is that now we'll keep pointlessly banging it
> even if it returns a real error.
>
> We should never really see that -EAGAIN since it indicates that our
> timeout is too short. So the real fix should be to increase that
> timeout. But I guess we could do a belt-and-suspenders approach
> where we also keep repeating on -EGAIN. But I'm thinking -EAGAIN
> should WARN as well to make sure we notice that our timeout is wrong.
>
> > }
> >
> > /**
> > --
> > 2.24.1.485.gad05a3d8e5
>
> --
> Ville Syrjälä
> Intel
--
Ville Syrjälä
Intel
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Intel-gfx] [PATCH 1/2] drm/i915: Fix skl_pcode_try_request function
2022-04-08 15:46 ` Ville Syrjälä
2022-04-08 15:59 ` Ville Syrjälä
@ 2022-04-08 17:39 ` Lisovskiy, Stanislav
1 sibling, 0 replies; 17+ messages in thread
From: Lisovskiy, Stanislav @ 2022-04-08 17:39 UTC (permalink / raw)
To: Ville Syrjälä; +Cc: intel-gfx
On Fri, Apr 08, 2022 at 06:46:00PM +0300, Ville Syrjälä wrote:
> On Fri, Apr 08, 2022 at 03:51:59PM +0300, Stanislav Lisovskiy wrote:
> > Currently skl_pcode_try_request function doesn't
> > properly handle return value it gets from
> > snb_pcode_rw, but treats status != 0 as success,
> > returning true, which basically doesn't allow
> > to use retry/timeout mechanisms if PCode happens
> > to be busy and returns EGAIN or some other status
> > code not equal to 0.
> >
> > We saw this on real hw and also tried simulating this
> > by always returning -EAGAIN from snb_pcode_rw for 6 times, which
> > currently will just result in false success, while it should
> > have tried until timeout is reached:
> >
> > [ 22.357729] i915 0000:00:02.0: [drm:intel_cdclk_dump_config [i915]] Changing CDCLK to
> > 307200 kHz, VCO 614400 kHz, ref 38400 kHz, bypass 19200 kHz, voltage level 0
> > [ 22.357831] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 1
> > [ 22.357892] i915 0000:00:02.0: [drm:skl_pcode_request [i915]] Success, exiting
> > [ 22.357936] i915 0000:00:02.0: [drm] ERROR Failed to inform PCU about cdclk change (err -11, freq 307200)
> >
> > We see en error because higher level api, still notices that status was wrong,
> > however we still did try only once.
> >
> > We fix it by requiring _both_ the status to be 0 and
> > request/reply match for success(true) and function
> > should return failure(false) if either status turns
> > out to be EAGAIN, EBUSY or whatever or reply/request
> > masks do not match.
> >
> > So now we see this in the logs:
> >
> > [ 22.318667] i915 0000:00:02.0: [drm:intel_cdclk_dump_config [i915]] Changing CDCLK to
> > 307200 kHz, VCO 614400 kHz, ref 38400 kHz, bypass 19200 kHz, voltage level 0
> > [ 22.318782] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 1
> > [ 22.318849] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 2
> > [ 22.319006] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 3
> > [ 22.319091] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 4
> > [ 22.319158] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 5
> > [ 22.319224] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 6
> >
> > Reviewed-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> > Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_pcode.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_pcode.c b/drivers/gpu/drm/i915/intel_pcode.c
> > index 391a37492ce5..fb6c43e8a02f 100644
> > --- a/drivers/gpu/drm/i915/intel_pcode.c
> > +++ b/drivers/gpu/drm/i915/intel_pcode.c
> > @@ -136,7 +136,7 @@ static bool skl_pcode_try_request(struct drm_i915_private *i915, u32 mbox,
> > {
> > *status = __snb_pcode_rw(i915, mbox, &request, NULL, 500, 0, true);
> >
> > - return *status || ((request & reply_mask) == reply);
> > + return (*status == 0) && ((request & reply_mask) == reply);
>
> The problem with this is that now we'll keep pointlessly banging it
> even if it returns a real error.
Question is that we should then define when it is pointless and when
its not.
Not sure, if we should retry on any status - maybe only if its EBUSY
or smth. But even if at some point we get some issue with PCode
which is resolved after retry as currently should we may be still retry?
Anyway I guess this isn't how this is supposed to work - i.e if we
get status != 0, we should fail, but not succeed, also I guess
request not matching the reply mask should make it fail.
Stan
>
> We should never really see that -EAGAIN since it indicates that our
> timeout is too short. So the real fix should be to increase that
> timeout. But I guess we could do a belt-and-suspenders approach
> where we also keep repeating on -EGAIN. But I'm thinking -EAGAIN
> should WARN as well to make sure we notice that our timeout is wrong.
>
> > }
> >
> > /**
> > --
> > 2.24.1.485.gad05a3d8e5
>
> --
> Ville Syrjälä
> Intel
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Intel-gfx] [PATCH 2/2] drm/i915: Swap ret and status returned from skl_pcode_request
2022-04-08 12:52 ` [Intel-gfx] [PATCH 2/2] drm/i915: Swap ret and status returned from skl_pcode_request Stanislav Lisovskiy
@ 2022-04-08 17:41 ` Govindapillai, Vinod
2022-04-11 8:13 ` Stanislav Lisovskiy
1 sibling, 0 replies; 17+ messages in thread
From: Govindapillai, Vinod @ 2022-04-08 17:41 UTC (permalink / raw)
To: Lisovskiy, Stanislav, intel-gfx
On Fri, 2022-04-08 at 15:52 +0300, Stanislav Lisovskiy wrote:
> If ret isn't zero, it is almost for sure ETIMEDOUT, because
> we use it in wait_for macro which does continuous retries
> until timeout is reached. If we still ran out of time and
> retries, we most likely would be interested in getting status,
> to understand what was the actual error propagated from PCode,
> rather than to find out that we had a time out, which is anyway
> quite obvious, if the function fails.
>
> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> ---
> drivers/gpu/drm/i915/intel_pcode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_pcode.c b/drivers/gpu/drm/i915/intel_pcode.c
> index fb6c43e8a02f..a68eaf510784 100644
> --- a/drivers/gpu/drm/i915/intel_pcode.c
> +++ b/drivers/gpu/drm/i915/intel_pcode.c
> @@ -202,7 +202,7 @@ int skl_pcode_request(struct drm_i915_private *i915, u32 mbox, u32 request,
>
> out:
> mutex_unlock(&i915->sb_lock);
> - return ret ? ret : status;
> + return ret ? status : ret;
Isnt this equivalent to "return status"
When we were discussing this, I felt this is good.
But on further check with the functions gen7_check_mailbox_status(), is there a possibility that
status = 0 but "request & reply_mask) != reply" for the "default" case handling?
In that cast _wait_for() will be timedout with ret = ETimedOut but "status" = 0
Is that real scenario?
> #undef COND
> }
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: [Intel-gfx] [PATCH 1/2] drm/i915: Fix skl_pcode_try_request function
2022-04-08 15:59 ` Ville Syrjälä
@ 2022-04-08 17:49 ` Lisovskiy, Stanislav
0 siblings, 0 replies; 17+ messages in thread
From: Lisovskiy, Stanislav @ 2022-04-08 17:49 UTC (permalink / raw)
To: Ville Syrjälä; +Cc: intel-gfx
On Fri, Apr 08, 2022 at 06:59:07PM +0300, Ville Syrjälä wrote:
> On Fri, Apr 08, 2022 at 06:46:00PM +0300, Ville Syrjälä wrote:
> > On Fri, Apr 08, 2022 at 03:51:59PM +0300, Stanislav Lisovskiy wrote:
> > > Currently skl_pcode_try_request function doesn't
> > > properly handle return value it gets from
> > > snb_pcode_rw, but treats status != 0 as success,
> > > returning true, which basically doesn't allow
> > > to use retry/timeout mechanisms if PCode happens
> > > to be busy and returns EGAIN or some other status
> > > code not equal to 0.
> > >
> > > We saw this on real hw and also tried simulating this
> > > by always returning -EAGAIN from snb_pcode_rw for 6 times, which
> > > currently will just result in false success, while it should
> > > have tried until timeout is reached:
> > >
> > > [ 22.357729] i915 0000:00:02.0: [drm:intel_cdclk_dump_config [i915]] Changing CDCLK to
> > > 307200 kHz, VCO 614400 kHz, ref 38400 kHz, bypass 19200 kHz, voltage level 0
> > > [ 22.357831] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 1
> > > [ 22.357892] i915 0000:00:02.0: [drm:skl_pcode_request [i915]] Success, exiting
> > > [ 22.357936] i915 0000:00:02.0: [drm] ERROR Failed to inform PCU about cdclk change (err -11, freq 307200)
> > >
> > > We see en error because higher level api, still notices that status was wrong,
> > > however we still did try only once.
> > >
> > > We fix it by requiring _both_ the status to be 0 and
> > > request/reply match for success(true) and function
> > > should return failure(false) if either status turns
> > > out to be EAGAIN, EBUSY or whatever or reply/request
> > > masks do not match.
> > >
> > > So now we see this in the logs:
> > >
> > > [ 22.318667] i915 0000:00:02.0: [drm:intel_cdclk_dump_config [i915]] Changing CDCLK to
> > > 307200 kHz, VCO 614400 kHz, ref 38400 kHz, bypass 19200 kHz, voltage level 0
> > > [ 22.318782] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 1
>
> Hmm. That is weird. The timestamp difference is only ~100 usec even
> though we are supposed to use that 500 usec timeout. So did some
> previous pcode access already timeout and leave the mailbox busy
> before we even do this request, or what is going on?
Ah that is not the real example.
What I did to check how it works is just added something like this:
+ static int retries = 0;
+ if (++retry < 6)
+ return -EAGAIN
to _snb_pcode_rw.
So before the patch, skl_pcode_try_request returned True when getting -EAGAIN and
immediately bailed out, assigning ret = 0 and goto out, as if it succeeded while it obvously not.
>
> > > [ 22.318849] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 2
> > > [ 22.319006] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 3
> > > [ 22.319091] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 4
> > > [ 22.319158] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 5
> > > [ 22.319224] i915 0000:00:02.0: [drm:__snb_pcode_rw [i915]] Returning EAGAIN retry 6
That is how it behaves with this patch, i.e status != 0 makes skl_pcode_try_request
return False(as it should) which then enables skl_pcode_request retry machinery.
In real case we have something similar to this but can't really reproduce it that easily,
so was kinda simulating that issue to check.
Stan
> > >
> > > Reviewed-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> > > Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> > > ---
> > > drivers/gpu/drm/i915/intel_pcode.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/gpu/drm/i915/intel_pcode.c b/drivers/gpu/drm/i915/intel_pcode.c
> > > index 391a37492ce5..fb6c43e8a02f 100644
> > > --- a/drivers/gpu/drm/i915/intel_pcode.c
> > > +++ b/drivers/gpu/drm/i915/intel_pcode.c
> > > @@ -136,7 +136,7 @@ static bool skl_pcode_try_request(struct drm_i915_private *i915, u32 mbox,
> > > {
> > > *status = __snb_pcode_rw(i915, mbox, &request, NULL, 500, 0, true);
> > >
> > > - return *status || ((request & reply_mask) == reply);
> > > + return (*status == 0) && ((request & reply_mask) == reply);
> >
> > The problem with this is that now we'll keep pointlessly banging it
> > even if it returns a real error.
> >
> > We should never really see that -EAGAIN since it indicates that our
> > timeout is too short. So the real fix should be to increase that
> > timeout. But I guess we could do a belt-and-suspenders approach
> > where we also keep repeating on -EGAIN. But I'm thinking -EAGAIN
> > should WARN as well to make sure we notice that our timeout is wrong.
> >
> > > }
> > >
> > > /**
> > > --
> > > 2.24.1.485.gad05a3d8e5
> >
> > --
> > Ville Syrjälä
> > Intel
>
> --
> Ville Syrjälä
> Intel
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Intel-gfx] [PATCH 2/2] drm/i915: Swap ret and status returned from skl_pcode_request
2022-04-08 12:51 [Intel-gfx] [PATCH 0/2] Fix issues in skl_pcode_request Stanislav Lisovskiy
` (4 preceding siblings ...)
2022-04-08 15:18 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
@ 2022-04-11 8:11 ` Stanislav Lisovskiy
2022-04-11 9:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix issues in skl_pcode_request (rev2) Patchwork
` (2 subsequent siblings)
8 siblings, 0 replies; 17+ messages in thread
From: Stanislav Lisovskiy @ 2022-04-11 8:11 UTC (permalink / raw)
To: intel-gfx
If ret isn't zero, it is almost for sure ETIMEDOUT, because
we use it in wait_for macro which does continuous retries
until timeout is reached. If we still ran out of time and
retries, we most likely would be interested in getting status,
to understand what was the actual error propagated from PCode,
rather than to find out that we had a time out, which is anyway
quite obvious, if the function fails.
v2: Make it status ? status : ret(thanks Vinod for the hint)
Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
---
drivers/gpu/drm/i915/intel_pcode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_pcode.c b/drivers/gpu/drm/i915/intel_pcode.c
index fb6c43e8a02f..ac727546868e 100644
--- a/drivers/gpu/drm/i915/intel_pcode.c
+++ b/drivers/gpu/drm/i915/intel_pcode.c
@@ -202,7 +202,7 @@ int skl_pcode_request(struct drm_i915_private *i915, u32 mbox, u32 request,
out:
mutex_unlock(&i915->sb_lock);
- return ret ? ret : status;
+ return status ? status : ret;
#undef COND
}
--
2.24.1.485.gad05a3d8e5
^ permalink raw reply related [flat|nested] 17+ messages in thread
* [Intel-gfx] [PATCH 2/2] drm/i915: Swap ret and status returned from skl_pcode_request
2022-04-08 12:52 ` [Intel-gfx] [PATCH 2/2] drm/i915: Swap ret and status returned from skl_pcode_request Stanislav Lisovskiy
2022-04-08 17:41 ` Govindapillai, Vinod
@ 2022-04-11 8:13 ` Stanislav Lisovskiy
2022-04-11 8:35 ` Govindapillai, Vinod
1 sibling, 1 reply; 17+ messages in thread
From: Stanislav Lisovskiy @ 2022-04-11 8:13 UTC (permalink / raw)
To: intel-gfx
If ret isn't zero, it is almost for sure ETIMEDOUT, because
we use it in wait_for macro which does continuous retries
until timeout is reached. If we still ran out of time and
retries, we most likely would be interested in getting status,
to understand what was the actual error propagated from PCode,
rather than to find out that we had a time out, which is anyway
quite obvious, if the function fails.
v2: Make it status ? status : ret(thanks Vinod for the hint)
Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
---
drivers/gpu/drm/i915/intel_pcode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_pcode.c b/drivers/gpu/drm/i915/intel_pcode.c
index fb6c43e8a02f..ac727546868e 100644
--- a/drivers/gpu/drm/i915/intel_pcode.c
+++ b/drivers/gpu/drm/i915/intel_pcode.c
@@ -202,7 +202,7 @@ int skl_pcode_request(struct drm_i915_private *i915, u32 mbox, u32 request,
out:
mutex_unlock(&i915->sb_lock);
- return ret ? ret : status;
+ return status ? status : ret;
#undef COND
}
--
2.24.1.485.gad05a3d8e5
^ permalink raw reply related [flat|nested] 17+ messages in thread
* Re: [Intel-gfx] [PATCH 2/2] drm/i915: Swap ret and status returned from skl_pcode_request
2022-04-11 8:13 ` Stanislav Lisovskiy
@ 2022-04-11 8:35 ` Govindapillai, Vinod
0 siblings, 0 replies; 17+ messages in thread
From: Govindapillai, Vinod @ 2022-04-11 8:35 UTC (permalink / raw)
To: Lisovskiy, Stanislav, intel-gfx
Thanks!
Reviewed-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> -----Original Message-----
> From: Lisovskiy, Stanislav <stanislav.lisovskiy@intel.com>
> Sent: 11 April 2022 11:14
> To: intel-gfx@lists.freedesktop.org
> Cc: Lisovskiy, Stanislav <stanislav.lisovskiy@intel.com>; Govindapillai, Vinod
> <vinod.govindapillai@intel.com>; Saarinen, Jani <jani.saarinen@intel.com>
> Subject: [PATCH 2/2] drm/i915: Swap ret and status returned from
> skl_pcode_request
>
> If ret isn't zero, it is almost for sure ETIMEDOUT, because we use it in
> wait_for macro which does continuous retries until timeout is reached. If we
> still ran out of time and retries, we most likely would be interested in getting
> status, to understand what was the actual error propagated from PCode,
> rather than to find out that we had a time out, which is anyway quite
> obvious, if the function fails.
>
> v2: Make it status ? status : ret(thanks Vinod for the hint)
>
> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> ---
> drivers/gpu/drm/i915/intel_pcode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_pcode.c
> b/drivers/gpu/drm/i915/intel_pcode.c
> index fb6c43e8a02f..ac727546868e 100644
> --- a/drivers/gpu/drm/i915/intel_pcode.c
> +++ b/drivers/gpu/drm/i915/intel_pcode.c
> @@ -202,7 +202,7 @@ int skl_pcode_request(struct drm_i915_private *i915,
> u32 mbox, u32 request,
>
> out:
> mutex_unlock(&i915->sb_lock);
> - return ret ? ret : status;
> + return status ? status : ret;
> #undef COND
> }
>
> --
> 2.24.1.485.gad05a3d8e5
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix issues in skl_pcode_request (rev2)
2022-04-08 12:51 [Intel-gfx] [PATCH 0/2] Fix issues in skl_pcode_request Stanislav Lisovskiy
` (5 preceding siblings ...)
2022-04-11 8:11 ` [Intel-gfx] [PATCH 2/2] drm/i915: Swap ret and status returned from skl_pcode_request Stanislav Lisovskiy
@ 2022-04-11 9:27 ` Patchwork
2022-04-11 9:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-11 11:12 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
8 siblings, 0 replies; 17+ messages in thread
From: Patchwork @ 2022-04-11 9:27 UTC (permalink / raw)
To: Stanislav Lisovskiy; +Cc: intel-gfx
== Series Details ==
Series: Fix issues in skl_pcode_request (rev2)
URL : https://patchwork.freedesktop.org/series/102410/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
bd8790414748 drm/i915: Fix skl_pcode_try_request function
-:25: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#25:
We see en error because higher level api, still notices that status was wrong,
total: 0 errors, 1 warnings, 0 checks, 8 lines checked
135b427bdf31 drm/i915: Swap ret and status returned from skl_pcode_request
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for Fix issues in skl_pcode_request (rev2)
2022-04-08 12:51 [Intel-gfx] [PATCH 0/2] Fix issues in skl_pcode_request Stanislav Lisovskiy
` (6 preceding siblings ...)
2022-04-11 9:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix issues in skl_pcode_request (rev2) Patchwork
@ 2022-04-11 9:59 ` Patchwork
2022-04-11 11:12 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
8 siblings, 0 replies; 17+ messages in thread
From: Patchwork @ 2022-04-11 9:59 UTC (permalink / raw)
To: Stanislav Lisovskiy; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 5739 bytes --]
== Series Details ==
Series: Fix issues in skl_pcode_request (rev2)
URL : https://patchwork.freedesktop.org/series/102410/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11481 -> Patchwork_22838
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/index.html
Participating hosts (48 -> 44)
------------------------------
Additional (2): bat-hsw-1 fi-tgl-u2
Missing (6): shard-tglu fi-bsw-cyan fi-icl-u2 shard-rkl shard-dg1 fi-bdw-samus
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_22838:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@gem_lmem_swapping@parallel-random-engines:
- {bat-hsw-1}: NOTRUN -> [FAIL][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/bat-hsw-1/igt@gem_lmem_swapping@parallel-random-engines.html
Known issues
------------
Here are the changes found in Patchwork_22838 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_basic@semaphore:
- fi-hsw-4770: NOTRUN -> [SKIP][2] ([fdo#109271] / [fdo#109315]) +17 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/fi-hsw-4770/igt@amdgpu/amd_basic@semaphore.html
* igt@gem_exec_suspend@basic-s3@smem:
- fi-bdw-5557u: [PASS][3] -> [INCOMPLETE][4] ([i915#146])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3@smem.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3@smem.html
* igt@gem_huc_copy@huc-copy:
- fi-tgl-u2: NOTRUN -> [SKIP][5] ([i915#2190])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/fi-tgl-u2/igt@gem_huc_copy@huc-copy.html
* igt@kms_busy@basic@flip:
- fi-tgl-u2: NOTRUN -> [DMESG-WARN][6] ([i915#402])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/fi-tgl-u2/igt@kms_busy@basic@flip.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-tgl-u2: NOTRUN -> [SKIP][7] ([fdo#109284] / [fdo#111827]) +8 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/fi-tgl-u2/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic:
- fi-tgl-u2: NOTRUN -> [SKIP][8] ([i915#4103]) +1 similar issue
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/fi-tgl-u2/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-atomic.html
* igt@kms_force_connector_basic@force-load-detect:
- fi-tgl-u2: NOTRUN -> [SKIP][9] ([fdo#109285])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/fi-tgl-u2/igt@kms_force_connector_basic@force-load-detect.html
* igt@kms_setmode@basic-clone-single-crtc:
- fi-tgl-u2: NOTRUN -> [SKIP][10] ([i915#3555])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/fi-tgl-u2/igt@kms_setmode@basic-clone-single-crtc.html
#### Possible fixes ####
* igt@i915_selftest@live@hangcheck:
- fi-hsw-4770: [INCOMPLETE][11] ([i915#4785]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/fi-hsw-4770/igt@i915_selftest@live@hangcheck.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/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#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#146]: https://gitlab.freedesktop.org/drm/intel/issues/146
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#3012]: https://gitlab.freedesktop.org/drm/intel/issues/3012
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3576]: https://gitlab.freedesktop.org/drm/intel/issues/3576
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4391]: https://gitlab.freedesktop.org/drm/intel/issues/4391
[i915#4785]: https://gitlab.freedesktop.org/drm/intel/issues/4785
[i915#4897]: https://gitlab.freedesktop.org/drm/intel/issues/4897
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
Build changes
-------------
* Linux: CI_DRM_11481 -> Patchwork_22838
CI-20190529: 20190529
CI_DRM_11481: 9bf68eb47288411da23ce5c9967f27dba43bda1d @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6415: c3b690bd5f7fb1fb7ed786ab0f3b815930a6a55f @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_22838: 135b427bdf319d1cf8bbf6a5db802967a7a2d744 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
135b427bdf31 drm/i915: Swap ret and status returned from skl_pcode_request
bd8790414748 drm/i915: Fix skl_pcode_try_request function
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/index.html
[-- Attachment #2: Type: text/html, Size: 6059 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* [Intel-gfx] ✓ Fi.CI.IGT: success for Fix issues in skl_pcode_request (rev2)
2022-04-08 12:51 [Intel-gfx] [PATCH 0/2] Fix issues in skl_pcode_request Stanislav Lisovskiy
` (7 preceding siblings ...)
2022-04-11 9:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
@ 2022-04-11 11:12 ` Patchwork
8 siblings, 0 replies; 17+ messages in thread
From: Patchwork @ 2022-04-11 11:12 UTC (permalink / raw)
To: Stanislav Lisovskiy; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 30262 bytes --]
== Series Details ==
Series: Fix issues in skl_pcode_request (rev2)
URL : https://patchwork.freedesktop.org/series/102410/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11481_full -> Patchwork_22838_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (13 -> 11)
------------------------------
Missing (2): shard-rkl shard-dg1
Known issues
------------
Here are the changes found in Patchwork_22838_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_balancer@parallel-contexts:
- shard-kbl: NOTRUN -> [DMESG-WARN][1] ([i915#5614])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl4/igt@gem_exec_balancer@parallel-contexts.html
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-apl: [PASS][2] -> [FAIL][3] ([i915#2842])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-apl6/igt@gem_exec_fair@basic-pace-solo@rcs0.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-apl3/igt@gem_exec_fair@basic-pace-solo@rcs0.html
* igt@gem_exec_fair@basic-pace@vcs1:
- shard-kbl: [PASS][4] -> [FAIL][5] ([i915#2842]) +1 similar issue
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl1/igt@gem_exec_fair@basic-pace@vcs1.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl4/igt@gem_exec_fair@basic-pace@vcs1.html
* igt@gem_exec_flush@basic-batch-kernel-default-uc:
- shard-snb: [PASS][6] -> [SKIP][7] ([fdo#109271]) +1 similar issue
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-snb4/igt@gem_exec_flush@basic-batch-kernel-default-uc.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-snb6/igt@gem_exec_flush@basic-batch-kernel-default-uc.html
* igt@gem_exec_schedule@semaphore-user:
- shard-skl: [PASS][8] -> [DMESG-WARN][9] ([i915#1982]) +1 similar issue
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-skl6/igt@gem_exec_schedule@semaphore-user.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl4/igt@gem_exec_schedule@semaphore-user.html
* igt@gem_lmem_swapping@heavy-verify-random:
- shard-skl: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#4613])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl1/igt@gem_lmem_swapping@heavy-verify-random.html
* igt@gem_lmem_swapping@parallel-random-verify:
- shard-kbl: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4613]) +1 similar issue
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl1/igt@gem_lmem_swapping@parallel-random-verify.html
* igt@gem_lmem_swapping@verify:
- shard-apl: NOTRUN -> [SKIP][12] ([fdo#109271] / [i915#4613])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-apl2/igt@gem_lmem_swapping@verify.html
* igt@gem_pxp@regular-baseline-src-copy-readible:
- shard-kbl: NOTRUN -> [SKIP][13] ([fdo#109271]) +99 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl4/igt@gem_pxp@regular-baseline-src-copy-readible.html
* igt@gem_render_copy@yf-tiled-to-vebox-yf-tiled:
- shard-iclb: NOTRUN -> [SKIP][14] ([i915#768])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb6/igt@gem_render_copy@yf-tiled-to-vebox-yf-tiled.html
* igt@gem_userptr_blits@vma-merge:
- shard-skl: NOTRUN -> [FAIL][15] ([i915#3318])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl1/igt@gem_userptr_blits@vma-merge.html
* igt@gem_workarounds@suspend-resume-context:
- shard-apl: [PASS][16] -> [DMESG-WARN][17] ([i915#180]) +6 similar issues
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-apl1/igt@gem_workarounds@suspend-resume-context.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-apl1/igt@gem_workarounds@suspend-resume-context.html
* igt@gem_workarounds@suspend-resume-fd:
- shard-kbl: NOTRUN -> [DMESG-WARN][18] ([i915#180])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl6/igt@gem_workarounds@suspend-resume-fd.html
* igt@gen9_exec_parse@allowed-single:
- shard-glk: [PASS][19] -> [DMESG-WARN][20] ([i915#5566] / [i915#716])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-glk7/igt@gen9_exec_parse@allowed-single.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-glk2/igt@gen9_exec_parse@allowed-single.html
* igt@i915_pm_dc@dc6-dpms:
- shard-kbl: NOTRUN -> [FAIL][21] ([i915#454])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl1/igt@i915_pm_dc@dc6-dpms.html
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [PASS][22] -> [FAIL][23] ([i915#454])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-iclb2/igt@i915_pm_dc@dc6-psr.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb4/igt@i915_pm_dc@dc6-psr.html
* igt@i915_pm_rc6_residency@rc6-idle:
- shard-iclb: NOTRUN -> [WARN][24] ([i915#2684])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb8/igt@i915_pm_rc6_residency@rc6-idle.html
* igt@i915_pm_rpm@pc8-residency:
- shard-iclb: NOTRUN -> [SKIP][25] ([fdo#109293] / [fdo#109506])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb8/igt@i915_pm_rpm@pc8-residency.html
* igt@i915_suspend@debugfs-reader:
- shard-kbl: [PASS][26] -> [DMESG-WARN][27] ([i915#180]) +1 similar issue
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl1/igt@i915_suspend@debugfs-reader.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl6/igt@i915_suspend@debugfs-reader.html
* igt@kms_async_flips@crc:
- shard-skl: NOTRUN -> [FAIL][28] ([i915#4272])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl1/igt@kms_async_flips@crc.html
* igt@kms_big_fb@linear-64bpp-rotate-270:
- shard-iclb: NOTRUN -> [SKIP][29] ([fdo#110725] / [fdo#111614])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb8/igt@kms_big_fb@linear-64bpp-rotate-270.html
* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip:
- shard-apl: NOTRUN -> [SKIP][30] ([fdo#109271] / [i915#3777]) +1 similar issue
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-apl2/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip.html
* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip:
- shard-kbl: NOTRUN -> [SKIP][31] ([fdo#109271] / [i915#3777])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl1/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip.html
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip:
- shard-skl: NOTRUN -> [SKIP][32] ([fdo#109271] / [i915#3777]) +1 similar issue
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl1/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip.html
* igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-async-flip:
- shard-skl: NOTRUN -> [FAIL][33] ([i915#3763])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl1/igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-async-flip.html
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-async-flip:
- shard-skl: NOTRUN -> [FAIL][34] ([i915#3743])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl6/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-async-flip.html
* igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][35] ([fdo#109271] / [i915#3886])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-apl2/igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][36] ([fdo#109271] / [i915#3886]) +7 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl2/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs:
- shard-apl: NOTRUN -> [SKIP][37] ([fdo#109271]) +50 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-apl2/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs.html
* igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc:
- shard-kbl: NOTRUN -> [SKIP][38] ([fdo#109271] / [i915#3886]) +1 similar issue
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl4/igt@kms_ccs@pipe-a-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc:
- shard-iclb: NOTRUN -> [SKIP][39] ([fdo#109278] / [i915#3886]) +2 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb8/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-d-bad-rotation-90-yf_tiled_ccs:
- shard-iclb: NOTRUN -> [SKIP][40] ([fdo#109278]) +9 similar issues
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb6/igt@kms_ccs@pipe-d-bad-rotation-90-yf_tiled_ccs.html
* igt@kms_chamelium@dp-hpd-storm-disable:
- shard-apl: NOTRUN -> [SKIP][41] ([fdo#109271] / [fdo#111827]) +4 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-apl2/igt@kms_chamelium@dp-hpd-storm-disable.html
* igt@kms_color_chamelium@pipe-b-ctm-max:
- shard-skl: NOTRUN -> [SKIP][42] ([fdo#109271] / [fdo#111827]) +13 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl10/igt@kms_color_chamelium@pipe-b-ctm-max.html
* igt@kms_color_chamelium@pipe-c-gamma:
- shard-kbl: NOTRUN -> [SKIP][43] ([fdo#109271] / [fdo#111827]) +12 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl3/igt@kms_color_chamelium@pipe-c-gamma.html
* igt@kms_content_protection@mei_interface:
- shard-iclb: NOTRUN -> [SKIP][44] ([fdo#109300] / [fdo#111066])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb6/igt@kms_content_protection@mei_interface.html
* igt@kms_cursor_crc@pipe-b-cursor-32x10-offscreen:
- shard-tglb: NOTRUN -> [SKIP][45] ([i915#3359])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-tglb8/igt@kms_cursor_crc@pipe-b-cursor-32x10-offscreen.html
* igt@kms_cursor_legacy@cursora-vs-flipb-varying-size:
- shard-iclb: NOTRUN -> [SKIP][46] ([fdo#109274] / [fdo#109278])
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb8/igt@kms_cursor_legacy@cursora-vs-flipb-varying-size.html
* igt@kms_draw_crc@draw-method-xrgb8888-render-4tiled:
- shard-iclb: NOTRUN -> [SKIP][47] ([i915#5287])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb8/igt@kms_draw_crc@draw-method-xrgb8888-render-4tiled.html
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-apl: [PASS][48] -> [INCOMPLETE][49] ([i915#180] / [i915#1982])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-apl8/igt@kms_fbcon_fbt@fbc-suspend.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-apl2/igt@kms_fbcon_fbt@fbc-suspend.html
- shard-kbl: [PASS][50] -> [INCOMPLETE][51] ([i915#180])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl1/igt@kms_fbcon_fbt@fbc-suspend.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl7/igt@kms_fbcon_fbt@fbc-suspend.html
* igt@kms_flip@2x-dpms-vs-vblank-race:
- shard-iclb: NOTRUN -> [SKIP][52] ([fdo#109274])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb8/igt@kms_flip@2x-dpms-vs-vblank-race.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling:
- shard-iclb: [PASS][53] -> [SKIP][54] ([i915#3701])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-iclb1/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-mmap-gtt:
- shard-iclb: NOTRUN -> [SKIP][55] ([fdo#109280]) +5 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb8/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-indfb-draw-mmap-gtt.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-shrfb-draw-render:
- shard-tglb: NOTRUN -> [SKIP][56] ([fdo#109280] / [fdo#111825])
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-tglb8/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-pri-shrfb-draw-render.html
* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-blt:
- shard-skl: NOTRUN -> [SKIP][57] ([fdo#109271]) +188 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl1/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-pri-indfb-draw-blt.html
* igt@kms_pipe_b_c_ivb@enable-pipe-c-while-b-has-3-lanes:
- shard-iclb: NOTRUN -> [SKIP][58] ([fdo#109289])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb8/igt@kms_pipe_b_c_ivb@enable-pipe-c-while-b-has-3-lanes.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-7efc:
- shard-skl: NOTRUN -> [FAIL][59] ([fdo#108145] / [i915#265]) +3 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl6/igt@kms_plane_alpha_blend@pipe-a-alpha-7efc.html
* igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max:
- shard-kbl: NOTRUN -> [FAIL][60] ([fdo#108145] / [i915#265]) +1 similar issue
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl4/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-max.html
* igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-5@pipe-a-edp-1-planes-upscale-downscale:
- shard-iclb: [PASS][61] -> [SKIP][62] ([i915#5235]) +2 similar issues
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-iclb1/igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-5@pipe-a-edp-1-planes-upscale-downscale.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb2/igt@kms_plane_scaling@planes-unity-scaling-downscale-factor-0-5@pipe-a-edp-1-planes-upscale-downscale.html
* igt@kms_psr2_sf@cursor-plane-update-sf:
- shard-skl: NOTRUN -> [SKIP][63] ([fdo#109271] / [i915#658]) +1 similar issue
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl2/igt@kms_psr2_sf@cursor-plane-update-sf.html
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area:
- shard-apl: NOTRUN -> [SKIP][64] ([fdo#109271] / [i915#658])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-apl2/igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area.html
* igt@kms_psr2_sf@plane-move-sf-dmg-area:
- shard-iclb: NOTRUN -> [SKIP][65] ([fdo#111068] / [i915#658])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb6/igt@kms_psr2_sf@plane-move-sf-dmg-area.html
* igt@kms_psr@psr2_cursor_blt:
- shard-iclb: [PASS][66] -> [SKIP][67] ([fdo#109441]) +1 similar issue
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-iclb2/igt@kms_psr@psr2_cursor_blt.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb4/igt@kms_psr@psr2_cursor_blt.html
* igt@kms_psr@psr2_sprite_mmap_cpu:
- shard-iclb: NOTRUN -> [SKIP][68] ([fdo#109441])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb8/igt@kms_psr@psr2_sprite_mmap_cpu.html
* igt@kms_psr_stress_test@invalidate-primary-flip-overlay:
- shard-iclb: [PASS][69] -> [SKIP][70] ([i915#5519])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-iclb5/igt@kms_psr_stress_test@invalidate-primary-flip-overlay.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb4/igt@kms_psr_stress_test@invalidate-primary-flip-overlay.html
* igt@kms_rotation_crc@primary-4-tiled-reflect-x-180:
- shard-iclb: NOTRUN -> [SKIP][71] ([i915#5289])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb8/igt@kms_rotation_crc@primary-4-tiled-reflect-x-180.html
* igt@kms_scaling_modes@scaling-mode-none@edp-1-pipe-c:
- shard-iclb: NOTRUN -> [SKIP][72] ([i915#5030]) +2 similar issues
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb6/igt@kms_scaling_modes@scaling-mode-none@edp-1-pipe-c.html
* igt@kms_vrr@flip-basic:
- shard-tglb: NOTRUN -> [SKIP][73] ([fdo#109502])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-tglb8/igt@kms_vrr@flip-basic.html
* igt@kms_writeback@writeback-pixel-formats:
- shard-skl: NOTRUN -> [SKIP][74] ([fdo#109271] / [i915#2437]) +1 similar issue
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl6/igt@kms_writeback@writeback-pixel-formats.html
* igt@prime_nv_test@i915_nv_sharing:
- shard-iclb: NOTRUN -> [SKIP][75] ([fdo#109291])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb6/igt@prime_nv_test@i915_nv_sharing.html
* igt@syncobj_timeline@invalid-transfer-non-existent-point:
- shard-kbl: NOTRUN -> [DMESG-WARN][76] ([i915#5098])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl1/igt@syncobj_timeline@invalid-transfer-non-existent-point.html
* igt@syncobj_timeline@transfer-timeline-point:
- shard-apl: NOTRUN -> [DMESG-FAIL][77] ([i915#5098])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-apl8/igt@syncobj_timeline@transfer-timeline-point.html
* igt@sysfs_clients@fair-0:
- shard-skl: NOTRUN -> [SKIP][78] ([fdo#109271] / [i915#2994]) +2 similar issues
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl1/igt@sysfs_clients@fair-0.html
* igt@sysfs_clients@fair-7:
- shard-apl: NOTRUN -> [SKIP][79] ([fdo#109271] / [i915#2994])
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-apl2/igt@sysfs_clients@fair-7.html
#### Possible fixes ####
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-iclb: [FAIL][80] ([i915#2842]) -> [PASS][81]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-iclb7/igt@gem_exec_fair@basic-none-share@rcs0.html
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb3/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [FAIL][82] ([i915#2842]) -> [PASS][83]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-glk3/igt@gem_exec_fair@basic-pace-share@rcs0.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-glk9/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-kbl: [FAIL][84] ([i915#2842]) -> [PASS][85]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl1/igt@gem_exec_fair@basic-pace@vecs0.html
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl4/igt@gem_exec_fair@basic-pace@vecs0.html
- shard-tglb: [FAIL][86] ([i915#2842]) -> [PASS][87]
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-tglb3/igt@gem_exec_fair@basic-pace@vecs0.html
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-tglb8/igt@gem_exec_fair@basic-pace@vecs0.html
* igt@gem_exec_flush@basic-wb-rw-before-default:
- shard-snb: [SKIP][88] ([fdo#109271]) -> [PASS][89] +3 similar issues
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-snb6/igt@gem_exec_flush@basic-wb-rw-before-default.html
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-snb7/igt@gem_exec_flush@basic-wb-rw-before-default.html
* igt@i915_selftest@live@gt_pm:
- {shard-tglu}: [DMESG-FAIL][90] ([i915#3987]) -> [PASS][91]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-tglu-6/igt@i915_selftest@live@gt_pm.html
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-tglu-3/igt@i915_selftest@live@gt_pm.html
* igt@kms_big_fb@y-tiled-32bpp-rotate-0:
- {shard-tglu}: [DMESG-WARN][92] ([i915#402]) -> [PASS][93]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-tglu-2/igt@kms_big_fb@y-tiled-32bpp-rotate-0.html
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-tglu-3/igt@kms_big_fb@y-tiled-32bpp-rotate-0.html
* igt@kms_flip@flip-vs-suspend@a-dp1:
- shard-apl: [DMESG-WARN][94] ([i915#180]) -> [PASS][95] +3 similar issues
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-apl3/igt@kms_flip@flip-vs-suspend@a-dp1.html
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-apl7/igt@kms_flip@flip-vs-suspend@a-dp1.html
* igt@kms_flip@flip-vs-suspend@c-dp1:
- shard-kbl: [INCOMPLETE][96] -> [PASS][97]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl3/igt@kms_flip@flip-vs-suspend@c-dp1.html
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl4/igt@kms_flip@flip-vs-suspend@c-dp1.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-kbl: [DMESG-WARN][98] ([i915#180]) -> [PASS][99] +2 similar issues
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl7/igt@kms_frontbuffer_tracking@fbc-suspend.html
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl3/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_frontbuffer_tracking@psr-suspend:
- shard-skl: [INCOMPLETE][100] ([i915#123] / [i915#1982]) -> [PASS][101]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-skl10/igt@kms_frontbuffer_tracking@psr-suspend.html
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl10/igt@kms_frontbuffer_tracking@psr-suspend.html
* igt@kms_hdr@bpc-switch-dpms@bpc-switch-dpms-edp-1-pipe-a:
- shard-skl: [FAIL][102] ([i915#1188]) -> [PASS][103]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-skl10/igt@kms_hdr@bpc-switch-dpms@bpc-switch-dpms-edp-1-pipe-a.html
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl4/igt@kms_hdr@bpc-switch-dpms@bpc-switch-dpms-edp-1-pipe-a.html
* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-skl: [FAIL][104] ([fdo#108145] / [i915#265]) -> [PASS][105] +1 similar issue
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-skl4/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-skl9/igt@kms_plane_alpha_blend@pipe-a-coverage-7efc.html
* igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-b-edp-1-scaler-with-clipping-clamping:
- shard-iclb: [INCOMPLETE][106] ([i915#5243]) -> [PASS][107]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-iclb2/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-b-edp-1-scaler-with-clipping-clamping.html
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb4/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-b-edp-1-scaler-with-clipping-clamping.html
* igt@kms_psr2_su@frontbuffer-xrgb8888:
- shard-iclb: [SKIP][108] ([fdo#109642] / [fdo#111068] / [i915#658]) -> [PASS][109]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-iclb1/igt@kms_psr2_su@frontbuffer-xrgb8888.html
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb2/igt@kms_psr2_su@frontbuffer-xrgb8888.html
* igt@kms_psr@psr2_cursor_mmap_cpu:
- shard-iclb: [SKIP][110] ([fdo#109441]) -> [PASS][111] +1 similar issue
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-iclb4/igt@kms_psr@psr2_cursor_mmap_cpu.html
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb2/igt@kms_psr@psr2_cursor_mmap_cpu.html
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-kbl: [INCOMPLETE][112] ([i915#3614]) -> [PASS][113]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl4/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl1/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
* igt@perf@polling-parameterized:
- shard-tglb: [FAIL][114] ([i915#1542]) -> [PASS][115]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-tglb6/igt@perf@polling-parameterized.html
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-tglb8/igt@perf@polling-parameterized.html
* igt@syncobj_wait@invalid-signal-bad-pad:
- {shard-tglu}: [INCOMPLETE][116] ([i915#2295]) -> [PASS][117]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-tglu-1/igt@syncobj_wait@invalid-signal-bad-pad.html
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-tglu-1/igt@syncobj_wait@invalid-signal-bad-pad.html
#### Warnings ####
* igt@gem_exec_balancer@parallel:
- shard-iclb: [SKIP][118] ([i915#4525]) -> [DMESG-WARN][119] ([i915#5614])
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-iclb5/igt@gem_exec_balancer@parallel.html
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb4/igt@gem_exec_balancer@parallel.html
* igt@gem_exec_balancer@parallel-out-fence:
- shard-iclb: [DMESG-WARN][120] ([i915#5614]) -> [SKIP][121] ([i915#4525])
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-iclb4/igt@gem_exec_balancer@parallel-out-fence.html
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb8/igt@gem_exec_balancer@parallel-out-fence.html
* igt@kms_psr2_sf@overlay-plane-move-continuous-sf:
- shard-iclb: [SKIP][122] ([i915#2920]) -> [SKIP][123] ([i915#658])
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-iclb2/igt@kms_psr2_sf@overlay-plane-move-continuous-sf.html
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-iclb4/igt@kms_psr2_sf@overlay-plane-move-continuous-sf.html
* igt@runner@aborted:
- shard-kbl: ([FAIL][124], [FAIL][125], [FAIL][126], [FAIL][127], [FAIL][128], [FAIL][129], [FAIL][130], [FAIL][131], [FAIL][132], [FAIL][133], [FAIL][134], [FAIL][135]) ([fdo#109271] / [i915#180] / [i915#1814] / [i915#3002] / [i915#4312] / [i915#5257]) -> ([FAIL][136], [FAIL][137], [FAIL][138], [FAIL][139], [FAIL][140], [FAIL][141], [FAIL][142], [FAIL][143], [FAIL][144], [FAIL][145], [FAIL][146], [FAIL][147], [FAIL][148], [FAIL][149], [FAIL][150]) ([i915#180] / [i915#1814] / [i915#3002] / [i915#4312] / [i915#5257] / [i915#92])
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl4/igt@runner@aborted.html
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl3/igt@runner@aborted.html
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl6/igt@runner@aborted.html
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl7/igt@runner@aborted.html
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl4/igt@runner@aborted.html
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl3/igt@runner@aborted.html
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl7/igt@runner@aborted.html
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl6/igt@runner@aborted.html
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl7/igt@runner@aborted.html
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl7/igt@runner@aborted.html
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl6/igt@runner@aborted.html
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11481/shard-kbl4/igt@runner@aborted.html
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl3/igt@runner@aborted.html
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl7/igt@runner@aborted.html
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl6/igt@runner@aborted.html
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl7/igt@runner@aborted.html
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl3/igt@runner@aborted.html
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl6/igt@runner@aborted.html
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl1/igt@runner@aborted.html
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl1/igt@runner@aborted.html
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl7/igt@runner@aborted.html
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl6/igt@runner@aborted.html
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl6/igt@runner@aborted.html
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/shard-kbl6/igt@runner@aborted.html
[148]: https://intel-gfx-ci.01.org/tree/drm-ti
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22838/index.html
[-- Attachment #2: Type: text/html, Size: 33771 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2022-04-11 11:12 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-04-08 12:51 [Intel-gfx] [PATCH 0/2] Fix issues in skl_pcode_request Stanislav Lisovskiy
2022-04-08 12:51 ` [Intel-gfx] [PATCH 1/2] drm/i915: Fix skl_pcode_try_request function Stanislav Lisovskiy
2022-04-08 15:46 ` Ville Syrjälä
2022-04-08 15:59 ` Ville Syrjälä
2022-04-08 17:49 ` Lisovskiy, Stanislav
2022-04-08 17:39 ` Lisovskiy, Stanislav
2022-04-08 12:52 ` [Intel-gfx] [PATCH 2/2] drm/i915: Swap ret and status returned from skl_pcode_request Stanislav Lisovskiy
2022-04-08 17:41 ` Govindapillai, Vinod
2022-04-11 8:13 ` Stanislav Lisovskiy
2022-04-11 8:35 ` Govindapillai, Vinod
2022-04-08 13:29 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix issues in skl_pcode_request Patchwork
2022-04-08 14:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-08 15:18 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-04-11 8:11 ` [Intel-gfx] [PATCH 2/2] drm/i915: Swap ret and status returned from skl_pcode_request Stanislav Lisovskiy
2022-04-11 9:27 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Fix issues in skl_pcode_request (rev2) Patchwork
2022-04-11 9:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-04-11 11:12 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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.