[Bug 89304] New: Recursive locking warning with Linux v3.19-8784-gb2b89ebfc0f0

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Feb 24 10:54:29 PST 2015


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

            Bug ID: 89304
           Summary: Recursive locking warning with Linux
                    v3.19-8784-gb2b89ebfc0f0
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: jwboyer at fedoraproject.org
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

We got the following lockdep report with Linux v3.19-8794-gb2b89ebfc0f0 (right
before 4.0-rc1).  This might be optimus related?

[ INFO: possible recursive locking detected ]
3.20.0-0.rc0.git9.1.fc22.x86_64 #1 Not tainted
---------------------------------------------
Xorg/1484 is trying to acquire lock:
 (&dev->struct_mutex){+.+.+.}, at: [<ffffffffa013fac9>]
i915_gem_unmap_dma_buf+0x39/0x110 [i915]

but task is already holding lock:
 (&dev->struct_mutex){+.+.+.}, at: [<ffffffffa002eb12>]
drm_gem_object_handle_unreference_unlocked+0xc2/0x130 [drm]

other info that might help us debug this:
 Possible unsafe locking scenario:

       CPU0
       ----
  lock(&dev->struct_mutex);
  lock(&dev->struct_mutex);

 *** DEADLOCK ***

 May be due to missing lock nesting notation

1 lock held by Xorg/1484:
 #0:  (&dev->struct_mutex){+.+.+.}, at: [<ffffffffa002eb12>]
drm_gem_object_handle_unreference_unlocked+0xc2/0x130 [drm]

stack backtrace:
CPU: 0 PID: 1484 Comm: Xorg Not tainted 3.20.0-0.rc0.git9.1.fc22.x86_64 #1
Hardware name: ASUSTeK COMPUTER INC. U32VJ/U32VJ, BIOS U32VJ.201 08/29/2012
 0000000000000000 000000002dfdbeed ffff8800b67779d8 ffffffff818773cd
 0000000000000000 ffffffff82bdbaf0 ffff8800b6777ad8 ffffffff811091c9
 00000000b6777ae8 ffff88012a003fc0 ffff880128f90000 0000000000000000
Call Trace:
 [<ffffffff818773cd>] dump_stack+0x4c/0x65
 [<ffffffff811091c9>] __lock_acquire+0x1bb9/0x1e20
 [<ffffffff8102f6ef>] ? save_stack_trace+0x2f/0x50
 [<ffffffff81109df7>] lock_acquire+0xc7/0x2a0
 [<ffffffffa013fac9>] ? i915_gem_unmap_dma_buf+0x39/0x110 [i915]
 [<ffffffff8187c02d>] mutex_lock_nested+0x7d/0x450
 [<ffffffffa013fac9>] ? i915_gem_unmap_dma_buf+0x39/0x110 [i915]
 [<ffffffffa013fac9>] ? i915_gem_unmap_dma_buf+0x39/0x110 [i915]
 [<ffffffffa013fac9>] i915_gem_unmap_dma_buf+0x39/0x110 [i915]
 [<ffffffff815ab2e5>] dma_buf_unmap_attachment+0x55/0x80
 [<ffffffffa0049592>] drm_prime_gem_destroy+0x22/0x40 [drm]
 [<ffffffffa0306461>] nouveau_gem_object_del+0x81/0xf0 [nouveau]
 [<ffffffffa002e5b7>] drm_gem_object_free+0x27/0x40 [drm]
 [<ffffffffa002eb30>] drm_gem_object_handle_unreference_unlocked+0xe0/0x130
[drm]
 [<ffffffffa002ec51>] drm_gem_handle_delete+0xd1/0x150 [drm]
 [<ffffffffa002f3c0>] drm_gem_close_ioctl+0x20/0x30 [drm]
 [<ffffffffa002fdab>] drm_ioctl+0x1db/0x640 [drm]
 [<ffffffff8110385f>] ? lock_release_holdtime.part.29+0xf/0x200
 [<ffffffff811071ad>] ? trace_hardirqs_on_caller+0x13d/0x1e0
 [<ffffffff8110725d>] ? trace_hardirqs_on+0xd/0x10
 [<ffffffffa02fdc62>] nouveau_drm_ioctl+0x72/0xd0 [nouveau]
 [<ffffffff8128c9a8>] do_vfs_ioctl+0x2e8/0x530
 [<ffffffff8128cc71>] SyS_ioctl+0x81/0xa0
 [<ffffffff81880969>] system_call_fastpath+0x12/0x17

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1194742

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


More information about the intel-gfx-bugs mailing list