This I got during boot with 2.6.20-rc4:
=============================================
[ INFO: possible recursive locking detected ]
2.6.20-rc4 #3
---------------------------------------------
mount/5819 is trying to acquire lock:
(&jfs_ip->commit_mutex){--..}, at: [<c03395e1>] mutex_lock+0x21/0x30
but task is already holding lock:
(&jfs_ip->commit_mutex){--..}, at: [<c03395e1>] mutex_lock+0x21/0x30
other info that might help us debug this:
2 locks held by mount/5819:
#0: (&inode->i_mutex){--..}, at: [<c03395e1>] mutex_lock+0x21/0x30
#1: (&jfs_ip->commit_mutex){--..}, at: [<c03395e1>] mutex_lock+0x21/0x30
stack backtrace:
[<c010375a>] show_trace_log_lvl+0x1a/0x30
[<c0103e62>] show_trace+0x12/0x20
[<c0103f16>] dump_stack+0x16/0x20
[<c0135e98>] __lock_acquire+0xa38/0xe00
[<c01362cf>] lock_acquire+0x6f/0x90
[<c033939a>] __mutex_lock_slowpath+0x6a/0x290
[<c03395e1>] mutex_lock+0x21/0x30
[<c01d64b0>] jfs_create+0x90/0x350
[<c0169489>] vfs_create+0xa9/0xf0
[<c016c5f7>] open_namei+0x5d7/0x630
[<c01602fc>] do_filp_open+0x2c/0x60
[<c0160377>] do_sys_open+0x47/0xe0
[<c016044c>] sys_open+0x1c/0x20
[<c0102f8e>] sysenter_past_esp+0x5f/0x99
=======================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
