Messages in this thread | | | Date | Sat, 1 Jul 2006 18:04:30 -0700 | From | "Miles Lane" <> | Subject | 2.6.17-mm4 + hostap + pcmcia + lockdep -- possible recursive locking detected -- (af_callback_keys + sk->sk_family#3){-.-?}, at: [<c119d8db>] sock_def_readable+0x15/0x69 |
| |
I have patches for hostap, pcmcia and lockdep applied to this kernel. These patches are the ones resulting from several recent message threads. I just noticed this in my kernel log:
[ INFO: possible recursive locking detected ] --------------------------------------------- multiload-apple/2820 is trying to acquire lock: (af_callback_keys + sk->sk_family#3){-.-?}, at: [<c119d8db>] sock_def_readable+0x15/0x69
but task is already holding lock: (af_callback_keys + sk->sk_family#3){-.-?}, at: [<c119d8db>] sock_def_readable+0x15/0x69
other info that might help us debug this: 3 locks held by multiload-apple/2820: #0: (rtnl_mutex){--..}, at: [<c120028e>] mutex_lock+0x1c/0x1f #1: (af_callback_keys + sk->sk_family#3){-.-?}, at: [<c119d8db>] sock_def_readable+0x15/0x69 #2: (&priv->lock){.+..}, at: [<f90472c9>] ipw_irq_tasklet+0x54/0x10c1 [ipw2200]
stack backtrace: [<c1003502>] show_trace_log_lvl+0x54/0xfd [<c1003b6a>] show_trace+0xd/0x10 [<c1003c0e>] dump_stack+0x19/0x1b [<c102ccd6>] __lock_acquire+0x755/0x970 [<c102d1b6>] lock_acquire+0x60/0x80 [<c1201533>] _read_lock+0x23/0x32 [<c119d8db>] sock_def_readable+0x15/0x69 [<c11b5621>] netlink_broadcast+0x1c6/0x2b8 [<c11ad712>] wireless_send_event+0x28a/0x29c [<f9047d02>] ipw_irq_tasklet+0xa8d/0x10c1 [ipw2200] [<c101a4e7>] tasklet_action+0x45/0x76 [<c101a709>] __do_softirq+0x55/0xb0 [<c1004a64>] do_softirq+0x58/0xbd [<c101a6a8>] irq_exit+0x3f/0x4b [<c1004b89>] do_IRQ+0xc0/0xcf [<c1002fd9>] common_interrupt+0x25/0x2c - 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/
| |