[Bug 105600] [CI] igt@* - incomplete - Softdog on gvtdvm machines, pi_lock lockdep in boot.log
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Jul 19 11:33:54 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=105600
--- Comment #40 from Chris Wilson <chris at chris-wilson.co.uk> ---
(In reply to Chris Wilson from comment #39)
> (In reply to Martin Peres from comment #37)
> > (In reply to Tomi Sarvela from comment #36)
> > > BDW-GVTDVM and SKL-GVTDVM qemu command line invocation changed as it was,
> > > and incomplete issues seemed to disappear.
> >
> > Still hapenning 100% of the time when running igt at gem_exec_reuse@contexts:
> >
> > -
> > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_87/fi-bdw-gvtdvm/
> > igt at gem_exec_reuse@contexts.html
> > -
> > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_85/fi-skl-gvtdvm/
> > igt at gem_exec_reuse@contexts.html
> >
> > Can you please check it out?
>
> That's a regression common to all machines,
commit 46b1063f91e5680eff2a6b9fe432f6aae3bef54e (HEAD -> drm-intel-next-queued,
drm-intel/for-linux-next, drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date: Thu Jul 19 08:22:06 2018 +0100
drm/i915: Handle recursive shrinker for vma->last_active allocation
If we call into the shrinker for direct relcaim inside kmalloc, it will
retire the requests. If we retire the vma->last_active while processing a
new i915_vma_move_to_active() we can upset the delicate bookkeeping
required for the cache. After the possible invocation of the shrinker, we
need to double check the vma->last_active is still valid.
Fixes: 8b293eb53a7d ("drm/i915: Track the last-active inside the i915_vma")
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105600#c39
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
Link:
https://patchwork.freedesktop.org/patch/msgid/20180719072206.16015-1-chris@chris-wilson.co.uk
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180719/00b0cad8/attachment.html>
More information about the intel-gfx-bugs
mailing list