From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 49030] New: Possible recursive locking detected in r600g
Date: Sat, 21 Apr 2012 04:23:15 +0000
Message-ID:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from annarchy.freedesktop.org (annarchy.freedesktop.org
[131.252.210.176])
by gabe.freedesktop.org (Postfix) with ESMTP id 372639E75D
for ;
Fri, 20 Apr 2012 21:23:15 -0700 (PDT)
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=49030
Bug #: 49030
Summary: Possible recursive locking detected in r600g
Classification: Unclassified
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: minor
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: alexandre.f.demers@gmail.com
Here is what I see under dmesg:
=============================================
[ INFO: possible recursive locking detected ]
3.4.0-rc3+ #120 Tainted: G C
---------------------------------------------
gnome-shell/1120 is trying to acquire lock:
(&vm->mutex){+.+...}, at: [] radeon_vm_unbind+0x24/0x40
[radeon]
but task is already holding lock:
(&vm->mutex){+.+...}, at: [] radeon_cs_ioctl+0x434/0x598
[radeon]
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&vm->mutex);
lock(&vm->mutex);
*** DEADLOCK ***
May be due to missing lock nesting notation
2 locks held by gnome-shell/1120:
#0: (&mutex->mutex){+.+.+.}, at: []
radeon_cs_ioctl+0x36/0x598 [radeon]
#1: (&vm->mutex){+.+...}, at: []
radeon_cs_ioctl+0x434/0x598 [radeon]
stack backtrace:
Pid: 1120, comm: gnome-shell Tainted: G C 3.4.0-rc3+ #120
Call Trace:
[] __lock_acquire+0xbf6/0xd11
[] ? __lock_acquire+0x4c0/0xd11
[] lock_acquire+0x92/0x104
[] ? radeon_vm_unbind+0x24/0x40 [radeon]
[] ? __lock_acquire+0x4c0/0xd11
[] __mutex_lock_common+0x48/0x34e
[] ? radeon_vm_unbind+0x24/0x40 [radeon]
[] ? radeon_vm_unbind+0x24/0x40 [radeon]
[] ? trace_hardirqs_on_caller+0x123/0x17f
[] mutex_lock_nested+0x2f/0x36
[] ? radeon_cs_ioctl+0x434/0x598 [radeon]
[] radeon_vm_unbind+0x24/0x40 [radeon]
[] radeon_vm_bind+0xb9/0x1c4 [radeon]
[] radeon_cs_ioctl+0x43f/0x598 [radeon]
[] drm_ioctl+0x2d6/0x3c0 [drm]
[] ? rcu_read_unlock+0x1c/0x1e
[] ? radeon_cs_finish_pages+0x91/0x91 [radeon]
[] ? avc_has_perm_flags+0x6b/0x7f
[] vfs_ioctl+0x24/0x2f
[] do_vfs_ioctl+0x412/0x455
[] sys_ioctl+0x56/0x7a
[] system_call_fastpath+0x1a/0x1f
It seems to be only a warning. However, if possible, it should be silenced if
there is no reason to have it. I know I reported something similar a couple of
months ago and it was fixed by moving some code around.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.