Messages in this thread |  | | | Date | Thu, 21 Sep 2006 14:47:08 -0700 | | From | "Miles Lane" <> | | Subject | 2.6.18 -- INFO: possible recursive locking detected |
| |
============================================= [ INFO: possible recursive locking detected ] --------------------------------------------- knodemgrd_1/13913 is trying to acquire lock: (&s->rwsem){..--}, at: [<f8960817>] nodemgr_probe_ne+0x22d/0x36c [ieee1394] but task is already holding lock: (&s->rwsem){..--}, at: [<f89610d8>] nodemgr_host_thread+0x739/0x8a7 [ieee1394] other info that might help us debug this: 1 lock held by knodemgrd_1/13913: #0: (&s->rwsem){..--}, at: [<f89610d8>] nodemgr_host_thread+0x739/0x8a7 [ieee1394] stack backtrace: [<c1003ef5>] show_trace_log_lvl+0x58/0x16a [<c100506d>] show_trace+0xd/0x10 [<c1005087>] dump_stack+0x17/0x1c [<c102e485>] __lock_acquire+0x79b/0x9ef [<c102e9b6>] lock_acquire+0x5e/0x80 [<c102b73e>] down_read+0x28/0x3a [<f8960817>] nodemgr_probe_ne+0x22d/0x36c [ieee1394] [<f89610f7>] nodemgr_host_thread+0x758/0x8a7 [ieee1394] [<c1001005>] kernel_thread_helper+0x5/0xb DWARF2 unwinder stuck at kernel_thread_helper+0x5/0xb Leftover inexact backtrace: [<c100506d>] show_trace+0xd/0x10 [<c1005087>] dump_stack+0x17/0x1c [<c102e485>] __lock_acquire+0x79b/0x9ef [<c102e9b6>] lock_acquire+0x5e/0x80 [<c102b73e>] down_read+0x28/0x3a [<f8960817>] nodemgr_probe_ne+0x22d/0x36c [ieee1394] [<f89610f7>] nodemgr_host_thread+0x758/0x8a7 [ieee1394] [<c1001005>] kernel_thread_helper+0x5/0xb ieee1394: send packet at S400: ffc0a140 ffc1ffff f0000234 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |