* [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset
@ 2019-09-10 7:57 Chris Wilson
2019-09-10 8:02 ` [PATCH v2] " Chris Wilson
` (3 more replies)
0 siblings, 4 replies; 8+ messages in thread
From: Chris Wilson @ 2019-09-10 7:57 UTC (permalink / raw)
To: intel-gfx
During reset, we try to ensure no forward progress of the CS prior to
the reset by setting the STOP_RING bit in RING_MI_MODE. Since gen9, this
register is context saved and do we end up in the odd situation where we
save the STOP_RING bit and so try to stop the engine again immediately
upon resume. This is quite unexpected and causes us to complain about an
early CS completion event!
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111514
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
---
drivers/gpu/drm/i915/gt/intel_lrc.c | 10 ++++++++++
drivers/gpu/drm/i915/gt/intel_lrc_reg.h | 2 ++
2 files changed, 12 insertions(+)
diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
index f073aea6a1fe..761f5cbd90d3 100644
--- a/drivers/gpu/drm/i915/gt/intel_lrc.c
+++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
@@ -2368,6 +2368,15 @@ static struct i915_request *active_request(struct i915_request *rq)
return active;
}
+static void __execlists_reset_reg_state(const struct intel_context *ce,
+ const struct intel_engine_cs *engine)
+{
+ u32 *regs = ce->lrc_reg_state;
+
+ if (INTEL_GEN(engine->i915) >= 9)
+ regs[GEN9_CTX_RING_MI_MODE + 1] |= _MASKED_BIT_DISABLE(STOP_RING);
+}
+
static void __execlists_reset(struct intel_engine_cs *engine, bool stalled)
{
struct intel_engine_execlists * const execlists = &engine->execlists;
@@ -2455,6 +2464,7 @@ static void __execlists_reset(struct intel_engine_cs *engine, bool stalled)
GEM_TRACE("%s replay {head:%04x, tail:%04x\n",
engine->name, ce->ring->head, ce->ring->tail);
intel_ring_update_space(ce->ring);
+ __execlists_reset_reg_state(ce, engine);
__execlists_update_reg_state(ce, engine);
mutex_release(&ce->pin_mutex.dep_map, 0, _THIS_IP_);
diff --git a/drivers/gpu/drm/i915/gt/intel_lrc_reg.h b/drivers/gpu/drm/i915/gt/intel_lrc_reg.h
index 68caf8541866..7e773e74a3fe 100644
--- a/drivers/gpu/drm/i915/gt/intel_lrc_reg.h
+++ b/drivers/gpu/drm/i915/gt/intel_lrc_reg.h
@@ -39,6 +39,8 @@
#define CTX_R_PWR_CLK_STATE 0x42
#define CTX_END 0x44
+#define GEN9_CTX_RING_MI_MODE 0x54
+
/* GEN12+ Reg State Context */
#define GEN12_CTX_BB_PER_CTX_PTR 0x12
#define GEN12_CTX_LRI_HEADER_3 0x41
--
2.23.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 8+ messages in thread* [PATCH v2] drm/i915/execlists: Clear STOP_RING bit on reset
2019-09-10 7:57 [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset Chris Wilson
@ 2019-09-10 8:02 ` Chris Wilson
2019-09-10 8:36 ` ✓ Fi.CI.BAT: success for drm/i915/execlists: Clear STOP_RING bit on reset (rev2) Patchwork
` (2 subsequent siblings)
3 siblings, 0 replies; 8+ messages in thread
From: Chris Wilson @ 2019-09-10 8:02 UTC (permalink / raw)
To: intel-gfx
During reset, we try to ensure no forward progress of the CS prior to
the reset by setting the STOP_RING bit in RING_MI_MODE. Since gen9, this
register is context saved and do we end up in the odd situation where we
save the STOP_RING bit and so try to stop the engine again immediately
upon resume. This is quite unexpected and causes us to complain about an
early CS completion event!
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111514
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
---
drivers/gpu/drm/i915/gt/intel_lrc.c | 12 ++++++++++++
drivers/gpu/drm/i915/gt/intel_lrc_reg.h | 2 ++
2 files changed, 14 insertions(+)
diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
index f073aea6a1fe..64170ce0c91b 100644
--- a/drivers/gpu/drm/i915/gt/intel_lrc.c
+++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
@@ -2368,6 +2368,17 @@ static struct i915_request *active_request(struct i915_request *rq)
return active;
}
+static void __execlists_reset_reg_state(const struct intel_context *ce,
+ const struct intel_engine_cs *engine)
+{
+ u32 *regs = ce->lrc_reg_state;
+
+ if (INTEL_GEN(engine->i915) >= 9) {
+ regs[GEN9_CTX_RING_MI_MODE + 1] &= ~STOP_RING;
+ regs[GEN9_CTX_RING_MI_MODE + 1] |= STOP_RING << 16;
+ }
+}
+
static void __execlists_reset(struct intel_engine_cs *engine, bool stalled)
{
struct intel_engine_execlists * const execlists = &engine->execlists;
@@ -2455,6 +2466,7 @@ static void __execlists_reset(struct intel_engine_cs *engine, bool stalled)
GEM_TRACE("%s replay {head:%04x, tail:%04x\n",
engine->name, ce->ring->head, ce->ring->tail);
intel_ring_update_space(ce->ring);
+ __execlists_reset_reg_state(ce, engine);
__execlists_update_reg_state(ce, engine);
mutex_release(&ce->pin_mutex.dep_map, 0, _THIS_IP_);
diff --git a/drivers/gpu/drm/i915/gt/intel_lrc_reg.h b/drivers/gpu/drm/i915/gt/intel_lrc_reg.h
index 68caf8541866..7e773e74a3fe 100644
--- a/drivers/gpu/drm/i915/gt/intel_lrc_reg.h
+++ b/drivers/gpu/drm/i915/gt/intel_lrc_reg.h
@@ -39,6 +39,8 @@
#define CTX_R_PWR_CLK_STATE 0x42
#define CTX_END 0x44
+#define GEN9_CTX_RING_MI_MODE 0x54
+
/* GEN12+ Reg State Context */
#define GEN12_CTX_BB_PER_CTX_PTR 0x12
#define GEN12_CTX_LRI_HEADER_3 0x41
--
2.23.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 8+ messages in thread* ✓ Fi.CI.BAT: success for drm/i915/execlists: Clear STOP_RING bit on reset (rev2)
2019-09-10 7:57 [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset Chris Wilson
2019-09-10 8:02 ` [PATCH v2] " Chris Wilson
@ 2019-09-10 8:36 ` Patchwork
2019-09-10 9:31 ` [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset Mika Kuoppala
2019-09-10 13:48 ` ✓ Fi.CI.IGT: success for drm/i915/execlists: Clear STOP_RING bit on reset (rev2) Patchwork
3 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2019-09-10 8:36 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/execlists: Clear STOP_RING bit on reset (rev2)
URL : https://patchwork.freedesktop.org/series/66473/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6857 -> Patchwork_14336
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/
Known issues
------------
Here are the changes found in Patchwork_14336 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_switch@legacy-render:
- fi-cml-u2: [PASS][1] -> [INCOMPLETE][2] ([fdo#110566] / [fdo#111381])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/fi-cml-u2/igt@gem_ctx_switch@legacy-render.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/fi-cml-u2/igt@gem_ctx_switch@legacy-render.html
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s4-devices:
- fi-blb-e6850: [INCOMPLETE][3] ([fdo#107718]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/fi-blb-e6850/igt@gem_exec_suspend@basic-s4-devices.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/fi-blb-e6850/igt@gem_exec_suspend@basic-s4-devices.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#110566]: https://bugs.freedesktop.org/show_bug.cgi?id=110566
[fdo#111381]: https://bugs.freedesktop.org/show_bug.cgi?id=111381
[fdo#111593]: https://bugs.freedesktop.org/show_bug.cgi?id=111593
Participating hosts (53 -> 42)
------------------------------
Missing (11): fi-ilk-m540 fi-cml-s fi-hsw-4200u fi-byt-squawks fi-icl-u2 fi-bsw-cyan fi-icl-u3 fi-icl-y fi-byt-clapper fi-bdw-samus fi-snb-2600
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_6857 -> Patchwork_14336
CI-20190529: 20190529
CI_DRM_6857: 4dd97e0eb8e88d369c067c71f5796568f41585c1 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5177: 8f351d693352d21c96cef38c3fd77f778c6d7c33 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_14336: 11751f7acb4e405718ea6f90a5df8aabdd98679e @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
11751f7acb4e drm/i915/execlists: Clear STOP_RING bit on reset
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset
2019-09-10 7:57 [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset Chris Wilson
2019-09-10 8:02 ` [PATCH v2] " Chris Wilson
2019-09-10 8:36 ` ✓ Fi.CI.BAT: success for drm/i915/execlists: Clear STOP_RING bit on reset (rev2) Patchwork
@ 2019-09-10 9:31 ` Mika Kuoppala
2019-09-10 9:39 ` Chris Wilson
2019-09-10 13:48 ` ✓ Fi.CI.IGT: success for drm/i915/execlists: Clear STOP_RING bit on reset (rev2) Patchwork
3 siblings, 1 reply; 8+ messages in thread
From: Mika Kuoppala @ 2019-09-10 9:31 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
Chris Wilson <chris@chris-wilson.co.uk> writes:
> During reset, we try to ensure no forward progress of the CS prior to
> the reset by setting the STOP_RING bit in RING_MI_MODE. Since gen9, this
> register is context saved and do we end up in the odd situation where we
> save the STOP_RING bit and so try to stop the engine again immediately
> upon resume. This is quite unexpected and causes us to complain about an
> early CS completion event!
The completion event is a product of resume with a stop set?
If my memory serves me well, we have fought this before.
But I have still missing pieces. Why would we not want to
set this for all contexts primed for execution? In gen8 too.
I mean, queuing context with a ring stopped just doesn't
sound right on any gen.
-Mika
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111514
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_lrc.c | 10 ++++++++++
> drivers/gpu/drm/i915/gt/intel_lrc_reg.h | 2 ++
> 2 files changed, 12 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
> index f073aea6a1fe..761f5cbd90d3 100644
> --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
> @@ -2368,6 +2368,15 @@ static struct i915_request *active_request(struct i915_request *rq)
> return active;
> }
>
> +static void __execlists_reset_reg_state(const struct intel_context *ce,
> + const struct intel_engine_cs *engine)
> +{
> + u32 *regs = ce->lrc_reg_state;
> +
> + if (INTEL_GEN(engine->i915) >= 9)
> + regs[GEN9_CTX_RING_MI_MODE + 1] |= _MASKED_BIT_DISABLE(STOP_RING);
> +}
> +
> static void __execlists_reset(struct intel_engine_cs *engine, bool stalled)
> {
> struct intel_engine_execlists * const execlists = &engine->execlists;
> @@ -2455,6 +2464,7 @@ static void __execlists_reset(struct intel_engine_cs *engine, bool stalled)
> GEM_TRACE("%s replay {head:%04x, tail:%04x\n",
> engine->name, ce->ring->head, ce->ring->tail);
> intel_ring_update_space(ce->ring);
> + __execlists_reset_reg_state(ce, engine);
> __execlists_update_reg_state(ce, engine);
> mutex_release(&ce->pin_mutex.dep_map, 0, _THIS_IP_);
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_lrc_reg.h b/drivers/gpu/drm/i915/gt/intel_lrc_reg.h
> index 68caf8541866..7e773e74a3fe 100644
> --- a/drivers/gpu/drm/i915/gt/intel_lrc_reg.h
> +++ b/drivers/gpu/drm/i915/gt/intel_lrc_reg.h
> @@ -39,6 +39,8 @@
> #define CTX_R_PWR_CLK_STATE 0x42
> #define CTX_END 0x44
>
> +#define GEN9_CTX_RING_MI_MODE 0x54
> +
> /* GEN12+ Reg State Context */
> #define GEN12_CTX_BB_PER_CTX_PTR 0x12
> #define GEN12_CTX_LRI_HEADER_3 0x41
> --
> 2.23.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset
2019-09-10 9:31 ` [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset Mika Kuoppala
@ 2019-09-10 9:39 ` Chris Wilson
2019-09-10 9:54 ` Mika Kuoppala
0 siblings, 1 reply; 8+ messages in thread
From: Chris Wilson @ 2019-09-10 9:39 UTC (permalink / raw)
To: Mika Kuoppala, intel-gfx
Quoting Mika Kuoppala (2019-09-10 10:31:05)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
>
> > During reset, we try to ensure no forward progress of the CS prior to
> > the reset by setting the STOP_RING bit in RING_MI_MODE. Since gen9, this
> > register is context saved and do we end up in the odd situation where we
> > save the STOP_RING bit and so try to stop the engine again immediately
> > upon resume. This is quite unexpected and causes us to complain about an
> > early CS completion event!
>
> The completion event is a product of resume with a stop set?
A completion event is the product of STOP_RING. Whether it is the
completion event that we keep failing on...
> If my memory serves me well, we have fought this before.
Exactly. We've reduced the frequency of when we apply the STOP_RING, but
have not eliminated it.
> But I have still missing pieces. Why would we not want to
> set this for all contexts primed for execution? In gen8 too.
It's not in the gen8 context, afaict. I searched the context image for an
LRI with the RING_MI_MODE register:
https://patchwork.freedesktop.org/patch/329919/?series=66468&rev=1
> I mean, queuing context with a ring stopped just doesn't
> sound right on any gen.
We clear the STOP_RING in the register on resume just in case, and that
is being flagged on Icelake (which I put down to the reset not being very
thorough!). The remaining question was whether we were restoring it from
the context image.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset
2019-09-10 9:39 ` Chris Wilson
@ 2019-09-10 9:54 ` Mika Kuoppala
2019-09-10 10:02 ` Chris Wilson
0 siblings, 1 reply; 8+ messages in thread
From: Mika Kuoppala @ 2019-09-10 9:54 UTC (permalink / raw)
To: Chris Wilson, intel-gfx
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Quoting Mika Kuoppala (2019-09-10 10:31:05)
>> Chris Wilson <chris@chris-wilson.co.uk> writes:
>>
>> > During reset, we try to ensure no forward progress of the CS prior to
>> > the reset by setting the STOP_RING bit in RING_MI_MODE. Since gen9, this
>> > register is context saved and do we end up in the odd situation where we
>> > save the STOP_RING bit and so try to stop the engine again immediately
>> > upon resume. This is quite unexpected and causes us to complain about an
>> > early CS completion event!
>>
>> The completion event is a product of resume with a stop set?
>
> A completion event is the product of STOP_RING. Whether it is the
> completion event that we keep failing on...
>
>> If my memory serves me well, we have fought this before.
>
> Exactly. We've reduced the frequency of when we apply the STOP_RING, but
> have not eliminated it.
>
>> But I have still missing pieces. Why would we not want to
>> set this for all contexts primed for execution? In gen8 too.
>
> It's not in the gen8 context, afaict. I searched the context image for an
> LRI with the RING_MI_MODE register:
> https://patchwork.freedesktop.org/patch/329919/?series=66468&rev=1
>
>> I mean, queuing context with a ring stopped just doesn't
>> sound right on any gen.
>
> We clear the STOP_RING in the register on resume just in case, and that
> is being flagged on Icelake (which I put down to the reset not being very
> thorough!). The remaining question was whether we were restoring it from
> the context image.
Hmm yeah, I was confused of the sequence of setup. With that cleared
and with the context state being worked on, perhaps we can add
sanity checkers to the queuing path.
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset
2019-09-10 9:54 ` Mika Kuoppala
@ 2019-09-10 10:02 ` Chris Wilson
0 siblings, 0 replies; 8+ messages in thread
From: Chris Wilson @ 2019-09-10 10:02 UTC (permalink / raw)
To: Mika Kuoppala, intel-gfx
Quoting Mika Kuoppala (2019-09-10 10:54:43)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
>
> > Quoting Mika Kuoppala (2019-09-10 10:31:05)
> >> Chris Wilson <chris@chris-wilson.co.uk> writes:
> >>
> >> > During reset, we try to ensure no forward progress of the CS prior to
> >> > the reset by setting the STOP_RING bit in RING_MI_MODE. Since gen9, this
> >> > register is context saved and do we end up in the odd situation where we
> >> > save the STOP_RING bit and so try to stop the engine again immediately
> >> > upon resume. This is quite unexpected and causes us to complain about an
> >> > early CS completion event!
> >>
> >> The completion event is a product of resume with a stop set?
> >
> > A completion event is the product of STOP_RING. Whether it is the
> > completion event that we keep failing on...
> >
> >> If my memory serves me well, we have fought this before.
> >
> > Exactly. We've reduced the frequency of when we apply the STOP_RING, but
> > have not eliminated it.
> >
> >> But I have still missing pieces. Why would we not want to
> >> set this for all contexts primed for execution? In gen8 too.
> >
> > It's not in the gen8 context, afaict. I searched the context image for an
> > LRI with the RING_MI_MODE register:
> > https://patchwork.freedesktop.org/patch/329919/?series=66468&rev=1
> >
> >> I mean, queuing context with a ring stopped just doesn't
> >> sound right on any gen.
> >
> > We clear the STOP_RING in the register on resume just in case, and that
> > is being flagged on Icelake (which I put down to the reset not being very
> > thorough!). The remaining question was whether we were restoring it from
> > the context image.
>
> Hmm yeah, I was confused of the sequence of setup. With that cleared
> and with the context state being worked on, perhaps we can add
> sanity checkers to the queuing path.
Yeah, I think there's definitely some fun we can have here. At the very
least a check that CTX_RING_START == ring->start would be a good
sanitycheck.
> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
As always, the only way to be sure if this changes the mtbf is to let is
soak. One day I may be able to run my own extended testing on icl!
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
* ✓ Fi.CI.IGT: success for drm/i915/execlists: Clear STOP_RING bit on reset (rev2)
2019-09-10 7:57 [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset Chris Wilson
` (2 preceding siblings ...)
2019-09-10 9:31 ` [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset Mika Kuoppala
@ 2019-09-10 13:48 ` Patchwork
3 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2019-09-10 13:48 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
== Series Details ==
Series: drm/i915/execlists: Clear STOP_RING bit on reset (rev2)
URL : https://patchwork.freedesktop.org/series/66473/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6857_full -> Patchwork_14336_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_14336_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_schedule@pi-ringfull-bsd:
- shard-iclb: [PASS][1] -> [SKIP][2] ([fdo#111325])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb5/igt@gem_exec_schedule@pi-ringfull-bsd.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb2/igt@gem_exec_schedule@pi-ringfull-bsd.html
* igt@gem_exec_schedule@promotion-bsd1:
- shard-iclb: [PASS][3] -> [SKIP][4] ([fdo#109276]) +16 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb4/igt@gem_exec_schedule@promotion-bsd1.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb5/igt@gem_exec_schedule@promotion-bsd1.html
* igt@gem_workarounds@suspend-resume-context:
- shard-skl: [PASS][5] -> [INCOMPLETE][6] ([fdo#104108]) +2 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-skl3/igt@gem_workarounds@suspend-resume-context.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-skl1/igt@gem_workarounds@suspend-resume-context.html
* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-apl: [PASS][7] -> [DMESG-WARN][8] ([fdo#108566]) +3 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-apl5/igt@i915_suspend@fence-restore-tiled2untiled.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-apl8/igt@i915_suspend@fence-restore-tiled2untiled.html
* igt@kms_atomic_transition@1x-modeset-transitions-fencing:
- shard-apl: [PASS][9] -> [INCOMPLETE][10] ([fdo#103927]) +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-apl6/igt@kms_atomic_transition@1x-modeset-transitions-fencing.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-apl5/igt@kms_atomic_transition@1x-modeset-transitions-fencing.html
* igt@kms_cursor_crc@pipe-b-cursor-128x128-offscreen:
- shard-iclb: [PASS][11] -> [INCOMPLETE][12] ([fdo#107713])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb5/igt@kms_cursor_crc@pipe-b-cursor-128x128-offscreen.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb7/igt@kms_cursor_crc@pipe-b-cursor-128x128-offscreen.html
* igt@kms_cursor_crc@pipe-b-cursor-64x64-sliding:
- shard-snb: [PASS][13] -> [SKIP][14] ([fdo#109271])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-snb1/igt@kms_cursor_crc@pipe-b-cursor-64x64-sliding.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-snb2/igt@kms_cursor_crc@pipe-b-cursor-64x64-sliding.html
* igt@kms_cursor_edge_walk@pipe-b-128x128-right-edge:
- shard-snb: [PASS][15] -> [SKIP][16] ([fdo#109271] / [fdo#109278])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-snb1/igt@kms_cursor_edge_walk@pipe-b-128x128-right-edge.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-snb2/igt@kms_cursor_edge_walk@pipe-b-128x128-right-edge.html
* igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy:
- shard-hsw: [PASS][17] -> [FAIL][18] ([fdo#105767])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-hsw7/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-hsw4/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-legacy.html
* igt@kms_cursor_legacy@cursor-vs-flip-atomic:
- shard-hsw: [PASS][19] -> [FAIL][20] ([fdo#103355])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-hsw1/igt@kms_cursor_legacy@cursor-vs-flip-atomic.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-hsw8/igt@kms_cursor_legacy@cursor-vs-flip-atomic.html
* igt@kms_fbcon_fbt@psr:
- shard-skl: [PASS][21] -> [DMESG-WARN][22] ([fdo#106107])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-skl6/igt@kms_fbcon_fbt@psr.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-skl1/igt@kms_fbcon_fbt@psr.html
* igt@kms_frontbuffer_tracking@basic:
- shard-iclb: [PASS][23] -> [FAIL][24] ([fdo#103167]) +2 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb7/igt@kms_frontbuffer_tracking@basic.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb4/igt@kms_frontbuffer_tracking@basic.html
* igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min:
- shard-skl: [PASS][25] -> [FAIL][26] ([fdo#108145])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-skl5/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-skl7/igt@kms_plane_alpha_blend@pipe-a-constant-alpha-min.html
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [PASS][27] -> [SKIP][28] ([fdo#109642] / [fdo#111068])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb2/igt@kms_psr2_su@frontbuffer.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb7/igt@kms_psr2_su@frontbuffer.html
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: [PASS][29] -> [SKIP][30] ([fdo#109441]) +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb7/igt@kms_psr@psr2_cursor_plane_move.html
* igt@kms_setmode@basic:
- shard-glk: [PASS][31] -> [FAIL][32] ([fdo#99912])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-glk4/igt@kms_setmode@basic.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-glk2/igt@kms_setmode@basic.html
* igt@perf@polling:
- shard-skl: [PASS][33] -> [FAIL][34] ([fdo#110728])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-skl5/igt@perf@polling.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-skl10/igt@perf@polling.html
* igt@perf_pmu@rc6:
- shard-kbl: [PASS][35] -> [SKIP][36] ([fdo#109271])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-kbl3/igt@perf_pmu@rc6.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-kbl7/igt@perf_pmu@rc6.html
#### Possible fixes ####
* igt@gem_eio@reset-stress:
- shard-glk: [FAIL][37] ([fdo#109661]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-glk2/igt@gem_eio@reset-stress.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-glk2/igt@gem_eio@reset-stress.html
* igt@gem_exec_schedule@independent-bsd2:
- shard-iclb: [SKIP][39] ([fdo#109276]) -> [PASS][40] +10 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb7/igt@gem_exec_schedule@independent-bsd2.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb4/igt@gem_exec_schedule@independent-bsd2.html
* igt@gem_exec_schedule@preempt-self-bsd:
- shard-iclb: [SKIP][41] ([fdo#111325]) -> [PASS][42] +3 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb4/igt@gem_exec_schedule@preempt-self-bsd.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb5/igt@gem_exec_schedule@preempt-self-bsd.html
* igt@gem_tiled_swapping@non-threaded:
- shard-glk: [DMESG-WARN][43] ([fdo#108686]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-glk3/igt@gem_tiled_swapping@non-threaded.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-glk6/igt@gem_tiled_swapping@non-threaded.html
* igt@gem_workarounds@suspend-resume-context:
- shard-apl: [DMESG-WARN][45] ([fdo#108566]) -> [PASS][46] +2 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-apl3/igt@gem_workarounds@suspend-resume-context.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-apl5/igt@gem_workarounds@suspend-resume-context.html
* igt@i915_selftest@live_gtt:
- shard-glk: [DMESG-WARN][47] ([fdo#110788]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-glk3/igt@i915_selftest@live_gtt.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-glk1/igt@i915_selftest@live_gtt.html
* igt@kms_cursor_legacy@all-pipes-torture-move:
- shard-skl: [DMESG-WARN][49] ([fdo#107122]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-skl9/igt@kms_cursor_legacy@all-pipes-torture-move.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-skl2/igt@kms_cursor_legacy@all-pipes-torture-move.html
* igt@kms_flip@flip-vs-expired-vblank:
- shard-skl: [FAIL][51] ([fdo#105363]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-skl5/igt@kms_flip@flip-vs-expired-vblank.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-skl10/igt@kms_flip@flip-vs-expired-vblank.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- shard-glk: [FAIL][53] ([fdo#105363]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-glk1/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-glk3/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
* igt@kms_flip_tiling@flip-to-y-tiled:
- shard-iclb: [FAIL][55] ([fdo#107931] / [fdo#108134]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb4/igt@kms_flip_tiling@flip-to-y-tiled.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb8/igt@kms_flip_tiling@flip-to-y-tiled.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt:
- shard-iclb: [FAIL][57] ([fdo#103167]) -> [PASS][58] +5 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-plflip-blt.html
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [FAIL][59] ([fdo#108145] / [fdo#110403]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-skl4/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-skl6/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
* igt@kms_plane_lowres@pipe-a-tiling-x:
- shard-iclb: [FAIL][61] ([fdo#103166]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb7/igt@kms_plane_lowres@pipe-a-tiling-x.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb4/igt@kms_plane_lowres@pipe-a-tiling-x.html
* igt@kms_psr@psr2_sprite_plane_move:
- shard-iclb: [SKIP][63] ([fdo#109441]) -> [PASS][64] +1 similar issue
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb1/igt@kms_psr@psr2_sprite_plane_move.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb2/igt@kms_psr@psr2_sprite_plane_move.html
* igt@kms_setmode@basic:
- shard-apl: [FAIL][65] ([fdo#99912]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-apl8/igt@kms_setmode@basic.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-apl7/igt@kms_setmode@basic.html
* igt@perf@blocking:
- shard-skl: [FAIL][67] ([fdo#110728]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-skl9/igt@perf@blocking.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-skl9/igt@perf@blocking.html
#### Warnings ####
* igt@gem_mocs_settings@mocs-rc6-bsd2:
- shard-iclb: [FAIL][69] ([fdo#111330]) -> [SKIP][70] ([fdo#109276])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb4/igt@gem_mocs_settings@mocs-rc6-bsd2.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb5/igt@gem_mocs_settings@mocs-rc6-bsd2.html
* igt@gem_mocs_settings@mocs-reset-bsd2:
- shard-iclb: [SKIP][71] ([fdo#109276]) -> [FAIL][72] ([fdo#111330]) +1 similar issue
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-iclb6/igt@gem_mocs_settings@mocs-reset-bsd2.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-iclb4/igt@gem_mocs_settings@mocs-reset-bsd2.html
* igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
- shard-apl: [INCOMPLETE][73] ([fdo#103927]) -> [FAIL][74] ([fdo#108145])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6857/shard-apl3/igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14336/shard-apl7/igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb.html
[fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103355]: https://bugs.freedesktop.org/show_bug.cgi?id=103355
[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#105767]: https://bugs.freedesktop.org/show_bug.cgi?id=105767
[fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107
[fdo#107122]: https://bugs.freedesktop.org/show_bug.cgi?id=107122
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107931]: https://bugs.freedesktop.org/show_bug.cgi?id=107931
[fdo#108134]: https://bugs.freedesktop.org/show_bug.cgi?id=108134
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
[fdo#108686]: https://bugs.freedesktop.org/show_bug.cgi?id=108686
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#109661]: https://bugs.freedesktop.org/show_bug.cgi?id=109661
[fdo#110403]: https://bugs.freedesktop.org/show_bug.cgi?id=110403
[fdo#110728]: https://bugs.freedesktop.org/show_bug.cgi?id=110728
[fdo#110788]: https://bugs.freedesktop.org/show_bug.cgi?id=110788
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325
[fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330
[fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_6857 -> Patchwork_14336
CI-20190529: 20190529
CI_DRM_6857: 4dd97e0eb8e88d369c067c71f5796568f41585c1 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5177: 8f351d693352d21c96cef38c3fd77f778c6d7c33 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_14336: 11751f7acb4e405718ea6f90a5df8aabdd98679e @ 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_14336/
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2019-09-10 13:48 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-09-10 7:57 [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset Chris Wilson
2019-09-10 8:02 ` [PATCH v2] " Chris Wilson
2019-09-10 8:36 ` ✓ Fi.CI.BAT: success for drm/i915/execlists: Clear STOP_RING bit on reset (rev2) Patchwork
2019-09-10 9:31 ` [PATCH] drm/i915/execlists: Clear STOP_RING bit on reset Mika Kuoppala
2019-09-10 9:39 ` Chris Wilson
2019-09-10 9:54 ` Mika Kuoppala
2019-09-10 10:02 ` Chris Wilson
2019-09-10 13:48 ` ✓ Fi.CI.IGT: success for drm/i915/execlists: Clear STOP_RING bit on reset (rev2) Patchwork
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.