<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [CI] igt@* - incomplete - Softdog on gvtdvm machines, pi_lock lockdep in boot.log" href="https://bugs.freedesktop.org/show_bug.cgi?id=105600#c40">Comment # 40</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [CI] igt@* - incomplete - Softdog on gvtdvm machines, pi_lock lockdep in boot.log" href="https://bugs.freedesktop.org/show_bug.cgi?id=105600">bug 105600</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=105600#c39">comment #39</a>) > (In reply to Martin Peres from <a href="show_bug.cgi?id=105600#c37">comment #37</a>) > > (In reply to Tomi Sarvela from <a href="show_bug.cgi?id=105600#c36">comment #36</a>) > > > 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@gem_exec_reuse@contexts: > > > > - > > <a href="https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_87/fi-bdw-gvtdvm/">https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_87/fi-bdw-gvtdvm/</a> > > igt@<a href="mailto:gem_exec_reuse@contexts.html">gem_exec_reuse@contexts.html</a> > > - > > <a href="https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_85/fi-skl-gvtdvm/">https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_85/fi-skl-gvtdvm/</a> > > igt@<a href="mailto:gem_exec_reuse@contexts.html">gem_exec_reuse@contexts.html</a> > > > > 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 <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> 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: <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [CI] igt@* - incomplete - Softdog on gvtdvm machines, pi_lock lockdep in boot.log" href="show_bug.cgi?id=105600#c39">https://bugs.freedesktop.org/show_bug.cgi?id=105600#c39</a> Signed-off-by: Chris Wilson <<a href="mailto:chris@chris-wilson.co.uk">chris@chris-wilson.co.uk</a>> Cc: Tvrtko Ursulin <<a href="mailto:tvrtko.ursulin@intel.com">tvrtko.ursulin@intel.com</a>> Reviewed-by: Tvrtko Ursulin <<a href="mailto:tvrtko.ursulin@intel.com">tvrtko.ursulin@intel.com</a>> Link: <a href="https://patchwork.freedesktop.org/patch/msgid/20180719072206.16015-1-chris@chris-wilson.co.uk">https://patchwork.freedesktop.org/patch/msgid/20180719072206.16015-1-chris@chris-wilson.co.uk</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>