* [PATCH] drm/i915: Reboot CI if forcewake fails
@ 2019-05-08 11:52 Chris Wilson
2019-05-08 12:18 ` Mika Kuoppala
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Chris Wilson @ 2019-05-08 11:52 UTC (permalink / raw)
To: intel-gfx
If the HW fail to ack a change in forcewake status, the machine is as
good as dead -- it may recover, but in reality it missed the mmio
updates and is now in a very inconsistent state. If it happens, we can't
trust the CI results (or at least the fails may be genuine but due to
the HW being dead and not the actual test!) so reboot the machine (CI
checks for a kernel taint in between each test and reboots if the
machine is tainted).
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
---
drivers/gpu/drm/i915/gt/intel_reset.c | 2 +-
drivers/gpu/drm/i915/i915_drv.h | 11 +++++++++++
drivers/gpu/drm/i915/intel_uncore.c | 8 ++++++--
3 files changed, 18 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c
index 419b3415370b..464369bc55ad 100644
--- a/drivers/gpu/drm/i915/gt/intel_reset.c
+++ b/drivers/gpu/drm/i915/gt/intel_reset.c
@@ -1042,7 +1042,7 @@ void i915_reset(struct drm_i915_private *i915,
* rather than continue on into oblivion. For everyone else,
* the system should still plod along, but they have been warned!
*/
- add_taint(TAINT_WARN, LOCKDEP_STILL_OK);
+ add_taint_for_CI(TAINT_WARN);
error:
__i915_gem_set_wedged(i915);
goto finish;
diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index 0a6ec61496f1..d0257808734c 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -3375,4 +3375,15 @@ static inline u32 i915_scratch_offset(const struct drm_i915_private *i915)
return i915_ggtt_offset(i915->gt.scratch);
}
+static inline void add_taint_for_CI(unsigned int taint)
+{
+ /*
+ * The system is "ok", just about surviving for the user, but
+ * CI results are now unreliable as the HW is very suspect.
+ * CI checks the taint state after every test and will reboot
+ * the machine if the kernel is tainted.
+ */
+ add_taint(taint, LOCKDEP_STILL_OK);
+}
+
#endif
diff --git a/drivers/gpu/drm/i915/intel_uncore.c b/drivers/gpu/drm/i915/intel_uncore.c
index d1d51e1121e2..6ec1bc97b665 100644
--- a/drivers/gpu/drm/i915/intel_uncore.c
+++ b/drivers/gpu/drm/i915/intel_uncore.c
@@ -111,9 +111,11 @@ wait_ack_set(const struct intel_uncore_forcewake_domain *d,
static inline void
fw_domain_wait_ack_clear(const struct intel_uncore_forcewake_domain *d)
{
- if (wait_ack_clear(d, FORCEWAKE_KERNEL))
+ if (wait_ack_clear(d, FORCEWAKE_KERNEL)) {
DRM_ERROR("%s: timed out waiting for forcewake ack to clear.\n",
intel_uncore_forcewake_domain_to_str(d->id));
+ add_taint_for_CI(TAINT_WARN); /* CI unreliable */
+ }
}
enum ack_type {
@@ -186,9 +188,11 @@ fw_domain_get(const struct intel_uncore_forcewake_domain *d)
static inline void
fw_domain_wait_ack_set(const struct intel_uncore_forcewake_domain *d)
{
- if (wait_ack_set(d, FORCEWAKE_KERNEL))
+ if (wait_ack_set(d, FORCEWAKE_KERNEL)) {
DRM_ERROR("%s: timed out waiting for forcewake ack request.\n",
intel_uncore_forcewake_domain_to_str(d->id));
+ add_taint_for_CI(TAINT_WARN); /* CI unreliable */
+ }
}
static inline void
--
2.20.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 6+ messages in thread* Re: [PATCH] drm/i915: Reboot CI if forcewake fails 2019-05-08 11:52 [PATCH] drm/i915: Reboot CI if forcewake fails Chris Wilson @ 2019-05-08 12:18 ` Mika Kuoppala 2019-05-08 12:30 ` Chris Wilson 2019-05-08 13:03 ` Chris Wilson 2019-05-08 12:40 ` ✓ Fi.CI.BAT: success for " Patchwork 2019-05-08 15:09 ` ✓ Fi.CI.IGT: " Patchwork 2 siblings, 2 replies; 6+ messages in thread From: Mika Kuoppala @ 2019-05-08 12:18 UTC (permalink / raw) To: Chris Wilson, intel-gfx Chris Wilson <chris@chris-wilson.co.uk> writes: > If the HW fail to ack a change in forcewake status, the machine is as > good as dead -- it may recover, but in reality it missed the mmio > updates and is now in a very inconsistent state. If it happens, we can't > trust the CI results (or at least the fails may be genuine but due to > the HW being dead and not the actual test!) so reboot the machine (CI > checks for a kernel taint in between each test and reboots if the > machine is tainted). > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> > Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> Sounds and looks reasonable. Should we also taint if we have unclaimed mmio after init sequence? Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> > --- > drivers/gpu/drm/i915/gt/intel_reset.c | 2 +- > drivers/gpu/drm/i915/i915_drv.h | 11 +++++++++++ > drivers/gpu/drm/i915/intel_uncore.c | 8 ++++++-- > 3 files changed, 18 insertions(+), 3 deletions(-) > > diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c > index 419b3415370b..464369bc55ad 100644 > --- a/drivers/gpu/drm/i915/gt/intel_reset.c > +++ b/drivers/gpu/drm/i915/gt/intel_reset.c > @@ -1042,7 +1042,7 @@ void i915_reset(struct drm_i915_private *i915, > * rather than continue on into oblivion. For everyone else, > * the system should still plod along, but they have been warned! > */ > - add_taint(TAINT_WARN, LOCKDEP_STILL_OK); > + add_taint_for_CI(TAINT_WARN); > error: > __i915_gem_set_wedged(i915); > goto finish; > diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h > index 0a6ec61496f1..d0257808734c 100644 > --- a/drivers/gpu/drm/i915/i915_drv.h > +++ b/drivers/gpu/drm/i915/i915_drv.h > @@ -3375,4 +3375,15 @@ static inline u32 i915_scratch_offset(const struct drm_i915_private *i915) > return i915_ggtt_offset(i915->gt.scratch); > } > > +static inline void add_taint_for_CI(unsigned int taint) > +{ > + /* > + * The system is "ok", just about surviving for the user, but > + * CI results are now unreliable as the HW is very suspect. > + * CI checks the taint state after every test and will reboot > + * the machine if the kernel is tainted. > + */ > + add_taint(taint, LOCKDEP_STILL_OK); > +} > + > #endif > diff --git a/drivers/gpu/drm/i915/intel_uncore.c b/drivers/gpu/drm/i915/intel_uncore.c > index d1d51e1121e2..6ec1bc97b665 100644 > --- a/drivers/gpu/drm/i915/intel_uncore.c > +++ b/drivers/gpu/drm/i915/intel_uncore.c > @@ -111,9 +111,11 @@ wait_ack_set(const struct intel_uncore_forcewake_domain *d, > static inline void > fw_domain_wait_ack_clear(const struct intel_uncore_forcewake_domain *d) > { > - if (wait_ack_clear(d, FORCEWAKE_KERNEL)) > + if (wait_ack_clear(d, FORCEWAKE_KERNEL)) { > DRM_ERROR("%s: timed out waiting for forcewake ack to clear.\n", > intel_uncore_forcewake_domain_to_str(d->id)); > + add_taint_for_CI(TAINT_WARN); /* CI unreliable */ > + } > } > > enum ack_type { > @@ -186,9 +188,11 @@ fw_domain_get(const struct intel_uncore_forcewake_domain *d) > static inline void > fw_domain_wait_ack_set(const struct intel_uncore_forcewake_domain *d) > { > - if (wait_ack_set(d, FORCEWAKE_KERNEL)) > + if (wait_ack_set(d, FORCEWAKE_KERNEL)) { > DRM_ERROR("%s: timed out waiting for forcewake ack request.\n", > intel_uncore_forcewake_domain_to_str(d->id)); > + add_taint_for_CI(TAINT_WARN); /* CI unreliable */ > + } > } > > static inline void > -- > 2.20.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] drm/i915: Reboot CI if forcewake fails 2019-05-08 12:18 ` Mika Kuoppala @ 2019-05-08 12:30 ` Chris Wilson 2019-05-08 13:03 ` Chris Wilson 1 sibling, 0 replies; 6+ messages in thread From: Chris Wilson @ 2019-05-08 12:30 UTC (permalink / raw) To: Mika Kuoppala, intel-gfx Quoting Mika Kuoppala (2019-05-08 13:18:06) > Chris Wilson <chris@chris-wilson.co.uk> writes: > > > If the HW fail to ack a change in forcewake status, the machine is as > > good as dead -- it may recover, but in reality it missed the mmio > > updates and is now in a very inconsistent state. If it happens, we can't > > trust the CI results (or at least the fails may be genuine but due to > > the HW being dead and not the actual test!) so reboot the machine (CI > > checks for a kernel taint in between each test and reboots if the > > machine is tainted). > > > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> > > Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> > > Sounds and looks reasonable. Should we also taint if we have > unclaimed mmio after init sequence? The unclaimed mmio throws a WARN so it naturally gets the add_taint(TAINT_WARN) and CI reboots already. Otherwise, yes :) -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] drm/i915: Reboot CI if forcewake fails 2019-05-08 12:18 ` Mika Kuoppala 2019-05-08 12:30 ` Chris Wilson @ 2019-05-08 13:03 ` Chris Wilson 1 sibling, 0 replies; 6+ messages in thread From: Chris Wilson @ 2019-05-08 13:03 UTC (permalink / raw) To: Mika Kuoppala, intel-gfx Quoting Mika Kuoppala (2019-05-08 13:18:06) > Chris Wilson <chris@chris-wilson.co.uk> writes: > > > If the HW fail to ack a change in forcewake status, the machine is as > > good as dead -- it may recover, but in reality it missed the mmio > > updates and is now in a very inconsistent state. If it happens, we can't > > trust the CI results (or at least the fails may be genuine but due to > > the HW being dead and not the actual test!) so reboot the machine (CI > > checks for a kernel taint in between each test and reboots if the > > machine is tainted). > > > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> > > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> > > Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> [snip] > Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> And pushed, thanks for the review. -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 6+ messages in thread
* ✓ Fi.CI.BAT: success for drm/i915: Reboot CI if forcewake fails 2019-05-08 11:52 [PATCH] drm/i915: Reboot CI if forcewake fails Chris Wilson 2019-05-08 12:18 ` Mika Kuoppala @ 2019-05-08 12:40 ` Patchwork 2019-05-08 15:09 ` ✓ Fi.CI.IGT: " Patchwork 2 siblings, 0 replies; 6+ messages in thread From: Patchwork @ 2019-05-08 12:40 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: drm/i915: Reboot CI if forcewake fails URL : https://patchwork.freedesktop.org/series/60412/ State : success == Summary == CI Bug Log - changes from CI_DRM_6063 -> Patchwork_12986 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/ Known issues ------------ Here are the changes found in Patchwork_12986 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_exec_suspend@basic-s3: - fi-blb-e6850: [PASS][1] -> [INCOMPLETE][2] ([fdo#107718]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html #### Possible fixes #### * igt@gem_exec_basic@readonly-render: - {fi-icl-y}: [INCOMPLETE][3] ([fdo#107713]) -> [PASS][4] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/fi-icl-y/igt@gem_exec_basic@readonly-render.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/fi-icl-y/igt@gem_exec_basic@readonly-render.html #### Warnings #### * igt@i915_selftest@live_hangcheck: - fi-apl-guc: [INCOMPLETE][5] ([fdo#103927]) -> [DMESG-FAIL][6] ([fdo#110620]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/fi-apl-guc/igt@i915_selftest@live_hangcheck.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/fi-apl-guc/igt@i915_selftest@live_hangcheck.html * igt@runner@aborted: - fi-apl-guc: [FAIL][7] ([fdo#110624]) -> [FAIL][8] ([fdo#110622]) [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/fi-apl-guc/igt@runner@aborted.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/fi-apl-guc/igt@runner@aborted.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718 [fdo#110620]: https://bugs.freedesktop.org/show_bug.cgi?id=110620 [fdo#110622]: https://bugs.freedesktop.org/show_bug.cgi?id=110622 [fdo#110624]: https://bugs.freedesktop.org/show_bug.cgi?id=110624 Participating hosts (53 -> 45) ------------------------------ Missing (8): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus Build changes ------------- * Linux: CI_DRM_6063 -> Patchwork_12986 CI_DRM_6063: 44ae4003d35743cbc7883825c5fe777d136b5247 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_4972: f052e49a43cc9704ea5f240df15dd9d3dfed68ab @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_12986: d0634a52dcb114fe2343e6921503473018e1121f @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == d0634a52dcb1 drm/i915: Reboot CI if forcewake fails == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/ _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 6+ messages in thread
* ✓ Fi.CI.IGT: success for drm/i915: Reboot CI if forcewake fails 2019-05-08 11:52 [PATCH] drm/i915: Reboot CI if forcewake fails Chris Wilson 2019-05-08 12:18 ` Mika Kuoppala 2019-05-08 12:40 ` ✓ Fi.CI.BAT: success for " Patchwork @ 2019-05-08 15:09 ` Patchwork 2 siblings, 0 replies; 6+ messages in thread From: Patchwork @ 2019-05-08 15:09 UTC (permalink / raw) To: Chris Wilson; +Cc: intel-gfx == Series Details == Series: drm/i915: Reboot CI if forcewake fails URL : https://patchwork.freedesktop.org/series/60412/ State : success == Summary == CI Bug Log - changes from CI_DRM_6063_full -> Patchwork_12986_full ==================================================== Summary ------- **SUCCESS** No regressions found. Known issues ------------ Here are the changes found in Patchwork_12986_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_eio@reset-stress: - shard-snb: [PASS][1] -> [FAIL][2] ([fdo#109661]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-snb6/igt@gem_eio@reset-stress.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-snb4/igt@gem_eio@reset-stress.html * igt@gem_workarounds@suspend-resume: - shard-apl: [PASS][3] -> [DMESG-WARN][4] ([fdo#108566]) +6 similar issues [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-apl7/igt@gem_workarounds@suspend-resume.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-apl5/igt@gem_workarounds@suspend-resume.html * igt@i915_pm_rpm@system-suspend: - shard-skl: [PASS][5] -> [INCOMPLETE][6] ([fdo#104108] / [fdo#107773] / [fdo#107807]) [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-skl5/igt@i915_pm_rpm@system-suspend.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-skl3/igt@i915_pm_rpm@system-suspend.html * igt@i915_pm_rpm@system-suspend-execbuf: - shard-glk: [PASS][7] -> [SKIP][8] ([fdo#109271]) +1 similar issue [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-glk1/igt@i915_pm_rpm@system-suspend-execbuf.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-glk3/igt@i915_pm_rpm@system-suspend-execbuf.html * igt@kms_flip@flip-vs-expired-vblank-interruptible: - shard-glk: [PASS][9] -> [FAIL][10] ([fdo#105363]) [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-glk4/igt@kms_flip@flip-vs-expired-vblank-interruptible.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-glk9/igt@kms_flip@flip-vs-expired-vblank-interruptible.html * igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-mmap-gtt: - shard-iclb: [PASS][11] -> [FAIL][12] ([fdo#103167]) +4 similar issues [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-iclb3/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-mmap-gtt.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-iclb2/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-mmap-gtt.html * igt@kms_plane_alpha_blend@pipe-b-coverage-7efc: - shard-skl: [PASS][13] -> [FAIL][14] ([fdo#108145] / [fdo#110403]) [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-skl4/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-skl10/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html * igt@kms_plane_lowres@pipe-a-tiling-y: - shard-iclb: [PASS][15] -> [FAIL][16] ([fdo#103166]) [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-iclb6/igt@kms_plane_lowres@pipe-a-tiling-y.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-iclb6/igt@kms_plane_lowres@pipe-a-tiling-y.html * igt@kms_plane_scaling@pipe-a-scaler-with-pixel-format: - shard-glk: [PASS][17] -> [SKIP][18] ([fdo#109271] / [fdo#109278]) +2 similar issues [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-glk9/igt@kms_plane_scaling@pipe-a-scaler-with-pixel-format.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-glk8/igt@kms_plane_scaling@pipe-a-scaler-with-pixel-format.html * igt@kms_psr@psr2_sprite_blt: - shard-iclb: [PASS][19] -> [SKIP][20] ([fdo#109441]) +1 similar issue [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-iclb2/igt@kms_psr@psr2_sprite_blt.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-iclb4/igt@kms_psr@psr2_sprite_blt.html * igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend: - shard-glk: [PASS][21] -> [INCOMPLETE][22] ([fdo#103359] / [k.org#198133]) [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-glk8/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-glk3/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html #### Possible fixes #### * igt@gem_ctx_isolation@vecs0-s3: - shard-kbl: [DMESG-WARN][23] ([fdo#108566]) -> [PASS][24] [23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-kbl1/igt@gem_ctx_isolation@vecs0-s3.html [24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-kbl6/igt@gem_ctx_isolation@vecs0-s3.html * igt@gem_eio@reset-stress: - shard-skl: [FAIL][25] ([fdo#105957]) -> [PASS][26] [25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-skl2/igt@gem_eio@reset-stress.html [26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-skl10/igt@gem_eio@reset-stress.html * igt@i915_pm_rpm@sysfs-read: - shard-skl: [INCOMPLETE][27] ([fdo#107807]) -> [PASS][28] [27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-skl1/igt@i915_pm_rpm@sysfs-read.html [28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-skl8/igt@i915_pm_rpm@sysfs-read.html * igt@i915_suspend@sysfs-reader: - shard-apl: [DMESG-WARN][29] ([fdo#108566]) -> [PASS][30] +5 similar issues [29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-apl4/igt@i915_suspend@sysfs-reader.html [30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-apl5/igt@i915_suspend@sysfs-reader.html * igt@kms_cursor_crc@cursor-64x21-onscreen: - shard-apl: [INCOMPLETE][31] ([fdo#103927]) -> [PASS][32] +1 similar issue [31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-apl4/igt@kms_cursor_crc@cursor-64x21-onscreen.html [32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-apl6/igt@kms_cursor_crc@cursor-64x21-onscreen.html * igt@kms_cursor_edge_walk@pipe-b-128x128-right-edge: - shard-snb: [SKIP][33] ([fdo#109271] / [fdo#109278]) -> [PASS][34] [33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-snb2/igt@kms_cursor_edge_walk@pipe-b-128x128-right-edge.html [34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-snb1/igt@kms_cursor_edge_walk@pipe-b-128x128-right-edge.html * igt@kms_cursor_legacy@2x-long-nonblocking-modeset-vs-cursor-atomic: - shard-glk: [FAIL][35] ([fdo#107409]) -> [PASS][36] [35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-glk9/igt@kms_cursor_legacy@2x-long-nonblocking-modeset-vs-cursor-atomic.html [36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-glk8/igt@kms_cursor_legacy@2x-long-nonblocking-modeset-vs-cursor-atomic.html * igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic: - shard-glk: [FAIL][37] ([fdo#106509] / [fdo#107409]) -> [PASS][38] [37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-glk2/igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic.html [38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-glk5/igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move: - shard-iclb: [FAIL][39] ([fdo#103167]) -> [PASS][40] +5 similar issues [39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move.html [40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-iclb6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-move.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-rte: - shard-iclb: [FAIL][41] ([fdo#103167] / [fdo#110378]) -> [PASS][42] [41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-iclb2/igt@kms_frontbuffer_tracking@fbcpsr-1p-rte.html [42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-iclb4/igt@kms_frontbuffer_tracking@fbcpsr-1p-rte.html * igt@kms_plane@pixel-format-pipe-a-planes-source-clamping: - shard-glk: [SKIP][43] ([fdo#109271]) -> [PASS][44] [43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-glk3/igt@kms_plane@pixel-format-pipe-a-planes-source-clamping.html [44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-glk9/igt@kms_plane@pixel-format-pipe-a-planes-source-clamping.html * igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min: - shard-skl: [FAIL][45] ([fdo#108145]) -> [PASS][46] +1 similar issue [45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-skl5/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min.html [46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-skl3/igt@kms_plane_alpha_blend@pipe-c-constant-alpha-min.html * igt@kms_psr@psr2_cursor_render: - shard-iclb: [SKIP][47] ([fdo#109441]) -> [PASS][48] +2 similar issues [47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-iclb5/igt@kms_psr@psr2_cursor_render.html [48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-iclb2/igt@kms_psr@psr2_cursor_render.html * igt@kms_rotation_crc@multiplane-rotation-cropping-top: - shard-kbl: [FAIL][49] ([fdo#109016]) -> [PASS][50] [49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-kbl7/igt@kms_rotation_crc@multiplane-rotation-cropping-top.html [50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-kbl7/igt@kms_rotation_crc@multiplane-rotation-cropping-top.html * igt@kms_setmode@basic: - shard-kbl: [FAIL][51] ([fdo#99912]) -> [PASS][52] [51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-kbl2/igt@kms_setmode@basic.html [52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-kbl1/igt@kms_setmode@basic.html #### Warnings #### * igt@kms_flip@flip-vs-suspend: - shard-apl: [FAIL][53] ([fdo#103375]) -> [DMESG-WARN][54] ([fdo#108566]) [53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-apl3/igt@kms_flip@flip-vs-suspend.html [54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-apl2/igt@kms_flip@flip-vs-suspend.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-gtt: - shard-skl: [FAIL][55] ([fdo#108040]) -> [FAIL][56] ([fdo#103167]) [55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6063/shard-skl4/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-gtt.html [56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/shard-skl10/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-mmap-gtt.html [fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166 [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167 [fdo#103359]: https://bugs.freedesktop.org/show_bug.cgi?id=103359 [fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375 [fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927 [fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108 [fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363 [fdo#105957]: https://bugs.freedesktop.org/show_bug.cgi?id=105957 [fdo#106509]: https://bugs.freedesktop.org/show_bug.cgi?id=106509 [fdo#107409]: https://bugs.freedesktop.org/show_bug.cgi?id=107409 [fdo#107773]: https://bugs.freedesktop.org/show_bug.cgi?id=107773 [fdo#107807]: https://bugs.freedesktop.org/show_bug.cgi?id=107807 [fdo#108040]: https://bugs.freedesktop.org/show_bug.cgi?id=108040 [fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145 [fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566 [fdo#109016]: https://bugs.freedesktop.org/show_bug.cgi?id=109016 [fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271 [fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278 [fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441 [fdo#109661]: https://bugs.freedesktop.org/show_bug.cgi?id=109661 [fdo#110378]: https://bugs.freedesktop.org/show_bug.cgi?id=110378 [fdo#110403]: https://bugs.freedesktop.org/show_bug.cgi?id=110403 [fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912 [k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133 Participating hosts (10 -> 10) ------------------------------ No changes in participating hosts Build changes ------------- * Linux: CI_DRM_6063 -> Patchwork_12986 CI_DRM_6063: 44ae4003d35743cbc7883825c5fe777d136b5247 @ git://anongit.freedesktop.org/gfx-ci/linux IGT_4972: f052e49a43cc9704ea5f240df15dd9d3dfed68ab @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_12986: d0634a52dcb114fe2343e6921503473018e1121f @ git://anongit.freedesktop.org/gfx-ci/linux piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_12986/ _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-05-08 15:09 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2019-05-08 11:52 [PATCH] drm/i915: Reboot CI if forcewake fails Chris Wilson 2019-05-08 12:18 ` Mika Kuoppala 2019-05-08 12:30 ` Chris Wilson 2019-05-08 13:03 ` Chris Wilson 2019-05-08 12:40 ` ✓ Fi.CI.BAT: success for " Patchwork 2019-05-08 15:09 ` ✓ Fi.CI.IGT: " Patchwork
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).