rt - BUG: bad unlock balance detected!
in [Kernel]
|
Prev: MAINTAINERS: Update Laurent Pinchart email
Next: [PATCH] i2c: cyttsp i2c touchscreen driver init submit
From: John Kacur on 12 Jul 2010 17:30 The following occurred on a tip/rt/2.6.33 kernel (last sha1 42edbcbc3240b56cf89a426cbfe9c8d9051459c4) plus two patches from John Stultz https://patchwork.kernel.org/patch/108928/ https://patchwork.kernel.org/patch/108927/ [ BUG: bad unlock balance detected! ] ------------------------------------- sirq-net-rx/5/78 is trying to release lock (&lock->lock) at: [<ffffffffa0650420>] ipt_do_table+0x8e8/0x968 [ip_tables] but there are no more locks to release! other info that might help us debug this: 3 locks held by sirq-net-rx/5/78: #0: (rcu_read_lock){......}, at: [<ffffffff8141d2ae>] rcu_read_lock+0x0/0x3a #1: (rcu_read_lock){......}, at: [<ffffffff8141d2ae>] rcu_read_lock+0x0/0x3a #2: (rcu_read_lock){......}, at: [<ffffffff81452bf7>] rcu_read_lock+0x0/0x3a stack backtrace: Pid: 78, comm: sirq-net-rx/5 Not tainted 2.6.33.5-rt23-tracing-dcachefix #1 Call Trace: [<ffffffffa0650420>] ? ipt_do_table+0x8e8/0x968 [ip_tables] [<ffffffff810a30de>] print_unlock_inbalance_bug+0xd6/0xe0 [<ffffffff810a3937>] lock_release_non_nested+0xbe/0x23b [<ffffffff810acd7c>] ? rt_spin_lock_fastunlock.clone.2+0x9b/0xc0 [<ffffffffa0650420>] ? ipt_do_table+0x8e8/0x968 [ip_tables] [<ffffffffa0650420>] ? ipt_do_table+0x8e8/0x968 [ip_tables] [<ffffffff810a41e6>] lock_release+0x17d/0x19f [<ffffffff8150eff0>] rt_spin_unlock+0x23/0x30 [<ffffffffa0650420>] ipt_do_table+0x8e8/0x968 [ip_tables] [<ffffffff8100bff3>] ? native_sched_clock+0x25/0x92 [<ffffffff81094abf>] ? sched_clock_cpu+0xdb/0x234 [<ffffffff81094c61>] ? cpu_clock+0x49/0x5c [<ffffffffa0660130>] ipt_local_in_hook+0x23/0x27 [iptable_filter] [<ffffffff81452eda>] nf_iterate+0x8a/0x10d [<ffffffff81466a31>] ? ip_local_deliver_finish+0x0/0x380 [<ffffffff81452fde>] nf_hook_slow+0x81/0x177 [<ffffffff81466a31>] ? ip_local_deliver_finish+0x0/0x380 [<ffffffff81466e0c>] nf_hook_thresh.clone.1+0x5b/0x5d [<ffffffff81466e8a>] ip_local_deliver+0x7c/0xa3 [<ffffffff814667d0>] ip_rcv_finish+0x5be/0x5e2 [<ffffffff814672c5>] ip_rcv+0x414/0x443 [<ffffffff81420984>] netif_receive_skb+0x7bf/0x7e9 [<ffffffffa02fdefb>] rtl8169_rx_interrupt+0x560/0x68c [r8169] [<ffffffffa03013f4>] rtl8169_poll+0x3c/0x23b [r8169] [<ffffffff814214ba>] net_rx_action+0x15e/0x3fc [<ffffffff8104f0ce>] ? get_parent_ip+0x11/0x6f [<ffffffff8106ae2e>] run_ksoftirqd+0x249/0x3be [<ffffffff81044b06>] ? need_resched+0x3f/0x46 [<ffffffff8106abe5>] ? run_ksoftirqd+0x0/0x3be [<ffffffff8108b816>] kthread+0xa4/0xac [<ffffffff81004594>] kernel_thread_helper+0x4/0x10 [<ffffffff815100c0>] ? restore_args+0x0/0x30 [<ffffffff8108b772>] ? kthread+0x0/0xac [<ffffffff81004590>] ? kernel_thread_helper+0x0/0x10 I've started to do a little debugging, some other info that might be useful: #0: (rcu_read_lock){......}, at: [<ffffffff8141d2ae>] ffffffff8141d2ae /home/jkacur/jk-2.6/net/core/datagram.c:230 function skb_free_datagram_locked lock_sock(sk); #2: (rcu_read_lock){......}, at: [<ffffffff81452bf7>] rcu_read_lock+0x0/0x3a ffffffff81452bf7 /home/jkacur/jk-2.6/net/netlink/af_netlink.c:878 function netlink_rcv_wake wake_up_interruptible(&nlk->wait); -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |