<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_CLOSED  bz_closed"
   title="CLOSED DUPLICATE - [CI][SNB,HSW,APL,KBL] igt@prime_mmap@test_userptr - possible circular locking dependency detected"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=102939#c9">Comment # 9</a>
              on <a class="bz_bug_link 
          bz_status_CLOSED  bz_closed"
   title="CLOSED DUPLICATE - [CI][SNB,HSW,APL,KBL] igt@prime_mmap@test_userptr - possible circular locking dependency detected"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=102939">bug 102939</a>
              from <span class="vcard"><a class="email" href="mailto:marta.lofstedt@intel.com" title="Marta Löfstedt <marta.lofstedt@intel.com>"> <span class="fn">Marta Löfstedt</span></a>
</span></b>
        <pre>"commit 7741b547b6e000b08e20667bb3bef22e1a362661
Author: Daniel Vetter <<a href="mailto:daniel.vetter@ffwll.ch">daniel.vetter@ffwll.ch</a>>
Date:   Mon Oct 9 18:44:00 2017 +0200

    drm/i915: Preallocate our mmu notifier workequeu to unbreak cpu hotplug
deadlock"

was integrated in CI_DRM_3202. From then the lockdep in 
igt@prime_mmap@test_userptr has not been reproduced. Note that this is not due
it being hidden by another lockdep, in for example:
<a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3202/shard-apl3/igt@prime_mmap@test_userptr.html">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3202/shard-apl3/igt@prime_mmap@test_userptr.html</a>
there is no lockdep either in bootlog or runtime dmesg.
The same is true for:
<a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3202/shard-kbl5/igt@gem_userptr_blits@process-exit-gtt.html">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3202/shard-kbl5/igt@gem_userptr_blits@process-exit-gtt.html</a>.
>From which I draw the conclusion that all the gem_userptr_blits lockdeps are
fixed by above commit.

However, the gem_eio lockdep is still present, see for example: 
<a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3202/shard-kbl7/igt@gem_eio@throttle.html">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3202/shard-kbl7/igt@gem_eio@throttle.html</a>.
Also, this is still present:
<a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3202/shard-hsw2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-render.html">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3202/shard-hsw2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-render.html</a>

>From this I (again) draw the conclusion that this is not a duplicate BUG
102886.</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are on the CC list for the bug.</li>
          <li>You are the QA Contact for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>