Red Hat Bugzilla – Bug 229192
possible recursive locking detected on boot up
Last modified: 2007-11-30 17:11:57 EST
Description of problem: I'm seeing the following on every bootup: ============================================= [ INFO: possible recursive locking detected ] 2.6.20-1.2932.fc7 #1 --------------------------------------------- init/1 is trying to acquire lock: (&bdev->bd_mutex){--..}, at: [<ffffffff80263385>] mutex_lock+0x2a/0x2e but task is already holding lock: (&bdev->bd_mutex){--..}, at: [<ffffffff80263385>] mutex_lock+0x2a/0x2e other info that might help us debug this: 1 lock held by init/1: #0: (&bdev->bd_mutex){--..}, at: [<ffffffff80263385>] mutex_lock+0x2a/0x2e stack backtrace: Call Trace: [<ffffffff802a4698>] __lock_acquire+0x151/0xbc4 [<ffffffff802a5501>] lock_acquire+0x4c/0x65 [<ffffffff80263385>] mutex_lock+0x2a/0x2e [<ffffffff802631c1>] __mutex_lock_slowpath+0xff/0x299 [<ffffffff802df266>] get_super+0x9e/0xa9 [<ffffffff80263385>] mutex_lock+0x2a/0x2e [<ffffffff8033f9ba>] blkdev_ioctl+0x574/0x6ba [<ffffffff802f220c>] block_ioctl+0x1b/0x1f [<ffffffff80242aad>] do_ioctl+0x2a/0x77 [<ffffffff802308d1>] vfs_ioctl+0x260/0x27d [<ffffffff80264599>] trace_hardirqs_on_thunk+0x35/0x37 [<ffffffff8024d1d8>] sys_ioctl+0x5f/0x82 [<ffffffff80248532>] set_close_on_exec+0x30/0x85 [<ffffffff8025d11e>] system_call+0x7e/0x83 Version-Release number of selected component (if applicable): kernel-2.6.20-1.2932.fc7 How reproducible: 100%
No longer relevant, closing