[Bug 111626] New: [CI][SHARDS] igt at perf_pmu@busy-idle-no-semaphores-bcs0 - dmesg-warn - WARNING: possible irq lock inversion dependency detected

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=111626

            Bug ID: 111626
           Summary: [CI][SHARDS]
                    igt at perf_pmu@busy-idle-no-semaphores-bcs0 - dmesg-warn
                    - WARNING: possible irq lock inversion dependency
                    detected
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: not set
          Priority: not set
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: lakshminarayana.vudum at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6847/shard-skl5/igt@perf_pmu@busy-idle-no-semaphores-bcs0.html

[IGT] perf_pmu: executing
<6> [1794.462364] [IGT] perf_pmu: starting subtest busy-idle-no-semaphores-bcs0
<4> [1795.080225] 
<4> [1795.080255] ========================================================
<4> [1795.080277] WARNING: possible irq lock inversion dependency detected
<4> [1795.080299] 5.3.0-rc7-CI-CI_DRM_6847+ #1 Tainted: G     U           
<4> [1795.080316] --------------------------------------------------------
<4> [1795.080334] kworker/0:0H/3056 just changed the state of lock:
<4> [1795.080352] 0000000062a190ff (&timeline->mutex/2){-...}, at:
__engine_park+0x3e/0x320 [i915]
<4> [1795.080638] but this lock took another, HARDIRQ-unsafe lock in the past:
<4> [1795.080655]  (&(&lock->wait_lock)->rlock){+.+.}
<4> [1795.080660] 

and interrupts could create inverse lock ordering between them.

<4> [1795.080698] 
other info that might help us debug this:
<4> [1795.080716] Chain exists of:
  &timeline->mutex/2 --> &(&timelines->lock)->rlock -->
&(&lock->wait_lock)->rlock

<4> [1795.080755]  Possible interrupt unsafe locking scenario:

<4> [1795.080774]        CPU0                    CPU1
<4> [1795.080788]        ----                    ----
<4> [1795.080802]   lock(&(&lock->wait_lock)->rlock);
<4> [1795.080819]                                local_irq_disable();
<4> [1795.080835]                                lock(&timeline->mutex/2);
<4> [1795.080855]                               
lock(&(&timelines->lock)->rlock);
<4> [1795.080876]   <Interrupt>
<4> [1795.080886]     lock(&timeline->mutex/2);
<4> [1795.080904] 
 *** DEADLOCK ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190910/6af7a8e7/attachment-0001.html>