Getting already a bit pissed off with need on hitting retest button as those
failures
have nothing in common with DBuf changes. It's again gem-gem-gem...
Best Regards,
Lisovskiy Stanislav
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
___
== Series Details ==
Series: drm/i915/dsb: Fix in mmio offset calculation of DSB instance
URL : https://patchwork.freedesktop.org/series/70490/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7489_full -> Patchwork_15603_full
== Series Details ==
Series: drm/i915/gt: Detect if we miss WaIdleLiteRestore (rev2)
URL : https://patchwork.freedesktop.org/series/70605/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7511 -> Patchwork_15651
Summary
--
== Series Details ==
Series: drm/i915/gt: Detect if we miss WaIdleLiteRestore
URL : https://patchwork.freedesktop.org/series/70605/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7511 -> Patchwork_15650
Summary
---
**
In order to avoid confusing the HW, we must never submit an empty ring
during lite-restore, that is we should always advance the RING_TAIL
before submitting to stay ahead of the RING_HEAD.
Normally this is prevented by keeping a couple of spare NOPs in the
request->wa_tail so that on resubmission
Quoting Chris Wilson (2019-12-09 02:01:45)
> In order to avoid confusing the HW, we must never submit an empty ring
> during lite-restore, that is we should always advance the RING_TAIL
> before submitting to stay ahead of the RING_HEAD.
>
> Normally this is prevented by keeping a couple of spare
In order to avoid confusing the HW, we must never submit an empty ring
during lite-restore, that is we should always advance the RING_TAIL
before submitting to stay ahead of the RING_HEAD.
Normally this is prevented by keeping a couple of spare NOPs in the
request->wa_tail so that on resubmission
Quoting Chris Wilson (2019-12-08 23:34:56)
> Despite taking the intel_gt wakeref, and asserting that we do indeed
> hold the runtime-pm wakeref for the device, our mmio debug insists that
> the irq enabling is not being recognised:
Scratch the dropping of fw, we miss interrupts.
-Chris
___
== Series Details ==
Series: drm/i915/gt: Suppress unclaimed mmio warnings for irq enabling
URL : https://patchwork.freedesktop.org/series/70603/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7511 -> Patchwork_15649
Summary
== Series Details ==
Series: drm/i915/gt: Suppress unclaimed mmio warnings for irq enabling
URL : https://patchwork.freedesktop.org/series/70603/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
5626a524b60b drm/i915/gt: Suppress unclaimed mmio warnings for irq enabling
-:39: WARN
== Series Details ==
Series: drm/i915/gt: Skip request resubmission if lite-restore w/a already
applied (rev2)
URL : https://patchwork.freedesktop.org/series/70602/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7511 -> Patchwork_15648
=
== Series Details ==
Series: drm/i915/gt: Skip request resubmission if lite-restore w/a already
applied
URL : https://patchwork.freedesktop.org/series/70602/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7511 -> Patchwork_15647
Quoting Chris Wilson (2019-12-08 23:33:08)
> Be careful that we never submit the same request again if we have
> already applied the LiteRestore w/a upon it -- as the HW may complete
> the request as we submit the ELSP and so become confused by the request
> to execute an empty ring.
>
> To submit
Despite taking the intel_gt wakeref, and asserting that we do indeed
hold the runtime-pm wakeref for the device, our mmio debug insists that
the irq enabling is not being recognised:
[ 19.342117] Unclaimed write to register 0x220a8
[ 19.342185] WARNING: CPU: 2 PID: 619 at __unclaimed_reg_debug
Be careful that we never submit the same request again if we have
already applied the LiteRestore w/a upon it -- as the HW may complete
the request as we submit the ELSP and so become confused by the request
to execute an empty ring.
To submit the same request in ELSP[0] three times (so triggering
Be careful that we never submit the same request again if we have
already applied the LiteRestore w/a upon it -- as the HW may complete
the request as we submit the ELSP and so become confused by the request
to execute an empty ring.
To submit the same request in ELSP[0] three times (so triggering
== Series Details ==
Series: series starting with [1/2] drm/i915/gem: Avoid rcu_barrier() from
shrinker paths
URL : https://patchwork.freedesktop.org/series/70601/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7510_full -> Patchwork_15645_full
On Wed, Dec 04, 2019 at 04:51:36PM -0500, Jerome Glisse wrote:
> On Tue, Dec 03, 2019 at 11:19:43AM -0800, Niranjan Vishwanathapura wrote:
> > On Tue, Nov 26, 2019 at 06:32:52PM +, Jason Gunthorpe wrote:
> > > On Mon, Nov 25, 2019 at 11:33:27AM -0500, Jerome Glisse wrote:
> > > > On Fri, Nov 22
== Series Details ==
Series: drm: Add support for DP 1.4 Compliance edid corruption test (rev2)
URL : https://patchwork.freedesktop.org/series/70530/
State : failure
== Summary ==
Applying: drm: Add support for DP 1.4 Compliance edid corruption test
error: corrupt patch at line 53
error: could
[AMD Official Use Only - Internal Distribution Only]
Hi All:
I just checked the CI report
https://patchwork.freedesktop.org/series/70530/. The failures described in
there are not quite related to my patch. Seems it is a false-positive. Does
anyone know something about the issue described i
== Series Details ==
Series: series starting with [1/2] drm/i915/gem: Avoid rcu_barrier() from
shrinker paths
URL : https://patchwork.freedesktop.org/series/70601/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7510 -> Patchwork_15645
==
== Series Details ==
Series: drm/i915/gt: Turn vm off then on again for gen7 mm switch (rev2)
URL : https://patchwork.freedesktop.org/series/70597/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7509_full -> Patchwork_15643_full
=
== Series Details ==
Series: series starting with [1/2] drm/i915/gem: Avoid rcu_barrier() from
shrinker paths
URL : https://patchwork.freedesktop.org/series/70601/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
5bab4aea886c drm/i915/gem: Avoid rcu_barrier() from shrinker paths
As i915_gem_object_unbind() waits on an rcu_barrier() to flush vm
releases (and destruction of their bound vma), we have to be careful not
to invoke that barrier from beneath the shrinker:
<4> [430.222671] WARNING: possible circular locking dependency detected
<4> [430.222673] 5.4.0-rc8-CI-CI_DRM_
If someone else acquires the i915_vma before we complete our wait and
unbind it, we currently error out with -EBUSY. Use -EAGAIN instead so
that if necessary the caller is prepared to try again.
Signed-off-by: Chris Wilson
Cc: Matthew Auld
---
drivers/gpu/drm/i915/i915_vma.c | 2 +-
1 file chan
== Series Details ==
Series: drm/i915: Change i915_vma_unbind() to report -EAGAIN on activity
URL : https://patchwork.freedesktop.org/series/70600/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7509 -> Patchwork_15644
Summa
== Series Details ==
Series: drm/i915/gt: Turn vm off then on again for gen7 mm switch (rev2)
URL : https://patchwork.freedesktop.org/series/70597/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7509 -> Patchwork_15643
Summa
If someone else acquires the i915_vma before we complete our wait and
unbind it, we currently error out with -EBUSY. Use -EAGAIN instead so
that if necessary the caller is prepared to try again.
Signed-off-by: Chris Wilson
Cc: Matthew Auld
---
drivers/gpu/drm/i915/i915_vma.c | 2 +-
1 file chan
"Have you tried switching it off and on again?"
Set the size of the mm to 0 to disable all PD cachelines, before
enabling the whole mm again. Let's see if that tricks the TLB into
reloading.
Signed-off-by: Chris Wilson
Cc: Mika Kuoppala
---
.../gpu/drm/i915/gt/intel_ring_submission.c | 22 ++
== Series Details ==
Series: drm/i915/gt: Turn vm off then on again for gen7 mm switch
URL : https://patchwork.freedesktop.org/series/70597/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7509 -> Patchwork_15642
Summary
"Have you tried switching it off and on again?"
Set the size of the mm to 0 to disable all PD cachelines, before
enabling the whole mm again. Let's see if that tricks the TLB into
reloading.
Signed-off-by: Chris Wilson
Cc: Mika Kuoppala
---
.../gpu/drm/i915/gt/intel_ring_submission.c | 20 ++
== Series Details ==
Series: drm/i915/gem: Avoid rcu_barrier() from shrinker paths
URL : https://patchwork.freedesktop.org/series/70596/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7509_full -> Patchwork_15641_full
Summar
32 matches
Mail list logo
