* [PATCH] drm/i915/guc: Don't error on reset of banned context
@ 2022-01-07 0:31 ` John.C.Harrison
0 siblings, 0 replies; 8+ messages in thread
From: John.C.Harrison @ 2022-01-07 0:31 UTC (permalink / raw)
To: Intel-GFX; +Cc: John Harrison, DRI-Devel
From: John Harrison <John.C.Harrison@Intel.com>
There is a race (already documented in the code) whereby a context can
be (re-)queued for submission at the same time as it is being banned
due to a hang and reset. That leads to a hang/reset report from GuC
for a context which i915 thinks is already banned.
While the race is indented to be fixed in a future GuC update, there
is no actual harm beyond the wasted execution time of that new hang
detection period. The context has already been banned for bad
behaviour so a fresh hang is hardly surprising and certainly isn't
going to be losing any work that wouldn't already have been lost if
there was no race.
So don't treat this situation as an error. The error message is seen
by the CI system as something fatal and causes test failures. Instead,
just print an informational so the user at least knows a context reset
occurred (given that the error capture is being skipped).
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
---
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
index 9989d121127d..e8a32a7e7daf 100644
--- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
+++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
@@ -3978,6 +3978,10 @@ static void guc_handle_context_reset(struct intel_guc *guc,
!context_blocked(ce))) {
capture_error_state(guc, ce);
guc_context_replay(ce);
+ } else if (intel_context_is_banned(ce)) {
+ drm_info(&guc_to_gt(guc)->i915->drm,
+ "Reset notificaion for banned context 0x%04X on %s",
+ ce->guc_id.id, ce->engine->name);
} else {
drm_err(&guc_to_gt(guc)->i915->drm,
"Invalid GuC engine reset notificaion for 0x%04X on %s: banned = %d, blocked = %d",
--
2.25.1
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [Intel-gfx] [PATCH] drm/i915/guc: Don't error on reset of banned context
@ 2022-01-07 0:31 ` John.C.Harrison
0 siblings, 0 replies; 8+ messages in thread
From: John.C.Harrison @ 2022-01-07 0:31 UTC (permalink / raw)
To: Intel-GFX; +Cc: DRI-Devel
From: John Harrison <John.C.Harrison@Intel.com>
There is a race (already documented in the code) whereby a context can
be (re-)queued for submission at the same time as it is being banned
due to a hang and reset. That leads to a hang/reset report from GuC
for a context which i915 thinks is already banned.
While the race is indented to be fixed in a future GuC update, there
is no actual harm beyond the wasted execution time of that new hang
detection period. The context has already been banned for bad
behaviour so a fresh hang is hardly surprising and certainly isn't
going to be losing any work that wouldn't already have been lost if
there was no race.
So don't treat this situation as an error. The error message is seen
by the CI system as something fatal and causes test failures. Instead,
just print an informational so the user at least knows a context reset
occurred (given that the error capture is being skipped).
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
---
drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
index 9989d121127d..e8a32a7e7daf 100644
--- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
+++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
@@ -3978,6 +3978,10 @@ static void guc_handle_context_reset(struct intel_guc *guc,
!context_blocked(ce))) {
capture_error_state(guc, ce);
guc_context_replay(ce);
+ } else if (intel_context_is_banned(ce)) {
+ drm_info(&guc_to_gt(guc)->i915->drm,
+ "Reset notificaion for banned context 0x%04X on %s",
+ ce->guc_id.id, ce->engine->name);
} else {
drm_err(&guc_to_gt(guc)->i915->drm,
"Invalid GuC engine reset notificaion for 0x%04X on %s: banned = %d, blocked = %d",
--
2.25.1
^ permalink raw reply related [flat|nested] 8+ messages in thread
* Re: [PATCH] drm/i915/guc: Don't error on reset of banned context
2022-01-07 0:31 ` [Intel-gfx] " John.C.Harrison
@ 2022-01-07 0:35 ` John Harrison
-1 siblings, 0 replies; 8+ messages in thread
From: John Harrison @ 2022-01-07 0:35 UTC (permalink / raw)
To: Intel-GFX; +Cc: DRI-Devel
On 1/6/2022 16:31, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> There is a race (already documented in the code) whereby a context can
> be (re-)queued for submission at the same time as it is being banned
> due to a hang and reset. That leads to a hang/reset report from GuC
> for a context which i915 thinks is already banned.
>
> While the race is indented to be fixed in a future GuC update, there
> is no actual harm beyond the wasted execution time of that new hang
> detection period. The context has already been banned for bad
> behaviour so a fresh hang is hardly surprising and certainly isn't
> going to be losing any work that wouldn't already have been lost if
> there was no race.
>
> So don't treat this situation as an error. The error message is seen
> by the CI system as something fatal and causes test failures. Instead,
> just print an informational so the user at least knows a context reset
> occurred (given that the error capture is being skipped).
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
PS: Meant to add:
Fixes: 249af7242af72 ("drm/i915/guc: Report error on invalid reset
notification")
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/guc: Don't error on reset of banned context
@ 2022-01-07 0:35 ` John Harrison
0 siblings, 0 replies; 8+ messages in thread
From: John Harrison @ 2022-01-07 0:35 UTC (permalink / raw)
To: Intel-GFX; +Cc: DRI-Devel
On 1/6/2022 16:31, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> There is a race (already documented in the code) whereby a context can
> be (re-)queued for submission at the same time as it is being banned
> due to a hang and reset. That leads to a hang/reset report from GuC
> for a context which i915 thinks is already banned.
>
> While the race is indented to be fixed in a future GuC update, there
> is no actual harm beyond the wasted execution time of that new hang
> detection period. The context has already been banned for bad
> behaviour so a fresh hang is hardly surprising and certainly isn't
> going to be losing any work that wouldn't already have been lost if
> there was no race.
>
> So don't treat this situation as an error. The error message is seen
> by the CI system as something fatal and causes test failures. Instead,
> just print an informational so the user at least knows a context reset
> occurred (given that the error capture is being skipped).
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
PS: Meant to add:
Fixes: 249af7242af72 ("drm/i915/guc: Report error on invalid reset
notification")
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/guc: Don't error on reset of banned context
2022-01-07 0:31 ` [Intel-gfx] " John.C.Harrison
(?)
(?)
@ 2022-01-07 1:49 ` Patchwork
-1 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2022-01-07 1:49 UTC (permalink / raw)
To: John Harrison; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 5961 bytes --]
== Series Details ==
Series: drm/i915/guc: Don't error on reset of banned context
URL : https://patchwork.freedesktop.org/series/98580/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11053 -> Patchwork_21937
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/index.html
Participating hosts (43 -> 37)
------------------------------
Additional (1): fi-pnv-d510
Missing (7): bat-dg1-6 bat-dg1-5 bat-adlp-6 bat-adlp-4 bat-rpls-1 fi-bdw-samus bat-jsl-1
Known issues
------------
Here are the changes found in Patchwork_21937 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_basic@cs-gfx:
- fi-kbl-soraka: NOTRUN -> [SKIP][1] ([fdo#109271]) +22 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/fi-kbl-soraka/igt@amdgpu/amd_basic@cs-gfx.html
* igt@gem_exec_suspend@basic-s3@smem:
- fi-bdw-5557u: [PASS][2] -> [INCOMPLETE][3] ([i915#146])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3@smem.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/fi-bdw-5557u/igt@gem_exec_suspend@basic-s3@smem.html
* igt@gem_huc_copy@huc-copy:
- fi-kbl-soraka: NOTRUN -> [SKIP][4] ([fdo#109271] / [i915#2190])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/fi-kbl-soraka/igt@gem_huc_copy@huc-copy.html
* igt@gem_lmem_swapping@basic:
- fi-kbl-soraka: NOTRUN -> [SKIP][5] ([fdo#109271] / [i915#4613]) +3 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/fi-kbl-soraka/igt@gem_lmem_swapping@basic.html
* igt@i915_selftest@live@execlists:
- fi-bsw-n3050: [PASS][6] -> [INCOMPLETE][7] ([i915#2940])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/fi-bsw-n3050/igt@i915_selftest@live@execlists.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/fi-bsw-n3050/igt@i915_selftest@live@execlists.html
* igt@i915_selftest@live@gt_pm:
- fi-kbl-soraka: NOTRUN -> [DMESG-FAIL][8] ([i915#1886] / [i915#2291])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/fi-kbl-soraka/igt@i915_selftest@live@gt_pm.html
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-kbl-soraka: NOTRUN -> [SKIP][9] ([fdo#109271] / [fdo#111827]) +8 similar issues
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/fi-kbl-soraka/igt@kms_chamelium@common-hpd-after-suspend.html
* igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d:
- fi-kbl-soraka: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#533])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/fi-kbl-soraka/igt@kms_pipe_crc_basic@compare-crc-sanitycheck-pipe-d.html
* igt@prime_vgem@basic-userptr:
- fi-pnv-d510: NOTRUN -> [SKIP][11] ([fdo#109271]) +57 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/fi-pnv-d510/igt@prime_vgem@basic-userptr.html
* igt@runner@aborted:
- fi-bsw-n3050: NOTRUN -> [FAIL][12] ([fdo#109271] / [i915#1436] / [i915#3428] / [i915#4312])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/fi-bsw-n3050/igt@runner@aborted.html
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s0@smem:
- fi-kbl-soraka: [INCOMPLETE][13] -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/fi-kbl-soraka/igt@gem_exec_suspend@basic-s0@smem.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/fi-kbl-soraka/igt@gem_exec_suspend@basic-s0@smem.html
* igt@i915_pm_rpm@basic-pci-d3-state:
- fi-skl-6600u: [FAIL][15] ([i915#3239]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/fi-skl-6600u/igt@i915_pm_rpm@basic-pci-d3-state.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/fi-skl-6600u/igt@i915_pm_rpm@basic-pci-d3-state.html
* igt@i915_selftest@live@gt_heartbeat:
- fi-bxt-dsi: [DMESG-FAIL][17] ([i915#541]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/fi-bxt-dsi/igt@i915_selftest@live@gt_heartbeat.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/fi-bxt-dsi/igt@i915_selftest@live@gt_heartbeat.html
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#146]: https://gitlab.freedesktop.org/drm/intel/issues/146
[i915#1886]: https://gitlab.freedesktop.org/drm/intel/issues/1886
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2291]: https://gitlab.freedesktop.org/drm/intel/issues/2291
[i915#2940]: https://gitlab.freedesktop.org/drm/intel/issues/2940
[i915#3239]: https://gitlab.freedesktop.org/drm/intel/issues/3239
[i915#3428]: https://gitlab.freedesktop.org/drm/intel/issues/3428
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#541]: https://gitlab.freedesktop.org/drm/intel/issues/541
Build changes
-------------
* Linux: CI_DRM_11053 -> Patchwork_21937
CI-20190529: 20190529
CI_DRM_11053: f0ad19ec6238528d9ea1ee54c9dcde4e0119f1e5 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6325: ac29e097d4ff0f2e269a955ca86c5eb23908467a @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_21937: 682d623fb1494a83af586a456dc422cbbe6cc13a @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
682d623fb149 drm/i915/guc: Don't error on reset of banned context
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/index.html
[-- Attachment #2: Type: text/html, Size: 7283 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/guc: Don't error on reset of banned context
2022-01-07 0:31 ` [Intel-gfx] " John.C.Harrison
` (2 preceding siblings ...)
(?)
@ 2022-01-07 17:06 ` Patchwork
-1 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2022-01-07 17:06 UTC (permalink / raw)
To: John Harrison; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 30275 bytes --]
== Series Details ==
Series: drm/i915/guc: Don't error on reset of banned context
URL : https://patchwork.freedesktop.org/series/98580/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11053_full -> Patchwork_21937_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (13 -> 13)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_21937_full:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@gem_create@busy-create:
- {shard-rkl}: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-rkl-2/igt@gem_create@busy-create.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-rkl-5/igt@gem_create@busy-create.html
* igt@gem_exec_whisper@basic-contexts-forked:
- {shard-rkl}: [PASS][3] -> [INCOMPLETE][4] +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-rkl-2/igt@gem_exec_whisper@basic-contexts-forked.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-rkl-5/igt@gem_exec_whisper@basic-contexts-forked.html
* igt@gem_exec_whisper@basic-queues-forked:
- {shard-rkl}: ([PASS][5], [PASS][6]) -> ([INCOMPLETE][7], [PASS][8])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-rkl-2/igt@gem_exec_whisper@basic-queues-forked.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-rkl-4/igt@gem_exec_whisper@basic-queues-forked.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-rkl-5/igt@gem_exec_whisper@basic-queues-forked.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-rkl-4/igt@gem_exec_whisper@basic-queues-forked.html
* igt@gem_workarounds@suspend-resume:
- {shard-rkl}: [PASS][9] -> [DMESG-WARN][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-rkl-5/igt@gem_workarounds@suspend-resume.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-rkl-2/igt@gem_workarounds@suspend-resume.html
* igt@i915_pm_rpm@basic-pci-d3-state:
- {shard-rkl}: [SKIP][11] ([fdo#109308]) -> [INCOMPLETE][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-rkl-2/igt@i915_pm_rpm@basic-pci-d3-state.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-rkl-5/igt@i915_pm_rpm@basic-pci-d3-state.html
Known issues
------------
Here are the changes found in Patchwork_21937_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_create@create-massive:
- shard-skl: NOTRUN -> [DMESG-WARN][13] ([i915#3002])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl4/igt@gem_create@create-massive.html
* igt@gem_ctx_isolation@preservation-s3@rcs0:
- shard-apl: [PASS][14] -> [DMESG-WARN][15] ([i915#180]) +4 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-apl6/igt@gem_ctx_isolation@preservation-s3@rcs0.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-apl1/igt@gem_ctx_isolation@preservation-s3@rcs0.html
* igt@gem_ctx_isolation@preservation-s3@vcs0:
- shard-kbl: [PASS][16] -> [DMESG-WARN][17] ([i915#180]) +2 similar issues
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-kbl3/igt@gem_ctx_isolation@preservation-s3@vcs0.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-kbl1/igt@gem_ctx_isolation@preservation-s3@vcs0.html
* igt@gem_ctx_sseu@invalid-args:
- shard-tglb: NOTRUN -> [SKIP][18] ([i915#280])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb1/igt@gem_ctx_sseu@invalid-args.html
* igt@gem_eio@in-flight-1us:
- shard-tglb: [PASS][19] -> [TIMEOUT][20] ([i915#3063])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-tglb5/igt@gem_eio@in-flight-1us.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb2/igt@gem_eio@in-flight-1us.html
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: [PASS][21] -> [FAIL][22] ([i915#2846])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-kbl4/igt@gem_exec_fair@basic-deadline.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-kbl1/igt@gem_exec_fair@basic-deadline.html
- shard-glk: [PASS][23] -> [FAIL][24] ([i915#2846])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-glk7/igt@gem_exec_fair@basic-deadline.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-glk7/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-flow@rcs0:
- shard-skl: NOTRUN -> [SKIP][25] ([fdo#109271]) +200 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl10/igt@gem_exec_fair@basic-flow@rcs0.html
* igt@gem_exec_fair@basic-none@vcs0:
- shard-kbl: [PASS][26] -> [FAIL][27] ([i915#2842]) +1 similar issue
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-kbl3/igt@gem_exec_fair@basic-none@vcs0.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-kbl7/igt@gem_exec_fair@basic-none@vcs0.html
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [PASS][28] -> [FAIL][29] ([i915#2842])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-glk2/igt@gem_exec_fair@basic-pace-share@rcs0.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-glk8/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@gem_exec_fair@basic-pace@vcs1:
- shard-iclb: NOTRUN -> [FAIL][30] ([i915#2842]) +1 similar issue
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-iclb1/igt@gem_exec_fair@basic-pace@vcs1.html
* igt@gem_exec_fair@basic-sync@rcs0:
- shard-tglb: [PASS][31] -> [SKIP][32] ([i915#2848])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-tglb7/igt@gem_exec_fair@basic-sync@rcs0.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb8/igt@gem_exec_fair@basic-sync@rcs0.html
* igt@gem_lmem_swapping@random:
- shard-glk: NOTRUN -> [SKIP][33] ([fdo#109271] / [i915#4613])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-glk5/igt@gem_lmem_swapping@random.html
* igt@gem_lmem_swapping@random-engines:
- shard-skl: NOTRUN -> [SKIP][34] ([fdo#109271] / [i915#4613])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl10/igt@gem_lmem_swapping@random-engines.html
* igt@gem_pxp@protected-raw-src-copy-not-readible:
- shard-tglb: NOTRUN -> [SKIP][35] ([i915#4270])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb6/igt@gem_pxp@protected-raw-src-copy-not-readible.html
* igt@gem_userptr_blits@dmabuf-sync:
- shard-skl: NOTRUN -> [SKIP][36] ([fdo#109271] / [i915#3323])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl4/igt@gem_userptr_blits@dmabuf-sync.html
* igt@gem_userptr_blits@input-checking:
- shard-kbl: NOTRUN -> [DMESG-WARN][37] ([i915#3002])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-kbl7/igt@gem_userptr_blits@input-checking.html
* igt@gen9_exec_parse@bb-start-cmd:
- shard-tglb: NOTRUN -> [SKIP][38] ([i915#2527] / [i915#2856])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb1/igt@gen9_exec_parse@bb-start-cmd.html
* igt@gen9_exec_parse@unaligned-access:
- shard-iclb: NOTRUN -> [SKIP][39] ([i915#2856])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-iclb5/igt@gen9_exec_parse@unaligned-access.html
* igt@i915_pm_dc@dc6-dpms:
- shard-skl: NOTRUN -> [FAIL][40] ([i915#454])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl10/igt@i915_pm_dc@dc6-dpms.html
* igt@i915_query@query-topology-known-pci-ids:
- shard-tglb: NOTRUN -> [SKIP][41] ([fdo#109303])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb2/igt@i915_query@query-topology-known-pci-ids.html
* igt@i915_selftest@live@gt_pm:
- shard-skl: NOTRUN -> [DMESG-FAIL][42] ([i915#1886] / [i915#2291])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl8/igt@i915_selftest@live@gt_pm.html
* igt@kms_big_fb@linear-8bpp-rotate-90:
- shard-tglb: NOTRUN -> [SKIP][43] ([fdo#111614])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb1/igt@kms_big_fb@linear-8bpp-rotate-90.html
* igt@kms_big_fb@linear-max-hw-stride-64bpp-rotate-180:
- shard-skl: NOTRUN -> [DMESG-WARN][44] ([i915#1982])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl10/igt@kms_big_fb@linear-max-hw-stride-64bpp-rotate-180.html
* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip:
- shard-tglb: [PASS][45] -> [FAIL][46] ([i915#3743])
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-tglb7/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb8/igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-async-flip.html
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-async-flip:
- shard-skl: NOTRUN -> [FAIL][47] ([i915#3743])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl9/igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-180-async-flip.html
* igt@kms_big_fb@yf-tiled-32bpp-rotate-0:
- shard-glk: [PASS][48] -> [DMESG-WARN][49] ([i915#118])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-glk6/igt@kms_big_fb@yf-tiled-32bpp-rotate-0.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-glk7/igt@kms_big_fb@yf-tiled-32bpp-rotate-0.html
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip:
- shard-kbl: NOTRUN -> [SKIP][50] ([fdo#109271] / [i915#3777])
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-kbl7/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-0-hflip.html
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-hflip:
- shard-skl: NOTRUN -> [SKIP][51] ([fdo#109271] / [i915#3777]) +1 similar issue
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl9/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-hflip.html
* igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][52] ([i915#3689]) +1 similar issue
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb6/igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_ccs.html
* igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_rc_ccs_cc:
- shard-apl: NOTRUN -> [SKIP][53] ([fdo#109271] / [i915#3886])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-apl4/igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
- shard-kbl: NOTRUN -> [SKIP][54] ([fdo#109271] / [i915#3886])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-kbl7/igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc:
- shard-glk: NOTRUN -> [SKIP][55] ([fdo#109271] / [i915#3886]) +2 similar issues
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-glk5/igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-b-crc-primary-rotation-180-yf_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][56] ([fdo#111615] / [i915#3689]) +1 similar issue
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb6/igt@kms_ccs@pipe-b-crc-primary-rotation-180-yf_tiled_ccs.html
* igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][57] ([fdo#109271] / [i915#3886]) +7 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl9/igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][58] ([i915#3689] / [i915#3886])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb1/igt@kms_ccs@pipe-c-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-d-crc-primary-rotation-180-yf_tiled_ccs:
- shard-apl: NOTRUN -> [SKIP][59] ([fdo#109271]) +24 similar issues
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-apl4/igt@kms_ccs@pipe-d-crc-primary-rotation-180-yf_tiled_ccs.html
* igt@kms_chamelium@dp-crc-multiple:
- shard-glk: NOTRUN -> [SKIP][60] ([fdo#109271] / [fdo#111827]) +3 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-glk5/igt@kms_chamelium@dp-crc-multiple.html
* igt@kms_chamelium@dp-hpd-for-each-pipe:
- shard-kbl: NOTRUN -> [SKIP][61] ([fdo#109271] / [fdo#111827]) +1 similar issue
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-kbl7/igt@kms_chamelium@dp-hpd-for-each-pipe.html
* igt@kms_color_chamelium@pipe-c-degamma:
- shard-tglb: NOTRUN -> [SKIP][62] ([fdo#109284] / [fdo#111827]) +4 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb1/igt@kms_color_chamelium@pipe-c-degamma.html
* igt@kms_color_chamelium@pipe-d-ctm-0-25:
- shard-apl: NOTRUN -> [SKIP][63] ([fdo#109271] / [fdo#111827])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-apl4/igt@kms_color_chamelium@pipe-d-ctm-0-25.html
* igt@kms_color_chamelium@pipe-d-degamma:
- shard-skl: NOTRUN -> [SKIP][64] ([fdo#109271] / [fdo#111827]) +13 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl8/igt@kms_color_chamelium@pipe-d-degamma.html
* igt@kms_content_protection@legacy:
- shard-glk: NOTRUN -> [SKIP][65] ([fdo#109271]) +38 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-glk5/igt@kms_content_protection@legacy.html
* igt@kms_cursor_crc@pipe-b-cursor-32x10-onscreen:
- shard-tglb: NOTRUN -> [SKIP][66] ([i915#3359])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb1/igt@kms_cursor_crc@pipe-b-cursor-32x10-onscreen.html
* igt@kms_cursor_crc@pipe-d-cursor-512x170-offscreen:
- shard-tglb: NOTRUN -> [SKIP][67] ([fdo#109279] / [i915#3359]) +1 similar issue
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb1/igt@kms_cursor_crc@pipe-d-cursor-512x170-offscreen.html
* igt@kms_cursor_legacy@cursora-vs-flipb-atomic:
- shard-iclb: NOTRUN -> [SKIP][68] ([fdo#109274] / [fdo#109278])
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-iclb5/igt@kms_cursor_legacy@cursora-vs-flipb-atomic.html
* igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions:
- shard-tglb: NOTRUN -> [SKIP][69] ([i915#4103])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb1/igt@kms_cursor_legacy@short-busy-flip-before-cursor-atomic-transitions.html
* igt@kms_flip@2x-flip-vs-absolute-wf_vblank-interruptible:
- shard-tglb: NOTRUN -> [SKIP][70] ([fdo#109274] / [fdo#111825]) +1 similar issue
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb1/igt@kms_flip@2x-flip-vs-absolute-wf_vblank-interruptible.html
* igt@kms_flip@flip-vs-expired-vblank@a-edp1:
- shard-skl: [PASS][71] -> [FAIL][72] ([i915#79])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-skl9/igt@kms_flip@flip-vs-expired-vblank@a-edp1.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl3/igt@kms_flip@flip-vs-expired-vblank@a-edp1.html
* igt@kms_flip@flip-vs-expired-vblank@a-hdmi-a1:
- shard-glk: [PASS][73] -> [FAIL][74] ([i915#79]) +1 similar issue
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-glk6/igt@kms_flip@flip-vs-expired-vblank@a-hdmi-a1.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-glk7/igt@kms_flip@flip-vs-expired-vblank@a-hdmi-a1.html
* igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1:
- shard-skl: [PASS][75] -> [FAIL][76] ([i915#2122]) +3 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-skl4/igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl5/igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling:
- shard-iclb: [PASS][77] -> [SKIP][78] ([i915#3701])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-iclb1/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytileccs-to-64bpp-ytile-downscaling.html
* igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-blt:
- shard-kbl: NOTRUN -> [SKIP][79] ([fdo#109271]) +28 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-kbl7/igt@kms_frontbuffer_tracking@fbc-2p-primscrn-spr-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-spr-indfb-draw-pwrite:
- shard-tglb: NOTRUN -> [SKIP][80] ([fdo#109280] / [fdo#111825]) +6 similar issues
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb6/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-spr-indfb-draw-pwrite.html
* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: NOTRUN -> [FAIL][81] ([i915#1188])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl9/igt@kms_hdr@bpc-switch-dpms.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-7efc:
- shard-skl: NOTRUN -> [FAIL][82] ([fdo#108145] / [i915#265]) +2 similar issues
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl8/igt@kms_plane_alpha_blend@pipe-a-alpha-7efc.html
- shard-apl: NOTRUN -> [FAIL][83] ([fdo#108145] / [i915#265])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-apl4/igt@kms_plane_alpha_blend@pipe-a-alpha-7efc.html
* igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb:
- shard-skl: NOTRUN -> [FAIL][84] ([i915#265])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl9/igt@kms_plane_alpha_blend@pipe-c-alpha-transparent-fb.html
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [PASS][85] -> [FAIL][86] ([fdo#108145] / [i915#265]) +1 similar issue
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-skl1/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl1/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html
* igt@kms_plane_lowres@pipe-b-tiling-x:
- shard-tglb: NOTRUN -> [SKIP][87] ([i915#3536])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb2/igt@kms_plane_lowres@pipe-b-tiling-x.html
* igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping:
- shard-glk: NOTRUN -> [SKIP][88] ([fdo#109271] / [i915#2733])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-glk5/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area:
- shard-skl: NOTRUN -> [SKIP][89] ([fdo#109271] / [i915#658])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl8/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area.html
- shard-apl: NOTRUN -> [SKIP][90] ([fdo#109271] / [i915#658])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-apl4/igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area.html
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area:
- shard-kbl: NOTRUN -> [SKIP][91] ([fdo#109271] / [i915#658])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-kbl7/igt@kms_psr2_sf@primary-plane-update-sf-dmg-area.html
* igt@kms_psr2_su@frontbuffer-xrgb8888:
- shard-tglb: NOTRUN -> [SKIP][92] ([i915#1911])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb1/igt@kms_psr2_su@frontbuffer-xrgb8888.html
* igt@kms_psr@psr2_cursor_mmap_gtt:
- shard-iclb: NOTRUN -> [SKIP][93] ([fdo#109441])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-iclb5/igt@kms_psr@psr2_cursor_mmap_gtt.html
* igt@kms_psr@psr2_no_drrs:
- shard-tglb: NOTRUN -> [FAIL][94] ([i915#132] / [i915#3467])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb6/igt@kms_psr@psr2_no_drrs.html
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [PASS][95] -> [SKIP][96] ([fdo#109441]) +1 similar issue
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-iclb6/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_sysfs_edid_timing:
- shard-skl: NOTRUN -> [FAIL][97] ([IGT#2])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl10/igt@kms_sysfs_edid_timing.html
* igt@kms_vblank@pipe-d-query-forked-hang:
- shard-snb: NOTRUN -> [SKIP][98] ([fdo#109271]) +12 similar issues
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-snb5/igt@kms_vblank@pipe-d-query-forked-hang.html
* igt@kms_vrr@flipline:
- shard-tglb: NOTRUN -> [SKIP][99] ([fdo#109502])
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb6/igt@kms_vrr@flipline.html
* igt@kms_writeback@writeback-invalid-parameters:
- shard-skl: NOTRUN -> [SKIP][100] ([fdo#109271] / [i915#2437]) +1 similar issue
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl9/igt@kms_writeback@writeback-invalid-parameters.html
* igt@perf@per-context-mode-unprivileged:
- shard-tglb: NOTRUN -> [SKIP][101] ([fdo#109289])
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb1/igt@perf@per-context-mode-unprivileged.html
* igt@perf@polling-parameterized:
- shard-skl: [PASS][102] -> [FAIL][103] ([i915#1542])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-skl9/igt@perf@polling-parameterized.html
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl10/igt@perf@polling-parameterized.html
* igt@perf@short-reads:
- shard-skl: NOTRUN -> [FAIL][104] ([i915#51])
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl4/igt@perf@short-reads.html
* igt@prime_nv_pcopy@test3_2:
- shard-tglb: NOTRUN -> [SKIP][105] ([fdo#109291]) +2 similar issues
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb2/igt@prime_nv_pcopy@test3_2.html
* igt@sysfs_clients@fair-7:
- shard-glk: NOTRUN -> [SKIP][106] ([fdo#109271] / [i915#2994])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-glk5/igt@sysfs_clients@fair-7.html
* igt@sysfs_clients@pidname:
- shard-tglb: NOTRUN -> [SKIP][107] ([i915#2994])
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb6/igt@sysfs_clients@pidname.html
* igt@sysfs_clients@recycle-many:
- shard-apl: NOTRUN -> [SKIP][108] ([fdo#109271] / [i915#2994])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-apl4/igt@sysfs_clients@recycle-many.html
- shard-skl: NOTRUN -> [SKIP][109] ([fdo#109271] / [i915#2994])
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl8/igt@sysfs_clients@recycle-many.html
#### Possible fixes ####
* igt@drm_read@invalid-buffer:
- {shard-rkl}: [SKIP][110] ([i915#1845] / [i915#4098]) -> [PASS][111]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-rkl-1/igt@drm_read@invalid-buffer.html
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-rkl-6/igt@drm_read@invalid-buffer.html
* igt@feature_discovery@psr2:
- shard-iclb: [SKIP][112] ([i915#658]) -> [PASS][113]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-iclb4/igt@feature_discovery@psr2.html
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-iclb2/igt@feature_discovery@psr2.html
* igt@gem_ctx_persistence@engines-hang@bcs0:
- {shard-dg1}: [DMESG-WARN][114] ([i915#4892]) -> [PASS][115] +16 similar issues
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-dg1-18/igt@gem_ctx_persistence@engines-hang@bcs0.html
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-dg1-12/igt@gem_ctx_persistence@engines-hang@bcs0.html
* igt@gem_eio@in-flight-contexts-immediate:
- shard-tglb: [TIMEOUT][116] ([i915#3063]) -> [PASS][117]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-tglb2/igt@gem_eio@in-flight-contexts-immediate.html
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb7/igt@gem_eio@in-flight-contexts-immediate.html
* igt@gem_eio@in-flight-suspend:
- shard-apl: [DMESG-WARN][118] ([i915#180]) -> [PASS][119]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-apl1/igt@gem_eio@in-flight-suspend.html
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-apl4/igt@gem_eio@in-flight-suspend.html
* igt@gem_eio@unwedge-stress:
- shard-tglb: [FAIL][120] ([i915#232]) -> [PASS][121]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-tglb3/igt@gem_eio@unwedge-stress.html
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb6/igt@gem_eio@unwedge-stress.html
- {shard-tglu}: [TIMEOUT][122] ([i915#3063] / [i915#3648]) -> [PASS][123]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-tglu-8/igt@gem_eio@unwedge-stress.html
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglu-3/igt@gem_eio@unwedge-stress.html
* igt@gem_exec_balancer@parallel:
- shard-iclb: [SKIP][124] ([i915#4525]) -> [PASS][125] +1 similar issue
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-iclb5/igt@gem_exec_balancer@parallel.html
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-iclb1/igt@gem_exec_balancer@parallel.html
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-apl: [FAIL][126] ([i915#2842]) -> [PASS][127]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-apl6/igt@gem_exec_fair@basic-pace-solo@rcs0.html
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-apl1/igt@gem_exec_fair@basic-pace-solo@rcs0.html
* igt@gem_exec_fair@basic-pace@vcs0:
- shard-kbl: [FAIL][128] ([i915#2842]) -> [PASS][129]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-kbl3/igt@gem_exec_fair@basic-pace@vcs0.html
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-kbl7/igt@gem_exec_fair@basic-pace@vcs0.html
* igt@gem_exec_fence@expired-history:
- {shard-rkl}: [DMESG-WARN][130] -> [PASS][131]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-rkl-5/igt@gem_exec_fence@expired-history.html
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-rkl-4/igt@gem_exec_fence@expired-history.html
* igt@gem_exec_flush@basic-batch-kernel-default-wb:
- {shard-rkl}: [INCOMPLETE][132] -> [PASS][133]
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-rkl-5/igt@gem_exec_flush@basic-batch-kernel-default-wb.html
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-rkl-2/igt@gem_exec_flush@basic-batch-kernel-default-wb.html
* igt@gem_huc_copy@huc-copy:
- shard-tglb: [SKIP][134] ([i915#2190]) -> [PASS][135]
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-tglb7/igt@gem_huc_copy@huc-copy.html
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-tglb8/igt@gem_huc_copy@huc-copy.html
* igt@gen9_exec_parse@allowed-all:
- shard-skl: [DMESG-WARN][136] ([i915#1436] / [i915#716]) -> [PASS][137]
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-skl9/igt@gen9_exec_parse@allowed-all.html
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-skl9/igt@gen9_exec_parse@allowed-all.html
* igt@i915_pm_dc@dc6-dpms:
- shard-iclb: [FAIL][138] ([i915#454]) -> [PASS][139] +1 similar issue
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-iclb3/igt@i915_pm_dc@dc6-dpms.html
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-iclb6/igt@i915_pm_dc@dc6-dpms.html
* igt@i915_pm_rpm@drm-resources-equal:
- {shard-rkl}: [SKIP][140] ([fdo#109308]) -> [PASS][141]
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11053/shard-rkl-1/igt@i915_pm_rpm@drm-resources-equal.html
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/shard-rkl-
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_21937/index.html
[-- Attachment #2: Type: text/html, Size: 33611 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] drm/i915/guc: Don't error on reset of banned context
2022-01-07 0:31 ` [Intel-gfx] " John.C.Harrison
@ 2022-01-11 18:45 ` Matthew Brost
-1 siblings, 0 replies; 8+ messages in thread
From: Matthew Brost @ 2022-01-11 18:45 UTC (permalink / raw)
To: John.C.Harrison; +Cc: Intel-GFX, DRI-Devel
On Thu, Jan 06, 2022 at 04:31:43PM -0800, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> There is a race (already documented in the code) whereby a context can
> be (re-)queued for submission at the same time as it is being banned
> due to a hang and reset. That leads to a hang/reset report from GuC
> for a context which i915 thinks is already banned.
>
I think there are 2 issues here.
1. Banning of context (e.g. user closes a non-persistent context)
results in an context reset. In this case we will receive a G2H
indicating a context reset and we want to convert the context reset to a
nop.
2. A GT reset races with a context reset result in the context getting
banned before the G2H is processed. Again we want to convert the context
reset to a nop. This race should be sealed when we can flush the G2H
handler in the reset path. Flushing G2H handler depends on the error
capture not allocating memory in non-sleeping contexts. Thomas H had a
patch for this.
In both cases we shouldn't print an error.
> While the race is indented to be fixed in a future GuC update, there
> is no actual harm beyond the wasted execution time of that new hang
> detection period. The context has already been banned for bad
> behaviour so a fresh hang is hardly surprising and certainly isn't
> going to be losing any work that wouldn't already have been lost if
> there was no race.
>
See above, I think you are confusing the issues here. This won't be
fixed by an updated GuC firmware.
> So don't treat this situation as an error. The error message is seen
> by the CI system as something fatal and causes test failures. Instead,
> just print an informational so the user at least knows a context reset
> occurred (given that the error capture is being skipped).
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> ---
> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> index 9989d121127d..e8a32a7e7daf 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> @@ -3978,6 +3978,10 @@ static void guc_handle_context_reset(struct intel_guc *guc,
> !context_blocked(ce))) {
> capture_error_state(guc, ce);
> guc_context_replay(ce);
> + } else if (intel_context_is_banned(ce)) {
> + drm_info(&guc_to_gt(guc)->i915->drm,
> + "Reset notificaion for banned context 0x%04X on %s",
> + ce->guc_id.id, ce->engine->name);
The context being blocking isn't an error either. I think real fix is
changing the below drm_err to drm_info and call it a day.
Matt
> } else {
> drm_err(&guc_to_gt(guc)->i915->drm,
> "Invalid GuC engine reset notificaion for 0x%04X on %s: banned = %d, blocked = %d",
> --
> 2.25.1
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/guc: Don't error on reset of banned context
@ 2022-01-11 18:45 ` Matthew Brost
0 siblings, 0 replies; 8+ messages in thread
From: Matthew Brost @ 2022-01-11 18:45 UTC (permalink / raw)
To: John.C.Harrison; +Cc: Intel-GFX, DRI-Devel
On Thu, Jan 06, 2022 at 04:31:43PM -0800, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> There is a race (already documented in the code) whereby a context can
> be (re-)queued for submission at the same time as it is being banned
> due to a hang and reset. That leads to a hang/reset report from GuC
> for a context which i915 thinks is already banned.
>
I think there are 2 issues here.
1. Banning of context (e.g. user closes a non-persistent context)
results in an context reset. In this case we will receive a G2H
indicating a context reset and we want to convert the context reset to a
nop.
2. A GT reset races with a context reset result in the context getting
banned before the G2H is processed. Again we want to convert the context
reset to a nop. This race should be sealed when we can flush the G2H
handler in the reset path. Flushing G2H handler depends on the error
capture not allocating memory in non-sleeping contexts. Thomas H had a
patch for this.
In both cases we shouldn't print an error.
> While the race is indented to be fixed in a future GuC update, there
> is no actual harm beyond the wasted execution time of that new hang
> detection period. The context has already been banned for bad
> behaviour so a fresh hang is hardly surprising and certainly isn't
> going to be losing any work that wouldn't already have been lost if
> there was no race.
>
See above, I think you are confusing the issues here. This won't be
fixed by an updated GuC firmware.
> So don't treat this situation as an error. The error message is seen
> by the CI system as something fatal and causes test failures. Instead,
> just print an informational so the user at least knows a context reset
> occurred (given that the error capture is being skipped).
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> ---
> drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> index 9989d121127d..e8a32a7e7daf 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_guc_submission.c
> @@ -3978,6 +3978,10 @@ static void guc_handle_context_reset(struct intel_guc *guc,
> !context_blocked(ce))) {
> capture_error_state(guc, ce);
> guc_context_replay(ce);
> + } else if (intel_context_is_banned(ce)) {
> + drm_info(&guc_to_gt(guc)->i915->drm,
> + "Reset notificaion for banned context 0x%04X on %s",
> + ce->guc_id.id, ce->engine->name);
The context being blocking isn't an error either. I think real fix is
changing the below drm_err to drm_info and call it a day.
Matt
> } else {
> drm_err(&guc_to_gt(guc)->i915->drm,
> "Invalid GuC engine reset notificaion for 0x%04X on %s: banned = %d, blocked = %d",
> --
> 2.25.1
>
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2022-01-11 18:51 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-07 0:31 [PATCH] drm/i915/guc: Don't error on reset of banned context John.C.Harrison
2022-01-07 0:31 ` [Intel-gfx] " John.C.Harrison
2022-01-07 0:35 ` John Harrison
2022-01-07 0:35 ` [Intel-gfx] " John Harrison
2022-01-07 1:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-01-07 17:06 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-01-11 18:45 ` [PATCH] " Matthew Brost
2022-01-11 18:45 ` [Intel-gfx] " Matthew Brost
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.