Re: INFO: possible recursive locking detected dev_deactivate

(cc's added)

On Tue, 29 Jul 2008 13:53:39 +0200 "Zdenek Kabelac" [off-list ref] wrote:

Hi

With kernel from yesterdays' git (08/07/28) (sorry I've already
deleted any traces for more precise commit number) - I've just found
the bactrace in the log running already today's 2.6.27-rc1.

Happened during the reboot of 2.6.26
As usually T61, 2GB, C2D

(wlan0): now unmanaged
(wlan0): device state change: 3 -> 1
(wlan0): cleaning up...
(wlan0): taking down device.

=============================================
[ INFO: possible recursive locking detected ]
2.6.26 #47
---------------------------------------------
NetworkManager/2623 is trying to acquire lock:
 (_xmit_IEEE80211#2){-...}, at: [<ffffffff812a3cd2>] dev_deactivate+0x82/0x150

but task is already holding lock:
 (_xmit_IEEE80211#2){-...}, at: [<ffffffff812a3cd2>] dev_deactivate+0x82/0x150

other info that might help us debug this:
2 locks held by NetworkManager/2623:
 #0:  (rtnl_mutex){--..}, at: [<ffffffff8129ca0a>] rtnetlink_rcv+0x1a/0x40
 #1:  (_xmit_IEEE80211#2){-...}, at: [<ffffffff812a3cd2>]
dev_deactivate+0x82/0x150

stack backtrace:
Pid: 2623, comm: NetworkManager Not tainted 2.6.26 #47

Call Trace:
 [<ffffffff81068b4a>] __lock_acquire+0xcea/0x13b0
 [<ffffffff810674fd>] ? mark_held_locks+0x4d/0x90
 [<ffffffff810657a4>] ? get_lock_stats+0x34/0x70
 [<ffffffff812a3cd2>] ? dev_deactivate+0x82/0x150
 [<ffffffff810692a6>] lock_acquire+0x96/0xe0
 [<ffffffff812a3cd2>] ? dev_deactivate+0x82/0x150

33 more quoted lines

2008/7/30 Andrew Morton [off-list ref]:

(cc's added)

On Tue, 29 Jul 2008 13:53:39 +0200 "Zdenek Kabelac" [off-list ref] wrote:

quoted

Hi

With kernel from yesterdays' git (08/07/28) (sorry I've already
deleted any traces for more precise commit number) - I've just found
the bactrace in the log running already today's 2.6.27-rc1.

Happened during the reboot of 2.6.26
As usually T61, 2GB, C2D

=============================================
[ INFO: possible recursive locking detected ]
2.6.26 #47

Update - happens with 2.6.27-rc1 (commit:
6e86841d05f371b5b9b86ce76c02aaee83352298)

Zdenek

quoted

---------------------------------------------
NetworkManager/2623 is trying to acquire lock:
 (_xmit_IEEE80211#2){-...}, at: [<ffffffff812a3cd2>] dev_deactivate+0x82/0x150

but task is already holding lock:
 (_xmit_IEEE80211#2){-...}, at: [<ffffffff812a3cd2>] dev_deactivate+0x82/0x150

other info that might help us debug this:
2 locks held by NetworkManager/2623:
 #0:  (rtnl_mutex){--..}, at: [<ffffffff8129ca0a>] rtnetlink_rcv+0x1a/0x40
 #1:  (_xmit_IEEE80211#2){-...}, at: [<ffffffff812a3cd2>]
dev_deactivate+0x82/0x150

stack backtrace:
Pid: 2623, comm: NetworkManager Not tainted 2.6.26 #47

Call Trace:
 [<ffffffff81068b4a>] __lock_acquire+0xcea/0x13b0
 [<ffffffff810674fd>] ? mark_held_locks+0x4d/0x90
 [<ffffffff810657a4>] ? get_lock_stats+0x34/0x70
 [<ffffffff812a3cd2>] ? dev_deactivate+0x82/0x150
 [<ffffffff810692a6>] lock_acquire+0x96/0xe0
 [<ffffffff812a3cd2>] ? dev_deactivate+0x82/0x150
 [<ffffffff81315161>] _spin_lock+0x31/0x60
 [<ffffffff812a3cd2>] dev_deactivate+0x82/0x150
 [<ffffffff81292885>] dev_close+0x65/0xc0
 [<ffffffffa013a9d9>] ieee80211_stop+0x339/0x4e0 [mac80211]
 [<ffffffff81292896>] dev_close+0x76/0xc0
 [<ffffffff81292461>] dev_change_flags+0xa1/0x1e0
 [<ffffffff8129b774>] do_setlink+0x214/0x3a0
 [<ffffffff81318c60>] ? sub_preempt_count+0x80/0x120
 [<ffffffff81314e40>] ? _read_unlock+0x30/0x60
 [<ffffffff8129bacd>] rtnl_setlink+0x10d/0x150
 [<ffffffff8129cbbd>] rtnetlink_rcv_msg+0x18d/0x240
 [<ffffffff8129ca30>] ? rtnetlink_rcv_msg+0x0/0x240
 [<ffffffff812a77e9>] netlink_rcv_skb+0x89/0xb0
 [<ffffffff8129ca19>] rtnetlink_rcv+0x29/0x40
 [<ffffffff812a720d>] netlink_unicast+0x2cd/0x2e0
 [<ffffffff8128b01e>] ? __alloc_skb+0x6e/0x150
 [<ffffffff812a7424>] netlink_sendmsg+0x204/0x300

18 more quoted lines

From: Andrew Morton <redacted>
Date: Wed, 30 Jul 2008 02:47:24 -0700

(cc's added)

Well known problem and one that is being worked on.

The warnings are harmless, please ignore them for now.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html