* [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets
@ 2019-10-23 23:24 Chris Wilson
2019-10-23 23:24 ` [Intel-gfx] " Chris Wilson
` (4 more replies)
0 siblings, 5 replies; 16+ messages in thread
From: Chris Wilson @ 2019-10-23 23:24 UTC (permalink / raw)
To: intel-gfx
When setting up the system to perform the atomic reset, we need to
serialise with any ongoing interrupt tasklet or else:
<0> [472.951428] i915_sel-4442 0d..1 466527056us : __i915_request_submit: rcs0 fence 11659:2, current 0
<0> [472.951554] i915_sel-4442 0d..1 466527059us : __execlists_submission_tasklet: rcs0: queue_priority_hint:-2147483648, submit:yes
<0> [472.951681] i915_sel-4442 0d..1 466527061us : trace_ports: rcs0: submit { 11659:2, 0:0 }
<0> [472.951805] i915_sel-4442 0.... 466527114us : __igt_atomic_reset_engine: i915_reset_engine(rcs0:active) under hardirq
<0> [472.951932] i915_sel-4442 0d... 466527115us : intel_engine_reset: rcs0 flags=11d
<0> [472.952056] i915_sel-4442 0d... 466527117us : execlists_reset_prepare: rcs0: depth<-1
<0> [472.952179] i915_sel-4442 0d... 466527119us : intel_engine_stop_cs: rcs0
<0> [472.952305] <idle>-0 1..s1 466527119us : process_csb: rcs0 cs-irq head=3, tail=4
<0> [472.952431] i915_sel-4442 0d... 466527122us : __intel_gt_reset: engine_mask=1
<0> [472.952557] <idle>-0 1..s1 466527124us : process_csb: rcs0 csb[4]: status=0x00000001:0x00000000
<0> [472.952683] <idle>-0 1..s1 466527130us : trace_ports: rcs0: promote { 11659:2*, 0:0 }
<0> [472.952808] i915_sel-4442 0d... 466527131us : execlists_reset: rcs0
<0> [472.952933] i915_sel-4442 0d..1 466527133us : process_csb: rcs0 cs-irq head=3, tail=4
<0> [472.953059] i915_sel-4442 0d..1 466527134us : process_csb: rcs0 csb[4]: status=0x00000001:0x00000000
<0> [472.953185] i915_sel-4442 0d..1 466527136us : trace_ports: rcs0: preempted { 11659:2*, 0:0 }
<0> [472.953310] i915_sel-4442 0d..1 466527150us : assert_pending_valid: Nothing pending for promotion!
<0> [472.953436] i915_sel-4442 0d..1 466527158us : process_csb: process_csb:1930 GEM_BUG_ON(!assert_pending_valid(execlists, "promote"))
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=112069
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
---
drivers/gpu/drm/i915/gt/selftest_hangcheck.c | 2 +-
drivers/gpu/drm/i915/gt/selftest_reset.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/selftest_hangcheck.c b/drivers/gpu/drm/i915/gt/selftest_hangcheck.c
index b892b47348ab..ba761fcf397b 100644
--- a/drivers/gpu/drm/i915/gt/selftest_hangcheck.c
+++ b/drivers/gpu/drm/i915/gt/selftest_hangcheck.c
@@ -1563,7 +1563,7 @@ static int __igt_atomic_reset_engine(struct intel_engine_cs *engine,
GEM_TRACE("i915_reset_engine(%s:%s) under %s\n",
engine->name, mode, p->name);
- tasklet_disable_nosync(t);
+ tasklet_disable(t);
p->critical_section_begin();
err = intel_engine_reset(engine, NULL);
diff --git a/drivers/gpu/drm/i915/gt/selftest_reset.c b/drivers/gpu/drm/i915/gt/selftest_reset.c
index 6efb9221b7fa..6ad6aca315f6 100644
--- a/drivers/gpu/drm/i915/gt/selftest_reset.c
+++ b/drivers/gpu/drm/i915/gt/selftest_reset.c
@@ -126,7 +126,7 @@ static int igt_atomic_engine_reset(void *arg)
goto out_unlock;
for_each_engine(engine, gt, id) {
- tasklet_disable_nosync(&engine->execlists.tasklet);
+ tasklet_disable(&engine->execlists.tasklet);
intel_engine_pm_get(engine);
for (p = igt_atomic_phases; p->name; p++) {
--
2.24.0.rc0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 16+ messages in thread* [Intel-gfx] [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-23 23:24 [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets Chris Wilson @ 2019-10-23 23:24 ` Chris Wilson 2019-10-24 2:27 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork ` (3 subsequent siblings) 4 siblings, 0 replies; 16+ messages in thread From: Chris Wilson @ 2019-10-23 23:24 UTC (permalink / raw) To: intel-gfx When setting up the system to perform the atomic reset, we need to serialise with any ongoing interrupt tasklet or else: <0> [472.951428] i915_sel-4442 0d..1 466527056us : __i915_request_submit: rcs0 fence 11659:2, current 0 <0> [472.951554] i915_sel-4442 0d..1 466527059us : __execlists_submission_tasklet: rcs0: queue_priority_hint:-2147483648, submit:yes <0> [472.951681] i915_sel-4442 0d..1 466527061us : trace_ports: rcs0: submit { 11659:2, 0:0 } <0> [472.951805] i915_sel-4442 0.... 466527114us : __igt_atomic_reset_engine: i915_reset_engine(rcs0:active) under hardirq <0> [472.951932] i915_sel-4442 0d... 466527115us : intel_engine_reset: rcs0 flags=11d <0> [472.952056] i915_sel-4442 0d... 466527117us : execlists_reset_prepare: rcs0: depth<-1 <0> [472.952179] i915_sel-4442 0d... 466527119us : intel_engine_stop_cs: rcs0 <0> [472.952305] <idle>-0 1..s1 466527119us : process_csb: rcs0 cs-irq head=3, tail=4 <0> [472.952431] i915_sel-4442 0d... 466527122us : __intel_gt_reset: engine_mask=1 <0> [472.952557] <idle>-0 1..s1 466527124us : process_csb: rcs0 csb[4]: status=0x00000001:0x00000000 <0> [472.952683] <idle>-0 1..s1 466527130us : trace_ports: rcs0: promote { 11659:2*, 0:0 } <0> [472.952808] i915_sel-4442 0d... 466527131us : execlists_reset: rcs0 <0> [472.952933] i915_sel-4442 0d..1 466527133us : process_csb: rcs0 cs-irq head=3, tail=4 <0> [472.953059] i915_sel-4442 0d..1 466527134us : process_csb: rcs0 csb[4]: status=0x00000001:0x00000000 <0> [472.953185] i915_sel-4442 0d..1 466527136us : trace_ports: rcs0: preempted { 11659:2*, 0:0 } <0> [472.953310] i915_sel-4442 0d..1 466527150us : assert_pending_valid: Nothing pending for promotion! <0> [472.953436] i915_sel-4442 0d..1 466527158us : process_csb: process_csb:1930 GEM_BUG_ON(!assert_pending_valid(execlists, "promote")) Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=112069 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> --- drivers/gpu/drm/i915/gt/selftest_hangcheck.c | 2 +- drivers/gpu/drm/i915/gt/selftest_reset.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/gt/selftest_hangcheck.c b/drivers/gpu/drm/i915/gt/selftest_hangcheck.c index b892b47348ab..ba761fcf397b 100644 --- a/drivers/gpu/drm/i915/gt/selftest_hangcheck.c +++ b/drivers/gpu/drm/i915/gt/selftest_hangcheck.c @@ -1563,7 +1563,7 @@ static int __igt_atomic_reset_engine(struct intel_engine_cs *engine, GEM_TRACE("i915_reset_engine(%s:%s) under %s\n", engine->name, mode, p->name); - tasklet_disable_nosync(t); + tasklet_disable(t); p->critical_section_begin(); err = intel_engine_reset(engine, NULL); diff --git a/drivers/gpu/drm/i915/gt/selftest_reset.c b/drivers/gpu/drm/i915/gt/selftest_reset.c index 6efb9221b7fa..6ad6aca315f6 100644 --- a/drivers/gpu/drm/i915/gt/selftest_reset.c +++ b/drivers/gpu/drm/i915/gt/selftest_reset.c @@ -126,7 +126,7 @@ static int igt_atomic_engine_reset(void *arg) goto out_unlock; for_each_engine(engine, gt, id) { - tasklet_disable_nosync(&engine->execlists.tasklet); + tasklet_disable(&engine->execlists.tasklet); intel_engine_pm_get(engine); for (p = igt_atomic_phases; p->name; p++) { -- 2.24.0.rc0 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 16+ messages in thread
* ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-23 23:24 [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets Chris Wilson 2019-10-23 23:24 ` [Intel-gfx] " Chris Wilson @ 2019-10-24 2:27 ` Patchwork 2019-10-24 2:27 ` [Intel-gfx] " Patchwork 2019-10-24 2:55 ` ✓ Fi.CI.BAT: success " Patchwork ` (2 subsequent siblings) 4 siblings, 1 reply; 16+ messages in thread From: Patchwork @ 2019-10-24 2:27 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: drm/i915/selftests: Flush interrupts before disabling tasklets URL : https://patchwork.freedesktop.org/series/68486/ State : warning == Summary == $ dim checkpatch origin/drm-tip d179199a3774 drm/i915/selftests: Flush interrupts before disabling tasklets -:10: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line) #10: <0> [472.951428] i915_sel-4442 0d..1 466527056us : __i915_request_submit: rcs0 fence 11659:2, current 0 total: 0 errors, 1 warnings, 0 checks, 16 lines checked _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-24 2:27 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork @ 2019-10-24 2:27 ` Patchwork 0 siblings, 0 replies; 16+ messages in thread From: Patchwork @ 2019-10-24 2:27 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: drm/i915/selftests: Flush interrupts before disabling tasklets URL : https://patchwork.freedesktop.org/series/68486/ State : warning == Summary == $ dim checkpatch origin/drm-tip d179199a3774 drm/i915/selftests: Flush interrupts before disabling tasklets -:10: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line) #10: <0> [472.951428] i915_sel-4442 0d..1 466527056us : __i915_request_submit: rcs0 fence 11659:2, current 0 total: 0 errors, 1 warnings, 0 checks, 16 lines checked _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
* ✓ Fi.CI.BAT: success for drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-23 23:24 [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets Chris Wilson 2019-10-23 23:24 ` [Intel-gfx] " Chris Wilson 2019-10-24 2:27 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork @ 2019-10-24 2:55 ` Patchwork 2019-10-24 2:55 ` [Intel-gfx] " Patchwork 2019-10-24 7:21 ` [PATCH] " Mika Kuoppala 2019-10-25 1:42 ` ✗ Fi.CI.IGT: failure for " Patchwork 4 siblings, 1 reply; 16+ messages in thread From: Patchwork @ 2019-10-24 2:55 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: drm/i915/selftests: Flush interrupts before disabling tasklets URL : https://patchwork.freedesktop.org/series/68486/ State : success == Summary == CI Bug Log - changes from CI_DRM_7167 -> Patchwork_14957 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/index.html Known issues ------------ Here are the changes found in Patchwork_14957 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_mmap_gtt@basic: - fi-icl-u3: [PASS][1] -> [DMESG-WARN][2] ([fdo#107724]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-icl-u3/igt@gem_mmap_gtt@basic.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-icl-u3/igt@gem_mmap_gtt@basic.html * igt@i915_selftest@live_gem_contexts: - fi-cfl-8109u: [PASS][3] -> [DMESG-FAIL][4] ([fdo#112050 ]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-cfl-8109u/igt@i915_selftest@live_gem_contexts.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-cfl-8109u/igt@i915_selftest@live_gem_contexts.html #### Possible fixes #### * igt@gem_sync@basic-store-all: - {fi-tgl-u}: [INCOMPLETE][5] ([fdo#111880]) -> [PASS][6] [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-tgl-u/igt@gem_sync@basic-store-all.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-tgl-u/igt@gem_sync@basic-store-all.html * igt@i915_pm_rpm@basic-pci-d3-state: - fi-skl-6600u: [FAIL][7] ([fdo#107707]) -> [PASS][8] [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-skl-6600u/igt@i915_pm_rpm@basic-pci-d3-state.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-skl-6600u/igt@i915_pm_rpm@basic-pci-d3-state.html * {igt@i915_selftest@live_gt_heartbeat}: - fi-kbl-8809g: [DMESG-FAIL][9] ([fdo#112096]) -> [PASS][10] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-kbl-8809g/igt@i915_selftest@live_gt_heartbeat.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-kbl-8809g/igt@i915_selftest@live_gt_heartbeat.html * igt@kms_busy@basic-flip-a: - {fi-tgl-u2}: [DMESG-WARN][11] ([fdo#111600]) -> [PASS][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-tgl-u2/igt@kms_busy@basic-flip-a.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-tgl-u2/igt@kms_busy@basic-flip-a.html * igt@prime_vgem@basic-fence-wait-default: - fi-icl-u3: [DMESG-WARN][13] ([fdo#107724]) -> [PASS][14] [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-icl-u3/igt@prime_vgem@basic-fence-wait-default.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-icl-u3/igt@prime_vgem@basic-fence-wait-default.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#107707]: https://bugs.freedesktop.org/show_bug.cgi?id=107707 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724 [fdo#108840]: https://bugs.freedesktop.org/show_bug.cgi?id=108840 [fdo#111600]: https://bugs.freedesktop.org/show_bug.cgi?id=111600 [fdo#111747]: https://bugs.freedesktop.org/show_bug.cgi?id=111747 [fdo#111880]: https://bugs.freedesktop.org/show_bug.cgi?id=111880 [fdo#112050 ]: https://bugs.freedesktop.org/show_bug.cgi?id=112050 [fdo#112096]: https://bugs.freedesktop.org/show_bug.cgi?id=112096 Participating hosts (52 -> 45) ------------------------------ Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus Build changes ------------- * CI: CI-20190529 -> None * Linux: CI_DRM_7167 -> Patchwork_14957 CI-20190529: 20190529 CI_DRM_7167: a62b1c4e7739c6777d51e7b2d66406b935131451 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5236: 8153b95b53bdef26d2c3e318197d174e982b4265 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_14957: d179199a3774c6f792d2455df296e2d01e686422 @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == d179199a3774 drm/i915/selftests: Flush interrupts before disabling tasklets == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-24 2:55 ` ✓ Fi.CI.BAT: success " Patchwork @ 2019-10-24 2:55 ` Patchwork 0 siblings, 0 replies; 16+ messages in thread From: Patchwork @ 2019-10-24 2:55 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: drm/i915/selftests: Flush interrupts before disabling tasklets URL : https://patchwork.freedesktop.org/series/68486/ State : success == Summary == CI Bug Log - changes from CI_DRM_7167 -> Patchwork_14957 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/index.html Known issues ------------ Here are the changes found in Patchwork_14957 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_mmap_gtt@basic: - fi-icl-u3: [PASS][1] -> [DMESG-WARN][2] ([fdo#107724]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-icl-u3/igt@gem_mmap_gtt@basic.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-icl-u3/igt@gem_mmap_gtt@basic.html * igt@i915_selftest@live_gem_contexts: - fi-cfl-8109u: [PASS][3] -> [DMESG-FAIL][4] ([fdo#112050 ]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-cfl-8109u/igt@i915_selftest@live_gem_contexts.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-cfl-8109u/igt@i915_selftest@live_gem_contexts.html #### Possible fixes #### * igt@gem_sync@basic-store-all: - {fi-tgl-u}: [INCOMPLETE][5] ([fdo#111880]) -> [PASS][6] [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-tgl-u/igt@gem_sync@basic-store-all.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-tgl-u/igt@gem_sync@basic-store-all.html * igt@i915_pm_rpm@basic-pci-d3-state: - fi-skl-6600u: [FAIL][7] ([fdo#107707]) -> [PASS][8] [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-skl-6600u/igt@i915_pm_rpm@basic-pci-d3-state.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-skl-6600u/igt@i915_pm_rpm@basic-pci-d3-state.html * {igt@i915_selftest@live_gt_heartbeat}: - fi-kbl-8809g: [DMESG-FAIL][9] ([fdo#112096]) -> [PASS][10] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-kbl-8809g/igt@i915_selftest@live_gt_heartbeat.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-kbl-8809g/igt@i915_selftest@live_gt_heartbeat.html * igt@kms_busy@basic-flip-a: - {fi-tgl-u2}: [DMESG-WARN][11] ([fdo#111600]) -> [PASS][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-tgl-u2/igt@kms_busy@basic-flip-a.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-tgl-u2/igt@kms_busy@basic-flip-a.html * igt@prime_vgem@basic-fence-wait-default: - fi-icl-u3: [DMESG-WARN][13] ([fdo#107724]) -> [PASS][14] [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/fi-icl-u3/igt@prime_vgem@basic-fence-wait-default.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/fi-icl-u3/igt@prime_vgem@basic-fence-wait-default.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#107707]: https://bugs.freedesktop.org/show_bug.cgi?id=107707 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724 [fdo#108840]: https://bugs.freedesktop.org/show_bug.cgi?id=108840 [fdo#111600]: https://bugs.freedesktop.org/show_bug.cgi?id=111600 [fdo#111747]: https://bugs.freedesktop.org/show_bug.cgi?id=111747 [fdo#111880]: https://bugs.freedesktop.org/show_bug.cgi?id=111880 [fdo#112050 ]: https://bugs.freedesktop.org/show_bug.cgi?id=112050 [fdo#112096]: https://bugs.freedesktop.org/show_bug.cgi?id=112096 Participating hosts (52 -> 45) ------------------------------ Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus Build changes ------------- * CI: CI-20190529 -> None * Linux: CI_DRM_7167 -> Patchwork_14957 CI-20190529: 20190529 CI_DRM_7167: a62b1c4e7739c6777d51e7b2d66406b935131451 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5236: 8153b95b53bdef26d2c3e318197d174e982b4265 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_14957: d179199a3774c6f792d2455df296e2d01e686422 @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == d179199a3774 drm/i915/selftests: Flush interrupts before disabling tasklets == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-23 23:24 [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets Chris Wilson ` (2 preceding siblings ...) 2019-10-24 2:55 ` ✓ Fi.CI.BAT: success " Patchwork @ 2019-10-24 7:21 ` Mika Kuoppala 2019-10-24 7:21 ` [Intel-gfx] " Mika Kuoppala 2019-10-24 7:28 ` Chris Wilson 2019-10-25 1:42 ` ✗ Fi.CI.IGT: failure for " Patchwork 4 siblings, 2 replies; 16+ messages in thread From: Mika Kuoppala @ 2019-10-24 7:21 UTC (permalink / raw) To: Chris Wilson, intel-gfx Chris Wilson <chris@chris-wilson.co.uk> writes: > When setting up the system to perform the atomic reset, we need to > serialise with any ongoing interrupt tasklet or else: > > <0> [472.951428] i915_sel-4442 0d..1 466527056us : __i915_request_submit: rcs0 fence 11659:2, current 0 > <0> [472.951554] i915_sel-4442 0d..1 466527059us : __execlists_submission_tasklet: rcs0: queue_priority_hint:-2147483648, submit:yes > <0> [472.951681] i915_sel-4442 0d..1 466527061us : trace_ports: rcs0: submit { 11659:2, 0:0 } > <0> [472.951805] i915_sel-4442 0.... 466527114us : __igt_atomic_reset_engine: i915_reset_engine(rcs0:active) under hardirq > <0> [472.951932] i915_sel-4442 0d... 466527115us : intel_engine_reset: rcs0 flags=11d > <0> [472.952056] i915_sel-4442 0d... 466527117us : execlists_reset_prepare: rcs0: depth<-1 > <0> [472.952179] i915_sel-4442 0d... 466527119us : intel_engine_stop_cs: rcs0 > <0> [472.952305] <idle>-0 1..s1 466527119us : process_csb: rcs0 cs-irq head=3, tail=4 Racing and this shows from old world? -Mika > <0> [472.952431] i915_sel-4442 0d... 466527122us : __intel_gt_reset: engine_mask=1 > <0> [472.952557] <idle>-0 1..s1 466527124us : process_csb: rcs0 csb[4]: status=0x00000001:0x00000000 > <0> [472.952683] <idle>-0 1..s1 466527130us : trace_ports: rcs0: promote { 11659:2*, 0:0 } > <0> [472.952808] i915_sel-4442 0d... 466527131us : execlists_reset: rcs0 > <0> [472.952933] i915_sel-4442 0d..1 466527133us : process_csb: rcs0 cs-irq head=3, tail=4 > <0> [472.953059] i915_sel-4442 0d..1 466527134us : process_csb: rcs0 csb[4]: status=0x00000001:0x00000000 > <0> [472.953185] i915_sel-4442 0d..1 466527136us : trace_ports: rcs0: preempted { 11659:2*, 0:0 } > <0> [472.953310] i915_sel-4442 0d..1 466527150us : assert_pending_valid: Nothing pending for promotion! > <0> [472.953436] i915_sel-4442 0d..1 466527158us : process_csb: process_csb:1930 GEM_BUG_ON(!assert_pending_valid(execlists, "promote")) > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=112069 > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> > --- G> drivers/gpu/drm/i915/gt/selftest_hangcheck.c | 2 +- > drivers/gpu/drm/i915/gt/selftest_reset.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/gpu/drm/i915/gt/selftest_hangcheck.c b/drivers/gpu/drm/i915/gt/selftest_hangcheck.c > index b892b47348ab..ba761fcf397b 100644 > --- a/drivers/gpu/drm/i915/gt/selftest_hangcheck.c > +++ b/drivers/gpu/drm/i915/gt/selftest_hangcheck.c > @@ -1563,7 +1563,7 @@ static int __igt_atomic_reset_engine(struct intel_engine_cs *engine, > GEM_TRACE("i915_reset_engine(%s:%s) under %s\n", > engine->name, mode, p->name); > > - tasklet_disable_nosync(t); > + tasklet_disable(t); > p->critical_section_begin(); > > err = intel_engine_reset(engine, NULL); > diff --git a/drivers/gpu/drm/i915/gt/selftest_reset.c b/drivers/gpu/drm/i915/gt/selftest_reset.c > index 6efb9221b7fa..6ad6aca315f6 100644 > --- a/drivers/gpu/drm/i915/gt/selftest_reset.c > +++ b/drivers/gpu/drm/i915/gt/selftest_reset.c > @@ -126,7 +126,7 @@ static int igt_atomic_engine_reset(void *arg) > goto out_unlock; > > for_each_engine(engine, gt, id) { > - tasklet_disable_nosync(&engine->execlists.tasklet); > + tasklet_disable(&engine->execlists.tasklet); > intel_engine_pm_get(engine); > > for (p = igt_atomic_phases; p->name; p++) { > -- > 2.24.0.rc0 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-24 7:21 ` [PATCH] " Mika Kuoppala @ 2019-10-24 7:21 ` Mika Kuoppala 2019-10-24 7:28 ` Chris Wilson 1 sibling, 0 replies; 16+ messages in thread From: Mika Kuoppala @ 2019-10-24 7:21 UTC (permalink / raw) To: Chris Wilson, intel-gfx Chris Wilson <chris@chris-wilson.co.uk> writes: > When setting up the system to perform the atomic reset, we need to > serialise with any ongoing interrupt tasklet or else: > > <0> [472.951428] i915_sel-4442 0d..1 466527056us : __i915_request_submit: rcs0 fence 11659:2, current 0 > <0> [472.951554] i915_sel-4442 0d..1 466527059us : __execlists_submission_tasklet: rcs0: queue_priority_hint:-2147483648, submit:yes > <0> [472.951681] i915_sel-4442 0d..1 466527061us : trace_ports: rcs0: submit { 11659:2, 0:0 } > <0> [472.951805] i915_sel-4442 0.... 466527114us : __igt_atomic_reset_engine: i915_reset_engine(rcs0:active) under hardirq > <0> [472.951932] i915_sel-4442 0d... 466527115us : intel_engine_reset: rcs0 flags=11d > <0> [472.952056] i915_sel-4442 0d... 466527117us : execlists_reset_prepare: rcs0: depth<-1 > <0> [472.952179] i915_sel-4442 0d... 466527119us : intel_engine_stop_cs: rcs0 > <0> [472.952305] <idle>-0 1..s1 466527119us : process_csb: rcs0 cs-irq head=3, tail=4 Racing and this shows from old world? -Mika > <0> [472.952431] i915_sel-4442 0d... 466527122us : __intel_gt_reset: engine_mask=1 > <0> [472.952557] <idle>-0 1..s1 466527124us : process_csb: rcs0 csb[4]: status=0x00000001:0x00000000 > <0> [472.952683] <idle>-0 1..s1 466527130us : trace_ports: rcs0: promote { 11659:2*, 0:0 } > <0> [472.952808] i915_sel-4442 0d... 466527131us : execlists_reset: rcs0 > <0> [472.952933] i915_sel-4442 0d..1 466527133us : process_csb: rcs0 cs-irq head=3, tail=4 > <0> [472.953059] i915_sel-4442 0d..1 466527134us : process_csb: rcs0 csb[4]: status=0x00000001:0x00000000 > <0> [472.953185] i915_sel-4442 0d..1 466527136us : trace_ports: rcs0: preempted { 11659:2*, 0:0 } > <0> [472.953310] i915_sel-4442 0d..1 466527150us : assert_pending_valid: Nothing pending for promotion! > <0> [472.953436] i915_sel-4442 0d..1 466527158us : process_csb: process_csb:1930 GEM_BUG_ON(!assert_pending_valid(execlists, "promote")) > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=112069 > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> > --- G> drivers/gpu/drm/i915/gt/selftest_hangcheck.c | 2 +- > drivers/gpu/drm/i915/gt/selftest_reset.c | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/drivers/gpu/drm/i915/gt/selftest_hangcheck.c b/drivers/gpu/drm/i915/gt/selftest_hangcheck.c > index b892b47348ab..ba761fcf397b 100644 > --- a/drivers/gpu/drm/i915/gt/selftest_hangcheck.c > +++ b/drivers/gpu/drm/i915/gt/selftest_hangcheck.c > @@ -1563,7 +1563,7 @@ static int __igt_atomic_reset_engine(struct intel_engine_cs *engine, > GEM_TRACE("i915_reset_engine(%s:%s) under %s\n", > engine->name, mode, p->name); > > - tasklet_disable_nosync(t); > + tasklet_disable(t); > p->critical_section_begin(); > > err = intel_engine_reset(engine, NULL); > diff --git a/drivers/gpu/drm/i915/gt/selftest_reset.c b/drivers/gpu/drm/i915/gt/selftest_reset.c > index 6efb9221b7fa..6ad6aca315f6 100644 > --- a/drivers/gpu/drm/i915/gt/selftest_reset.c > +++ b/drivers/gpu/drm/i915/gt/selftest_reset.c > @@ -126,7 +126,7 @@ static int igt_atomic_engine_reset(void *arg) > goto out_unlock; > > for_each_engine(engine, gt, id) { > - tasklet_disable_nosync(&engine->execlists.tasklet); > + tasklet_disable(&engine->execlists.tasklet); > intel_engine_pm_get(engine); > > for (p = igt_atomic_phases; p->name; p++) { > -- > 2.24.0.rc0 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-24 7:21 ` [PATCH] " Mika Kuoppala 2019-10-24 7:21 ` [Intel-gfx] " Mika Kuoppala @ 2019-10-24 7:28 ` Chris Wilson 2019-10-24 7:28 ` [Intel-gfx] " Chris Wilson 2019-10-24 8:06 ` Mika Kuoppala 1 sibling, 2 replies; 16+ messages in thread From: Chris Wilson @ 2019-10-24 7:28 UTC (permalink / raw) To: Mika Kuoppala, intel-gfx Quoting Mika Kuoppala (2019-10-24 08:21:14) > Chris Wilson <chris@chris-wilson.co.uk> writes: > > > When setting up the system to perform the atomic reset, we need to > > serialise with any ongoing interrupt tasklet or else: > > > > <0> [472.951428] i915_sel-4442 0d..1 466527056us : __i915_request_submit: rcs0 fence 11659:2, current 0 > > <0> [472.951554] i915_sel-4442 0d..1 466527059us : __execlists_submission_tasklet: rcs0: queue_priority_hint:-2147483648, submit:yes > > <0> [472.951681] i915_sel-4442 0d..1 466527061us : trace_ports: rcs0: submit { 11659:2, 0:0 } > > <0> [472.951805] i915_sel-4442 0.... 466527114us : __igt_atomic_reset_engine: i915_reset_engine(rcs0:active) under hardirq > > <0> [472.951932] i915_sel-4442 0d... 466527115us : intel_engine_reset: rcs0 flags=11d > > <0> [472.952056] i915_sel-4442 0d... 466527117us : execlists_reset_prepare: rcs0: depth<-1 > > <0> [472.952179] i915_sel-4442 0d... 466527119us : intel_engine_stop_cs: rcs0 > > <0> [472.952305] <idle>-0 1..s1 466527119us : process_csb: rcs0 cs-irq head=3, tail=4 > > Racing and this shows from old world? We have the same CSB events being seen by process_csb() on two different processors. One being issued by the reset in the test, the other by the interrupt; this scenario is supposed to be prevented by flushing the interrupt tasklet with tasklet_disable() before we enter the atomic reset -- but I copied the code to use tasklet_disable_nosync() that is meant to only used from inside the atomic reset after we had serialised (or know we are inside the tasklet) with the tasklet. Basically this bug is of our own invention because we are bypassing the usual setup in order to do engine->reset() from unusual conditions. -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-24 7:28 ` Chris Wilson @ 2019-10-24 7:28 ` Chris Wilson 2019-10-24 8:06 ` Mika Kuoppala 1 sibling, 0 replies; 16+ messages in thread From: Chris Wilson @ 2019-10-24 7:28 UTC (permalink / raw) To: Mika Kuoppala, intel-gfx Quoting Mika Kuoppala (2019-10-24 08:21:14) > Chris Wilson <chris@chris-wilson.co.uk> writes: > > > When setting up the system to perform the atomic reset, we need to > > serialise with any ongoing interrupt tasklet or else: > > > > <0> [472.951428] i915_sel-4442 0d..1 466527056us : __i915_request_submit: rcs0 fence 11659:2, current 0 > > <0> [472.951554] i915_sel-4442 0d..1 466527059us : __execlists_submission_tasklet: rcs0: queue_priority_hint:-2147483648, submit:yes > > <0> [472.951681] i915_sel-4442 0d..1 466527061us : trace_ports: rcs0: submit { 11659:2, 0:0 } > > <0> [472.951805] i915_sel-4442 0.... 466527114us : __igt_atomic_reset_engine: i915_reset_engine(rcs0:active) under hardirq > > <0> [472.951932] i915_sel-4442 0d... 466527115us : intel_engine_reset: rcs0 flags=11d > > <0> [472.952056] i915_sel-4442 0d... 466527117us : execlists_reset_prepare: rcs0: depth<-1 > > <0> [472.952179] i915_sel-4442 0d... 466527119us : intel_engine_stop_cs: rcs0 > > <0> [472.952305] <idle>-0 1..s1 466527119us : process_csb: rcs0 cs-irq head=3, tail=4 > > Racing and this shows from old world? We have the same CSB events being seen by process_csb() on two different processors. One being issued by the reset in the test, the other by the interrupt; this scenario is supposed to be prevented by flushing the interrupt tasklet with tasklet_disable() before we enter the atomic reset -- but I copied the code to use tasklet_disable_nosync() that is meant to only used from inside the atomic reset after we had serialised (or know we are inside the tasklet) with the tasklet. Basically this bug is of our own invention because we are bypassing the usual setup in order to do engine->reset() from unusual conditions. -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-24 7:28 ` Chris Wilson 2019-10-24 7:28 ` [Intel-gfx] " Chris Wilson @ 2019-10-24 8:06 ` Mika Kuoppala 2019-10-24 8:06 ` [Intel-gfx] " Mika Kuoppala 2019-10-24 8:17 ` Chris Wilson 1 sibling, 2 replies; 16+ messages in thread From: Mika Kuoppala @ 2019-10-24 8:06 UTC (permalink / raw) To: Chris Wilson, intel-gfx Chris Wilson <chris@chris-wilson.co.uk> writes: > Quoting Mika Kuoppala (2019-10-24 08:21:14) >> Chris Wilson <chris@chris-wilson.co.uk> writes: >> >> > When setting up the system to perform the atomic reset, we need to >> > serialise with any ongoing interrupt tasklet or else: >> > >> > <0> [472.951428] i915_sel-4442 0d..1 466527056us : __i915_request_submit: rcs0 fence 11659:2, current 0 >> > <0> [472.951554] i915_sel-4442 0d..1 466527059us : __execlists_submission_tasklet: rcs0: queue_priority_hint:-2147483648, submit:yes >> > <0> [472.951681] i915_sel-4442 0d..1 466527061us : trace_ports: rcs0: submit { 11659:2, 0:0 } >> > <0> [472.951805] i915_sel-4442 0.... 466527114us : __igt_atomic_reset_engine: i915_reset_engine(rcs0:active) under hardirq >> > <0> [472.951932] i915_sel-4442 0d... 466527115us : intel_engine_reset: rcs0 flags=11d >> > <0> [472.952056] i915_sel-4442 0d... 466527117us : execlists_reset_prepare: rcs0: depth<-1 >> > <0> [472.952179] i915_sel-4442 0d... 466527119us : intel_engine_stop_cs: rcs0 >> > <0> [472.952305] <idle>-0 1..s1 466527119us : process_csb: rcs0 cs-irq head=3, tail=4 >> >> Racing and this shows from old world? > > We have the same CSB events being seen by process_csb() on two different > processors. One being issued by the reset in the test, the other by the > interrupt; this scenario is supposed to be prevented by flushing the > interrupt tasklet with tasklet_disable() before we enter the atomic > reset -- but I copied the code to use tasklet_disable_nosync() that is > meant to only used from inside the atomic reset after we had serialised > (or know we are inside the tasklet) with the tasklet. Basically this bug > is of our own invention because we are bypassing the usual setup in > order to do engine->reset() from unusual conditions. Some deepdiving into the trace format and tasklet_disable_nosync vs tasklet_disable and I agree with the trace and the patch. I don't know where you copied the nosync from but I did look at preempt_reset and it can pull the nosync trick as it is inside the submission. Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> > -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-24 8:06 ` Mika Kuoppala @ 2019-10-24 8:06 ` Mika Kuoppala 2019-10-24 8:17 ` Chris Wilson 1 sibling, 0 replies; 16+ messages in thread From: Mika Kuoppala @ 2019-10-24 8:06 UTC (permalink / raw) To: Chris Wilson, intel-gfx Chris Wilson <chris@chris-wilson.co.uk> writes: > Quoting Mika Kuoppala (2019-10-24 08:21:14) >> Chris Wilson <chris@chris-wilson.co.uk> writes: >> >> > When setting up the system to perform the atomic reset, we need to >> > serialise with any ongoing interrupt tasklet or else: >> > >> > <0> [472.951428] i915_sel-4442 0d..1 466527056us : __i915_request_submit: rcs0 fence 11659:2, current 0 >> > <0> [472.951554] i915_sel-4442 0d..1 466527059us : __execlists_submission_tasklet: rcs0: queue_priority_hint:-2147483648, submit:yes >> > <0> [472.951681] i915_sel-4442 0d..1 466527061us : trace_ports: rcs0: submit { 11659:2, 0:0 } >> > <0> [472.951805] i915_sel-4442 0.... 466527114us : __igt_atomic_reset_engine: i915_reset_engine(rcs0:active) under hardirq >> > <0> [472.951932] i915_sel-4442 0d... 466527115us : intel_engine_reset: rcs0 flags=11d >> > <0> [472.952056] i915_sel-4442 0d... 466527117us : execlists_reset_prepare: rcs0: depth<-1 >> > <0> [472.952179] i915_sel-4442 0d... 466527119us : intel_engine_stop_cs: rcs0 >> > <0> [472.952305] <idle>-0 1..s1 466527119us : process_csb: rcs0 cs-irq head=3, tail=4 >> >> Racing and this shows from old world? > > We have the same CSB events being seen by process_csb() on two different > processors. One being issued by the reset in the test, the other by the > interrupt; this scenario is supposed to be prevented by flushing the > interrupt tasklet with tasklet_disable() before we enter the atomic > reset -- but I copied the code to use tasklet_disable_nosync() that is > meant to only used from inside the atomic reset after we had serialised > (or know we are inside the tasklet) with the tasklet. Basically this bug > is of our own invention because we are bypassing the usual setup in > order to do engine->reset() from unusual conditions. Some deepdiving into the trace format and tasklet_disable_nosync vs tasklet_disable and I agree with the trace and the patch. I don't know where you copied the nosync from but I did look at preempt_reset and it can pull the nosync trick as it is inside the submission. Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> > -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-24 8:06 ` Mika Kuoppala 2019-10-24 8:06 ` [Intel-gfx] " Mika Kuoppala @ 2019-10-24 8:17 ` Chris Wilson 2019-10-24 8:17 ` [Intel-gfx] " Chris Wilson 1 sibling, 1 reply; 16+ messages in thread From: Chris Wilson @ 2019-10-24 8:17 UTC (permalink / raw) To: Mika Kuoppala, intel-gfx Quoting Mika Kuoppala (2019-10-24 09:06:30) > Chris Wilson <chris@chris-wilson.co.uk> writes: > > > Quoting Mika Kuoppala (2019-10-24 08:21:14) > >> Chris Wilson <chris@chris-wilson.co.uk> writes: > >> > >> > When setting up the system to perform the atomic reset, we need to > >> > serialise with any ongoing interrupt tasklet or else: > >> > > >> > <0> [472.951428] i915_sel-4442 0d..1 466527056us : __i915_request_submit: rcs0 fence 11659:2, current 0 > >> > <0> [472.951554] i915_sel-4442 0d..1 466527059us : __execlists_submission_tasklet: rcs0: queue_priority_hint:-2147483648, submit:yes > >> > <0> [472.951681] i915_sel-4442 0d..1 466527061us : trace_ports: rcs0: submit { 11659:2, 0:0 } > >> > <0> [472.951805] i915_sel-4442 0.... 466527114us : __igt_atomic_reset_engine: i915_reset_engine(rcs0:active) under hardirq > >> > <0> [472.951932] i915_sel-4442 0d... 466527115us : intel_engine_reset: rcs0 flags=11d > >> > <0> [472.952056] i915_sel-4442 0d... 466527117us : execlists_reset_prepare: rcs0: depth<-1 > >> > <0> [472.952179] i915_sel-4442 0d... 466527119us : intel_engine_stop_cs: rcs0 > >> > <0> [472.952305] <idle>-0 1..s1 466527119us : process_csb: rcs0 cs-irq head=3, tail=4 > >> > >> Racing and this shows from old world? > > > > We have the same CSB events being seen by process_csb() on two different > > processors. One being issued by the reset in the test, the other by the > > interrupt; this scenario is supposed to be prevented by flushing the > > interrupt tasklet with tasklet_disable() before we enter the atomic > > reset -- but I copied the code to use tasklet_disable_nosync() that is > > meant to only used from inside the atomic reset after we had serialised > > (or know we are inside the tasklet) with the tasklet. Basically this bug > > is of our own invention because we are bypassing the usual setup in > > order to do engine->reset() from unusual conditions. > > Some deepdiving into the trace format and tasklet_disable_nosync vs > tasklet_disable and I agree with the trace and the patch. > > I don't know where you copied the nosync from but I did look > at preempt_reset and it can pull the nosync trick as it > is inside the submission. A much older preempt timeout series :) -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-24 8:17 ` Chris Wilson @ 2019-10-24 8:17 ` Chris Wilson 0 siblings, 0 replies; 16+ messages in thread From: Chris Wilson @ 2019-10-24 8:17 UTC (permalink / raw) To: Mika Kuoppala, intel-gfx Quoting Mika Kuoppala (2019-10-24 09:06:30) > Chris Wilson <chris@chris-wilson.co.uk> writes: > > > Quoting Mika Kuoppala (2019-10-24 08:21:14) > >> Chris Wilson <chris@chris-wilson.co.uk> writes: > >> > >> > When setting up the system to perform the atomic reset, we need to > >> > serialise with any ongoing interrupt tasklet or else: > >> > > >> > <0> [472.951428] i915_sel-4442 0d..1 466527056us : __i915_request_submit: rcs0 fence 11659:2, current 0 > >> > <0> [472.951554] i915_sel-4442 0d..1 466527059us : __execlists_submission_tasklet: rcs0: queue_priority_hint:-2147483648, submit:yes > >> > <0> [472.951681] i915_sel-4442 0d..1 466527061us : trace_ports: rcs0: submit { 11659:2, 0:0 } > >> > <0> [472.951805] i915_sel-4442 0.... 466527114us : __igt_atomic_reset_engine: i915_reset_engine(rcs0:active) under hardirq > >> > <0> [472.951932] i915_sel-4442 0d... 466527115us : intel_engine_reset: rcs0 flags=11d > >> > <0> [472.952056] i915_sel-4442 0d... 466527117us : execlists_reset_prepare: rcs0: depth<-1 > >> > <0> [472.952179] i915_sel-4442 0d... 466527119us : intel_engine_stop_cs: rcs0 > >> > <0> [472.952305] <idle>-0 1..s1 466527119us : process_csb: rcs0 cs-irq head=3, tail=4 > >> > >> Racing and this shows from old world? > > > > We have the same CSB events being seen by process_csb() on two different > > processors. One being issued by the reset in the test, the other by the > > interrupt; this scenario is supposed to be prevented by flushing the > > interrupt tasklet with tasklet_disable() before we enter the atomic > > reset -- but I copied the code to use tasklet_disable_nosync() that is > > meant to only used from inside the atomic reset after we had serialised > > (or know we are inside the tasklet) with the tasklet. Basically this bug > > is of our own invention because we are bypassing the usual setup in > > order to do engine->reset() from unusual conditions. > > Some deepdiving into the trace format and tasklet_disable_nosync vs > tasklet_disable and I agree with the trace and the patch. > > I don't know where you copied the nosync from but I did look > at preempt_reset and it can pull the nosync trick as it > is inside the submission. A much older preempt timeout series :) -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
* ✗ Fi.CI.IGT: failure for drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-23 23:24 [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets Chris Wilson ` (3 preceding siblings ...) 2019-10-24 7:21 ` [PATCH] " Mika Kuoppala @ 2019-10-25 1:42 ` Patchwork 2019-10-25 1:42 ` [Intel-gfx] " Patchwork 4 siblings, 1 reply; 16+ messages in thread From: Patchwork @ 2019-10-25 1:42 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: drm/i915/selftests: Flush interrupts before disabling tasklets URL : https://patchwork.freedesktop.org/series/68486/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7167_full -> Patchwork_14957_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with Patchwork_14957_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_14957_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_14957_full: ### IGT changes ### #### Possible regressions #### * igt@gem_ctx_shared@q-promotion-bsd1: - shard-glk: [PASS][1] -> [FAIL][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-glk5/igt@gem_ctx_shared@q-promotion-bsd1.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-glk5/igt@gem_ctx_shared@q-promotion-bsd1.html * igt@gem_exec_parallel@fds: - shard-skl: [PASS][3] -> [FAIL][4] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl7/igt@gem_exec_parallel@fds.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl10/igt@gem_exec_parallel@fds.html * igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd: - shard-skl: NOTRUN -> [FAIL][5] [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl10/igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd.html Known issues ------------ Here are the changes found in Patchwork_14957_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_ctx_exec@basic-invalid-context-vcs1: - shard-iclb: [PASS][6] -> [SKIP][7] ([fdo#112080]) +7 similar issues [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb4/igt@gem_ctx_exec@basic-invalid-context-vcs1.html [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb5/igt@gem_ctx_exec@basic-invalid-context-vcs1.html * igt@gem_ctx_isolation@bcs0-s3: - shard-apl: [PASS][8] -> [DMESG-WARN][9] ([fdo#108566]) +2 similar issues [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-apl3/igt@gem_ctx_isolation@bcs0-s3.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-apl1/igt@gem_ctx_isolation@bcs0-s3.html * igt@gem_ctx_isolation@vcs1-dirty-create: - shard-iclb: [PASS][10] -> [SKIP][11] ([fdo#109276] / [fdo#112080]) +2 similar issues [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb1/igt@gem_ctx_isolation@vcs1-dirty-create.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb5/igt@gem_ctx_isolation@vcs1-dirty-create.html * igt@gem_ctx_param@vm: - shard-kbl: [PASS][12] -> [INCOMPLETE][13] ([fdo#103665]) [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-kbl2/igt@gem_ctx_param@vm.html [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-kbl1/igt@gem_ctx_param@vm.html * igt@gem_exec_schedule@preemptive-hang-bsd: - shard-iclb: [PASS][14] -> [SKIP][15] ([fdo#111325]) +2 similar issues [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb3/igt@gem_exec_schedule@preemptive-hang-bsd.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb4/igt@gem_exec_schedule@preemptive-hang-bsd.html * igt@gem_persistent_relocs@forked-interruptible-thrashing: - shard-hsw: [PASS][16] -> [FAIL][17] ([fdo#112037]) [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-hsw5/igt@gem_persistent_relocs@forked-interruptible-thrashing.html [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-hsw6/igt@gem_persistent_relocs@forked-interruptible-thrashing.html * igt@gem_userptr_blits@dmabuf-sync: - shard-snb: [PASS][18] -> [DMESG-WARN][19] ([fdo#111870]) +1 similar issue [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-snb2/igt@gem_userptr_blits@dmabuf-sync.html [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-snb6/igt@gem_userptr_blits@dmabuf-sync.html * igt@i915_pm_rpm@basic-rte: - shard-iclb: [PASS][20] -> [INCOMPLETE][21] ([fdo#107713] / [fdo#108840]) [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb8/igt@i915_pm_rpm@basic-rte.html [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb7/igt@i915_pm_rpm@basic-rte.html * igt@kms_busy@extended-pageflip-hang-newfb-render-c: - shard-skl: [PASS][22] -> [SKIP][23] ([fdo#109271]) +3 similar issues [22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl7/igt@kms_busy@extended-pageflip-hang-newfb-render-c.html [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl10/igt@kms_busy@extended-pageflip-hang-newfb-render-c.html * igt@kms_cursor_legacy@flip-vs-cursor-toggle: - shard-skl: [PASS][24] -> [FAIL][25] ([fdo#102670]) [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl5/igt@kms_cursor_legacy@flip-vs-cursor-toggle.html [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl2/igt@kms_cursor_legacy@flip-vs-cursor-toggle.html * igt@kms_flip@flip-vs-expired-vblank: - shard-skl: [PASS][26] -> [FAIL][27] ([fdo#105363]) [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl8/igt@kms_flip@flip-vs-expired-vblank.html [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl3/igt@kms_flip@flip-vs-expired-vblank.html * igt@kms_flip@flip-vs-suspend: - shard-snb: [PASS][28] -> [INCOMPLETE][29] ([fdo#105411]) [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-snb4/igt@kms_flip@flip-vs-suspend.html [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-snb1/igt@kms_flip@flip-vs-suspend.html * igt@kms_flip@flip-vs-suspend-interruptible: - shard-skl: [PASS][30] -> [INCOMPLETE][31] ([fdo#109507]) [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl2/igt@kms_flip@flip-vs-suspend-interruptible.html [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl2/igt@kms_flip@flip-vs-suspend-interruptible.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-pwrite: - shard-iclb: [PASS][32] -> [FAIL][33] ([fdo#103167]) +4 similar issues [32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-pwrite.html [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-pwrite.html * igt@kms_frontbuffer_tracking@fbc-suspend: - shard-kbl: [PASS][34] -> [DMESG-WARN][35] ([fdo#108566]) +3 similar issues [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-kbl6/igt@kms_frontbuffer_tracking@fbc-suspend.html [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-kbl4/igt@kms_frontbuffer_tracking@fbc-suspend.html * igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min: - shard-skl: [PASS][36] -> [FAIL][37] ([fdo#108145]) [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl4/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl9/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html * igt@kms_psr2_su@frontbuffer: - shard-iclb: [PASS][38] -> [SKIP][39] ([fdo#109642] / [fdo#111068]) [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb2/igt@kms_psr2_su@frontbuffer.html [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb1/igt@kms_psr2_su@frontbuffer.html * igt@kms_psr@psr2_cursor_blt: - shard-iclb: [PASS][40] -> [SKIP][41] ([fdo#109441]) +1 similar issue [40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb2/igt@kms_psr@psr2_cursor_blt.html [41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb1/igt@kms_psr@psr2_cursor_blt.html * igt@prime_busy@after-bsd2: - shard-iclb: [PASS][42] -> [SKIP][43] ([fdo#109276]) +13 similar issues [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb1/igt@prime_busy@after-bsd2.html [43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb5/igt@prime_busy@after-bsd2.html * igt@tools_test@tools_test: - shard-kbl: [PASS][44] -> [SKIP][45] ([fdo#109271]) [44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-kbl2/igt@tools_test@tools_test.html [45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-kbl1/igt@tools_test@tools_test.html #### Possible fixes #### * igt@gem_ctx_isolation@rcs0-s3: - shard-kbl: [DMESG-WARN][46] ([fdo#108566]) -> [PASS][47] +6 similar issues [46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-kbl1/igt@gem_ctx_isolation@rcs0-s3.html [47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-kbl3/igt@gem_ctx_isolation@rcs0-s3.html * igt@gem_ctx_isolation@vcs1-clean: - shard-iclb: [SKIP][48] ([fdo#109276] / [fdo#112080]) -> [PASS][49] [48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb5/igt@gem_ctx_isolation@vcs1-clean.html [49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb2/igt@gem_ctx_isolation@vcs1-clean.html * igt@gem_ctx_shared@exec-single-timeline-bsd: - shard-iclb: [SKIP][50] ([fdo#110841]) -> [PASS][51] [50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb2/igt@gem_ctx_shared@exec-single-timeline-bsd.html [51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb6/igt@gem_ctx_shared@exec-single-timeline-bsd.html * igt@gem_ctx_shared@q-promotion-bsd1: - shard-kbl: [FAIL][52] -> [PASS][53] [52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-kbl2/igt@gem_ctx_shared@q-promotion-bsd1.html [53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-kbl1/igt@gem_ctx_shared@q-promotion-bsd1.html * igt@gem_ctx_switch@vcs1-heavy-queue: - shard-iclb: [SKIP][54] ([fdo#112080]) -> [PASS][55] +10 similar issues [54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb3/igt@gem_ctx_switch@vcs1-heavy-queue.html [55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb4/igt@gem_ctx_switch@vcs1-heavy-queue.html * igt@gem_eio@unwedge-stress: - shard-snb: [FAIL][56] ([fdo#109661]) -> [PASS][57] +1 similar issue [56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-snb5/igt@gem_eio@unwedge-stress.html [57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-snb2/igt@gem_eio@unwedge-stress.html * igt@gem_exec_reloc@basic-cpu-wc-active: - shard-skl: [DMESG-WARN][58] ([fdo#106107]) -> [PASS][59] [58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl6/igt@gem_exec_reloc@basic-cpu-wc-active.html [59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl7/igt@gem_exec_reloc@basic-cpu-wc-active.html * igt@gem_exec_schedule@preempt-other-chain-bsd: - shard-iclb: [SKIP][60] ([fdo#111325]) -> [PASS][61] +7 similar issues [60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb1/igt@gem_exec_schedule@preempt-other-chain-bsd.html [61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb6/igt@gem_exec_schedule@preempt-other-chain-bsd.html * igt@gem_exec_schedule@preempt-queue-bsd1: - shard-iclb: [SKIP][62] ([fdo#109276]) -> [PASS][63] +18 similar issues [62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb7/igt@gem_exec_schedule@preempt-queue-bsd1.html [63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb2/igt@gem_exec_schedule@preempt-queue-bsd1.html * igt@gem_linear_blits@interruptible: - {shard-tglb}: [TIMEOUT][64] -> [PASS][65] +1 similar issue [64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb7/igt@gem_linear_blits@interruptible.html [65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-tglb2/igt@gem_linear_blits@interruptible.html * igt@gem_persistent_relocs@forked-thrash-inactive: - shard-snb: [INCOMPLETE][66] ([fdo#105411]) -> [PASS][67] [66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-snb4/igt@gem_persistent_relocs@forked-thrash-inactive.html [67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-snb5/igt@gem_persistent_relocs@forked-thrash-inactive.html * igt@gem_softpin@noreloc-s3: - shard-skl: [INCOMPLETE][68] ([fdo#104108]) -> [PASS][69] +1 similar issue [68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl6/igt@gem_softpin@noreloc-s3.html [69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl7/igt@gem_softpin@noreloc-s3.html * igt@gem_userptr_blits@map-fixed-invalidate-busy: - shard-snb: [DMESG-WARN][70] ([fdo#111870]) -> [PASS][71] +1 similar issue [70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-snb4/igt@gem_userptr_blits@map-fixed-invalidate-busy.html [71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-busy.html * igt@gem_userptr_blits@sync-unmap: - shard-hsw: [DMESG-WARN][72] ([fdo#111870]) -> [PASS][73] [72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-hsw4/igt@gem_userptr_blits@sync-unmap.html [73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-hsw8/igt@gem_userptr_blits@sync-unmap.html * {igt@i915_pm_dc@dc6-dpms}: - shard-iclb: [FAIL][74] ([fdo#110548]) -> [PASS][75] [74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb3/igt@i915_pm_dc@dc6-dpms.html [75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb7/igt@i915_pm_dc@dc6-dpms.html * igt@i915_pm_rpm@modeset-stress-extra-wait: - shard-glk: [DMESG-WARN][76] ([fdo#105763] / [fdo#106538]) -> [PASS][77] [76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-glk8/igt@i915_pm_rpm@modeset-stress-extra-wait.html [77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-glk2/igt@i915_pm_rpm@modeset-stress-extra-wait.html * igt@i915_pm_rpm@system-suspend: - {shard-tglb}: [INCOMPLETE][78] ([fdo#111747] / [fdo#111850]) -> [PASS][79] [78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb7/igt@i915_pm_rpm@system-suspend.html [79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-tglb6/igt@i915_pm_rpm@system-suspend.html * igt@i915_pm_rpm@system-suspend-execbuf: - shard-skl: [INCOMPLETE][80] ([fdo#104108] / [fdo#107807]) -> [PASS][81] [80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl7/igt@i915_pm_rpm@system-suspend-execbuf.html [81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl10/igt@i915_pm_rpm@system-suspend-execbuf.html * {igt@i915_selftest@live_gt_heartbeat}: - shard-skl: [DMESG-FAIL][82] -> [PASS][83] [82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl3/igt@i915_selftest@live_gt_heartbeat.html [83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl1/igt@i915_selftest@live_gt_heartbeat.html * igt@i915_selftest@live_hangcheck: - shard-hsw: [DMESG-FAIL][84] ([fdo#111991]) -> [PASS][85] [84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-hsw7/igt@i915_selftest@live_hangcheck.html [85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-hsw5/igt@i915_selftest@live_hangcheck.html - shard-iclb: [INCOMPLETE][86] ([fdo#107713] / [fdo#108569]) -> [PASS][87] [86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb3/igt@i915_selftest@live_hangcheck.html [87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb5/igt@i915_selftest@live_hangcheck.html * igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing: - {shard-tglb}: [DMESG-WARN][88] ([fdo#111600]) -> [PASS][89] [88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb6/igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing.html [89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-tglb1/igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing.html * igt@kms_cursor_legacy@cursor-vs-flip-legacy: - shard-hsw: [FAIL][90] ([fdo#103355]) -> [PASS][91] [90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-hsw6/igt@kms_cursor_legacy@cursor-vs-flip-legacy.html [91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-hsw1/igt@kms_cursor_legacy@cursor-vs-flip-legacy.html * igt@kms_flip@blocking-absolute-wf_vblank-interruptible: - {shard-tglb}: [INCOMPLETE][92] -> [PASS][93] +1 similar issue [92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb3/igt@kms_flip@blocking-absolute-wf_vblank-interruptible.html [93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-tglb1/igt@kms_flip@blocking-absolute-wf_vblank-interruptible.html * igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw: - shard-iclb: [FAIL][94] ([fdo#103167]) -> [PASS][95] +8 similar issues [94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb5/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html [95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt: - {shard-tglb}: [FAIL][96] ([fdo#103167]) -> [PASS][97] +1 similar issue [96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt.html [97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-tglb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-blt: - shard-snb: [SKIP][98] ([fdo#109271]) -> [PASS][99] [98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-snb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-blt.html [99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-snb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-blt.html * igt@kms_frontbuffer_tracking@fbc-suspend: - {shard-tglb}: [INCOMPLETE][100] ([fdo#111832] / [fdo#111850] / [fdo#111884]) -> [PASS][101] [100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb4/igt@kms_frontbuffer_tracking@fbc-suspend.html [101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-tglb5/igt@kms_frontbuffer_tracking@fbc-suspend.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-rte: - shard-iclb: [FAIL][102] ([fdo#103167] / [fdo#110378]) -> [PASS][103] [102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-rte.html [103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb4/igt@kms_frontbuffer_tracking@fbcpsr-1p-rte.html * igt@kms_plane_alpha_blend@pipe-b-coverage-7efc: - shard-skl: [FAIL][104] ([fdo#108145] / [fdo#110403]) -> [PASS][105] [104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl9/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html [105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl3/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html * igt@kms_psr@psr2_ == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/selftests: Flush interrupts before disabling tasklets 2019-10-25 1:42 ` ✗ Fi.CI.IGT: failure for " Patchwork @ 2019-10-25 1:42 ` Patchwork 0 siblings, 0 replies; 16+ messages in thread From: Patchwork @ 2019-10-25 1:42 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: drm/i915/selftests: Flush interrupts before disabling tasklets URL : https://patchwork.freedesktop.org/series/68486/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7167_full -> Patchwork_14957_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with Patchwork_14957_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_14957_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI. Possible new issues ------------------- Here are the unknown changes that may have been introduced in Patchwork_14957_full: ### IGT changes ### #### Possible regressions #### * igt@gem_ctx_shared@q-promotion-bsd1: - shard-glk: [PASS][1] -> [FAIL][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-glk5/igt@gem_ctx_shared@q-promotion-bsd1.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-glk5/igt@gem_ctx_shared@q-promotion-bsd1.html * igt@gem_exec_parallel@fds: - shard-skl: [PASS][3] -> [FAIL][4] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl7/igt@gem_exec_parallel@fds.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl10/igt@gem_exec_parallel@fds.html * igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd: - shard-skl: NOTRUN -> [FAIL][5] [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl10/igt@gem_exec_schedule@preempt-queue-contexts-chain-bsd.html Known issues ------------ Here are the changes found in Patchwork_14957_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_ctx_exec@basic-invalid-context-vcs1: - shard-iclb: [PASS][6] -> [SKIP][7] ([fdo#112080]) +7 similar issues [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb4/igt@gem_ctx_exec@basic-invalid-context-vcs1.html [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb5/igt@gem_ctx_exec@basic-invalid-context-vcs1.html * igt@gem_ctx_isolation@bcs0-s3: - shard-apl: [PASS][8] -> [DMESG-WARN][9] ([fdo#108566]) +2 similar issues [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-apl3/igt@gem_ctx_isolation@bcs0-s3.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-apl1/igt@gem_ctx_isolation@bcs0-s3.html * igt@gem_ctx_isolation@vcs1-dirty-create: - shard-iclb: [PASS][10] -> [SKIP][11] ([fdo#109276] / [fdo#112080]) +2 similar issues [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb1/igt@gem_ctx_isolation@vcs1-dirty-create.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb5/igt@gem_ctx_isolation@vcs1-dirty-create.html * igt@gem_ctx_param@vm: - shard-kbl: [PASS][12] -> [INCOMPLETE][13] ([fdo#103665]) [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-kbl2/igt@gem_ctx_param@vm.html [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-kbl1/igt@gem_ctx_param@vm.html * igt@gem_exec_schedule@preemptive-hang-bsd: - shard-iclb: [PASS][14] -> [SKIP][15] ([fdo#111325]) +2 similar issues [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb3/igt@gem_exec_schedule@preemptive-hang-bsd.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb4/igt@gem_exec_schedule@preemptive-hang-bsd.html * igt@gem_persistent_relocs@forked-interruptible-thrashing: - shard-hsw: [PASS][16] -> [FAIL][17] ([fdo#112037]) [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-hsw5/igt@gem_persistent_relocs@forked-interruptible-thrashing.html [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-hsw6/igt@gem_persistent_relocs@forked-interruptible-thrashing.html * igt@gem_userptr_blits@dmabuf-sync: - shard-snb: [PASS][18] -> [DMESG-WARN][19] ([fdo#111870]) +1 similar issue [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-snb2/igt@gem_userptr_blits@dmabuf-sync.html [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-snb6/igt@gem_userptr_blits@dmabuf-sync.html * igt@i915_pm_rpm@basic-rte: - shard-iclb: [PASS][20] -> [INCOMPLETE][21] ([fdo#107713] / [fdo#108840]) [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb8/igt@i915_pm_rpm@basic-rte.html [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb7/igt@i915_pm_rpm@basic-rte.html * igt@kms_busy@extended-pageflip-hang-newfb-render-c: - shard-skl: [PASS][22] -> [SKIP][23] ([fdo#109271]) +3 similar issues [22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl7/igt@kms_busy@extended-pageflip-hang-newfb-render-c.html [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl10/igt@kms_busy@extended-pageflip-hang-newfb-render-c.html * igt@kms_cursor_legacy@flip-vs-cursor-toggle: - shard-skl: [PASS][24] -> [FAIL][25] ([fdo#102670]) [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl5/igt@kms_cursor_legacy@flip-vs-cursor-toggle.html [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl2/igt@kms_cursor_legacy@flip-vs-cursor-toggle.html * igt@kms_flip@flip-vs-expired-vblank: - shard-skl: [PASS][26] -> [FAIL][27] ([fdo#105363]) [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl8/igt@kms_flip@flip-vs-expired-vblank.html [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl3/igt@kms_flip@flip-vs-expired-vblank.html * igt@kms_flip@flip-vs-suspend: - shard-snb: [PASS][28] -> [INCOMPLETE][29] ([fdo#105411]) [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-snb4/igt@kms_flip@flip-vs-suspend.html [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-snb1/igt@kms_flip@flip-vs-suspend.html * igt@kms_flip@flip-vs-suspend-interruptible: - shard-skl: [PASS][30] -> [INCOMPLETE][31] ([fdo#109507]) [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl2/igt@kms_flip@flip-vs-suspend-interruptible.html [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl2/igt@kms_flip@flip-vs-suspend-interruptible.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-pwrite: - shard-iclb: [PASS][32] -> [FAIL][33] ([fdo#103167]) +4 similar issues [32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-pwrite.html [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-pwrite.html * igt@kms_frontbuffer_tracking@fbc-suspend: - shard-kbl: [PASS][34] -> [DMESG-WARN][35] ([fdo#108566]) +3 similar issues [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-kbl6/igt@kms_frontbuffer_tracking@fbc-suspend.html [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-kbl4/igt@kms_frontbuffer_tracking@fbc-suspend.html * igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min: - shard-skl: [PASS][36] -> [FAIL][37] ([fdo#108145]) [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl4/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl9/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html * igt@kms_psr2_su@frontbuffer: - shard-iclb: [PASS][38] -> [SKIP][39] ([fdo#109642] / [fdo#111068]) [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb2/igt@kms_psr2_su@frontbuffer.html [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb1/igt@kms_psr2_su@frontbuffer.html * igt@kms_psr@psr2_cursor_blt: - shard-iclb: [PASS][40] -> [SKIP][41] ([fdo#109441]) +1 similar issue [40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb2/igt@kms_psr@psr2_cursor_blt.html [41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb1/igt@kms_psr@psr2_cursor_blt.html * igt@prime_busy@after-bsd2: - shard-iclb: [PASS][42] -> [SKIP][43] ([fdo#109276]) +13 similar issues [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb1/igt@prime_busy@after-bsd2.html [43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb5/igt@prime_busy@after-bsd2.html * igt@tools_test@tools_test: - shard-kbl: [PASS][44] -> [SKIP][45] ([fdo#109271]) [44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-kbl2/igt@tools_test@tools_test.html [45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-kbl1/igt@tools_test@tools_test.html #### Possible fixes #### * igt@gem_ctx_isolation@rcs0-s3: - shard-kbl: [DMESG-WARN][46] ([fdo#108566]) -> [PASS][47] +6 similar issues [46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-kbl1/igt@gem_ctx_isolation@rcs0-s3.html [47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-kbl3/igt@gem_ctx_isolation@rcs0-s3.html * igt@gem_ctx_isolation@vcs1-clean: - shard-iclb: [SKIP][48] ([fdo#109276] / [fdo#112080]) -> [PASS][49] [48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb5/igt@gem_ctx_isolation@vcs1-clean.html [49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb2/igt@gem_ctx_isolation@vcs1-clean.html * igt@gem_ctx_shared@exec-single-timeline-bsd: - shard-iclb: [SKIP][50] ([fdo#110841]) -> [PASS][51] [50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb2/igt@gem_ctx_shared@exec-single-timeline-bsd.html [51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb6/igt@gem_ctx_shared@exec-single-timeline-bsd.html * igt@gem_ctx_shared@q-promotion-bsd1: - shard-kbl: [FAIL][52] -> [PASS][53] [52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-kbl2/igt@gem_ctx_shared@q-promotion-bsd1.html [53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-kbl1/igt@gem_ctx_shared@q-promotion-bsd1.html * igt@gem_ctx_switch@vcs1-heavy-queue: - shard-iclb: [SKIP][54] ([fdo#112080]) -> [PASS][55] +10 similar issues [54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb3/igt@gem_ctx_switch@vcs1-heavy-queue.html [55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb4/igt@gem_ctx_switch@vcs1-heavy-queue.html * igt@gem_eio@unwedge-stress: - shard-snb: [FAIL][56] ([fdo#109661]) -> [PASS][57] +1 similar issue [56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-snb5/igt@gem_eio@unwedge-stress.html [57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-snb2/igt@gem_eio@unwedge-stress.html * igt@gem_exec_reloc@basic-cpu-wc-active: - shard-skl: [DMESG-WARN][58] ([fdo#106107]) -> [PASS][59] [58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl6/igt@gem_exec_reloc@basic-cpu-wc-active.html [59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl7/igt@gem_exec_reloc@basic-cpu-wc-active.html * igt@gem_exec_schedule@preempt-other-chain-bsd: - shard-iclb: [SKIP][60] ([fdo#111325]) -> [PASS][61] +7 similar issues [60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb1/igt@gem_exec_schedule@preempt-other-chain-bsd.html [61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb6/igt@gem_exec_schedule@preempt-other-chain-bsd.html * igt@gem_exec_schedule@preempt-queue-bsd1: - shard-iclb: [SKIP][62] ([fdo#109276]) -> [PASS][63] +18 similar issues [62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb7/igt@gem_exec_schedule@preempt-queue-bsd1.html [63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb2/igt@gem_exec_schedule@preempt-queue-bsd1.html * igt@gem_linear_blits@interruptible: - {shard-tglb}: [TIMEOUT][64] -> [PASS][65] +1 similar issue [64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb7/igt@gem_linear_blits@interruptible.html [65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-tglb2/igt@gem_linear_blits@interruptible.html * igt@gem_persistent_relocs@forked-thrash-inactive: - shard-snb: [INCOMPLETE][66] ([fdo#105411]) -> [PASS][67] [66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-snb4/igt@gem_persistent_relocs@forked-thrash-inactive.html [67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-snb5/igt@gem_persistent_relocs@forked-thrash-inactive.html * igt@gem_softpin@noreloc-s3: - shard-skl: [INCOMPLETE][68] ([fdo#104108]) -> [PASS][69] +1 similar issue [68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl6/igt@gem_softpin@noreloc-s3.html [69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl7/igt@gem_softpin@noreloc-s3.html * igt@gem_userptr_blits@map-fixed-invalidate-busy: - shard-snb: [DMESG-WARN][70] ([fdo#111870]) -> [PASS][71] +1 similar issue [70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-snb4/igt@gem_userptr_blits@map-fixed-invalidate-busy.html [71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-busy.html * igt@gem_userptr_blits@sync-unmap: - shard-hsw: [DMESG-WARN][72] ([fdo#111870]) -> [PASS][73] [72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-hsw4/igt@gem_userptr_blits@sync-unmap.html [73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-hsw8/igt@gem_userptr_blits@sync-unmap.html * {igt@i915_pm_dc@dc6-dpms}: - shard-iclb: [FAIL][74] ([fdo#110548]) -> [PASS][75] [74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb3/igt@i915_pm_dc@dc6-dpms.html [75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb7/igt@i915_pm_dc@dc6-dpms.html * igt@i915_pm_rpm@modeset-stress-extra-wait: - shard-glk: [DMESG-WARN][76] ([fdo#105763] / [fdo#106538]) -> [PASS][77] [76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-glk8/igt@i915_pm_rpm@modeset-stress-extra-wait.html [77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-glk2/igt@i915_pm_rpm@modeset-stress-extra-wait.html * igt@i915_pm_rpm@system-suspend: - {shard-tglb}: [INCOMPLETE][78] ([fdo#111747] / [fdo#111850]) -> [PASS][79] [78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb7/igt@i915_pm_rpm@system-suspend.html [79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-tglb6/igt@i915_pm_rpm@system-suspend.html * igt@i915_pm_rpm@system-suspend-execbuf: - shard-skl: [INCOMPLETE][80] ([fdo#104108] / [fdo#107807]) -> [PASS][81] [80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl7/igt@i915_pm_rpm@system-suspend-execbuf.html [81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl10/igt@i915_pm_rpm@system-suspend-execbuf.html * {igt@i915_selftest@live_gt_heartbeat}: - shard-skl: [DMESG-FAIL][82] -> [PASS][83] [82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl3/igt@i915_selftest@live_gt_heartbeat.html [83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl1/igt@i915_selftest@live_gt_heartbeat.html * igt@i915_selftest@live_hangcheck: - shard-hsw: [DMESG-FAIL][84] ([fdo#111991]) -> [PASS][85] [84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-hsw7/igt@i915_selftest@live_hangcheck.html [85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-hsw5/igt@i915_selftest@live_hangcheck.html - shard-iclb: [INCOMPLETE][86] ([fdo#107713] / [fdo#108569]) -> [PASS][87] [86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb3/igt@i915_selftest@live_hangcheck.html [87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb5/igt@i915_selftest@live_hangcheck.html * igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing: - {shard-tglb}: [DMESG-WARN][88] ([fdo#111600]) -> [PASS][89] [88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb6/igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing.html [89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-tglb1/igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing.html * igt@kms_cursor_legacy@cursor-vs-flip-legacy: - shard-hsw: [FAIL][90] ([fdo#103355]) -> [PASS][91] [90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-hsw6/igt@kms_cursor_legacy@cursor-vs-flip-legacy.html [91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-hsw1/igt@kms_cursor_legacy@cursor-vs-flip-legacy.html * igt@kms_flip@blocking-absolute-wf_vblank-interruptible: - {shard-tglb}: [INCOMPLETE][92] -> [PASS][93] +1 similar issue [92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb3/igt@kms_flip@blocking-absolute-wf_vblank-interruptible.html [93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-tglb1/igt@kms_flip@blocking-absolute-wf_vblank-interruptible.html * igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw: - shard-iclb: [FAIL][94] ([fdo#103167]) -> [PASS][95] +8 similar issues [94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb5/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html [95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt: - {shard-tglb}: [FAIL][96] ([fdo#103167]) -> [PASS][97] +1 similar issue [96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt.html [97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-tglb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-indfb-plflip-blt.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-blt: - shard-snb: [SKIP][98] ([fdo#109271]) -> [PASS][99] [98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-snb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-blt.html [99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-snb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-blt.html * igt@kms_frontbuffer_tracking@fbc-suspend: - {shard-tglb}: [INCOMPLETE][100] ([fdo#111832] / [fdo#111850] / [fdo#111884]) -> [PASS][101] [100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-tglb4/igt@kms_frontbuffer_tracking@fbc-suspend.html [101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-tglb5/igt@kms_frontbuffer_tracking@fbc-suspend.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-rte: - shard-iclb: [FAIL][102] ([fdo#103167] / [fdo#110378]) -> [PASS][103] [102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-iclb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-rte.html [103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-iclb4/igt@kms_frontbuffer_tracking@fbcpsr-1p-rte.html * igt@kms_plane_alpha_blend@pipe-b-coverage-7efc: - shard-skl: [FAIL][104] ([fdo#108145] / [fdo#110403]) -> [PASS][105] [104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7167/shard-skl9/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html [105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/shard-skl3/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html * igt@kms_psr@psr2_ == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14957/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2019-10-25 1:42 UTC | newest] Thread overview: 16+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2019-10-23 23:24 [PATCH] drm/i915/selftests: Flush interrupts before disabling tasklets Chris Wilson 2019-10-23 23:24 ` [Intel-gfx] " Chris Wilson 2019-10-24 2:27 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork 2019-10-24 2:27 ` [Intel-gfx] " Patchwork 2019-10-24 2:55 ` ✓ Fi.CI.BAT: success " Patchwork 2019-10-24 2:55 ` [Intel-gfx] " Patchwork 2019-10-24 7:21 ` [PATCH] " Mika Kuoppala 2019-10-24 7:21 ` [Intel-gfx] " Mika Kuoppala 2019-10-24 7:28 ` Chris Wilson 2019-10-24 7:28 ` [Intel-gfx] " Chris Wilson 2019-10-24 8:06 ` Mika Kuoppala 2019-10-24 8:06 ` [Intel-gfx] " Mika Kuoppala 2019-10-24 8:17 ` Chris Wilson 2019-10-24 8:17 ` [Intel-gfx] " Chris Wilson 2019-10-25 1:42 ` ✗ Fi.CI.IGT: failure for " Patchwork 2019-10-25 1:42 ` [Intel-gfx] " Patchwork
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox