INFO: possible recursive locking detected dev_deactivate - Kernel

This is a discussion on INFO: possible recursive locking detected dev_deactivate - Kernel ; 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, ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: INFO: possible recursive locking detected dev_deactivate

  1. INFO: possible recursive locking detected dev_deactivate

    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: [] dev_deactivate+0x82/0x150

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

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

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

    Call Trace:
    [] __lock_acquire+0xcea/0x13b0
    [] ? mark_held_locks+0x4d/0x90
    [] ? get_lock_stats+0x34/0x70
    [] ? dev_deactivate+0x82/0x150
    [] lock_acquire+0x96/0xe0
    [] ? dev_deactivate+0x82/0x150
    [] _spin_lock+0x31/0x60
    [] dev_deactivate+0x82/0x150
    [] dev_close+0x65/0xc0
    [] ieee80211_stop+0x339/0x4e0 [mac80211]
    [] dev_close+0x76/0xc0
    [] dev_change_flags+0xa1/0x1e0
    [] do_setlink+0x214/0x3a0
    [] ? sub_preempt_count+0x80/0x120
    [] ? _read_unlock+0x30/0x60
    [] rtnl_setlink+0x10d/0x150
    [] rtnetlink_rcv_msg+0x18d/0x240
    [] ? rtnetlink_rcv_msg+0x0/0x240
    [] netlink_rcv_skb+0x89/0xb0
    [] rtnetlink_rcv+0x29/0x40
    [] netlink_unicast+0x2cd/0x2e0
    [] ? __alloc_skb+0x6e/0x150
    [] netlink_sendmsg+0x204/0x300
    [] ? _read_unlock+0x4e/0x60
    [] sock_sendmsg+0x127/0x140
    [] ? autoremove_wake_function+0x0/0x40
    [] ? trace_hardirqs_on+0xd/0x10
    [] ? trace_hardirqs_on_caller+0x14b/0x1b0
    [] ? move_addr_to_kernel+0x57/0x60
    [] ? verify_iovec+0x3f/0xe0
    [] sys_sendmsg+0x189/0x320
    [] ? sys_sendto+0xfd/0x120
    [] ? d_free+0x6c/0x80
    [] ? __fput+0x171/0x1c0
    [] ? trace_hardirqs_on_caller+0x14b/0x1b0
    [] ? trace_hardirqs_on_thunk+0x3a/0x3f
    [] system_call_fastpath+0x16/0x1b

    iwl3945 0000:03:00.0: PCI INT A disabled
    --
    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/

  2. Re: INFO: possible recursive locking detected dev_deactivate


    (cc's added)

    On Tue, 29 Jul 2008 13:53:39 +0200 "Zdenek Kabelac" 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: [] dev_deactivate+0x82/0x150
    >
    > but task is already holding lock:
    > (_xmit_IEEE80211#2){-...}, at: [] dev_deactivate+0x82/0x150
    >
    > other info that might help us debug this:
    > 2 locks held by NetworkManager/2623:
    > #0: (rtnl_mutex){--..}, at: [] rtnetlink_rcv+0x1a/0x40
    > #1: (_xmit_IEEE80211#2){-...}, at: []
    > dev_deactivate+0x82/0x150
    >
    > stack backtrace:
    > Pid: 2623, comm: NetworkManager Not tainted 2.6.26 #47
    >
    > Call Trace:
    > [] __lock_acquire+0xcea/0x13b0
    > [] ? mark_held_locks+0x4d/0x90
    > [] ? get_lock_stats+0x34/0x70
    > [] ? dev_deactivate+0x82/0x150
    > [] lock_acquire+0x96/0xe0
    > [] ? dev_deactivate+0x82/0x150
    > [] _spin_lock+0x31/0x60
    > [] dev_deactivate+0x82/0x150
    > [] dev_close+0x65/0xc0
    > [] ieee80211_stop+0x339/0x4e0 [mac80211]
    > [] dev_close+0x76/0xc0
    > [] dev_change_flags+0xa1/0x1e0
    > [] do_setlink+0x214/0x3a0
    > [] ? sub_preempt_count+0x80/0x120
    > [] ? _read_unlock+0x30/0x60
    > [] rtnl_setlink+0x10d/0x150
    > [] rtnetlink_rcv_msg+0x18d/0x240
    > [] ? rtnetlink_rcv_msg+0x0/0x240
    > [] netlink_rcv_skb+0x89/0xb0
    > [] rtnetlink_rcv+0x29/0x40
    > [] netlink_unicast+0x2cd/0x2e0
    > [] ? __alloc_skb+0x6e/0x150
    > [] netlink_sendmsg+0x204/0x300
    > [] ? _read_unlock+0x4e/0x60
    > [] sock_sendmsg+0x127/0x140
    > [] ? autoremove_wake_function+0x0/0x40
    > [] ? trace_hardirqs_on+0xd/0x10
    > [] ? trace_hardirqs_on_caller+0x14b/0x1b0
    > [] ? move_addr_to_kernel+0x57/0x60
    > [] ? verify_iovec+0x3f/0xe0
    > [] sys_sendmsg+0x189/0x320
    > [] ? sys_sendto+0xfd/0x120
    > [] ? d_free+0x6c/0x80
    > [] ? __fput+0x171/0x1c0
    > [] ? trace_hardirqs_on_caller+0x14b/0x1b0
    > [] ? trace_hardirqs_on_thunk+0x3a/0x3f
    > [] system_call_fastpath+0x16/0x1b
    >
    > iwl3945 0000:03:00.0: PCI INT A disabled


    --
    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/

  3. Re: INFO: possible recursive locking detected dev_deactivate

    From: Andrew Morton
    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-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/

  4. Re: INFO: possible recursive locking detected dev_deactivate

    2008/7/30 Andrew Morton :
    >
    > (cc's added)
    >
    > On Tue, 29 Jul 2008 13:53:39 +0200 "Zdenek Kabelac" 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
    >>
    >> =============================================
    >> [ INFO: possible recursive locking detected ]
    >> 2.6.26 #47


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

    Zdenek














    >> ---------------------------------------------
    >> NetworkManager/2623 is trying to acquire lock:
    >> (_xmit_IEEE80211#2){-...}, at: [] dev_deactivate+0x82/0x150
    >>
    >> but task is already holding lock:
    >> (_xmit_IEEE80211#2){-...}, at: [] dev_deactivate+0x82/0x150
    >>
    >> other info that might help us debug this:
    >> 2 locks held by NetworkManager/2623:
    >> #0: (rtnl_mutex){--..}, at: [] rtnetlink_rcv+0x1a/0x40
    >> #1: (_xmit_IEEE80211#2){-...}, at: []
    >> dev_deactivate+0x82/0x150
    >>
    >> stack backtrace:
    >> Pid: 2623, comm: NetworkManager Not tainted 2.6.26 #47
    >>
    >> Call Trace:
    >> [] __lock_acquire+0xcea/0x13b0
    >> [] ? mark_held_locks+0x4d/0x90
    >> [] ? get_lock_stats+0x34/0x70
    >> [] ? dev_deactivate+0x82/0x150
    >> [] lock_acquire+0x96/0xe0
    >> [] ? dev_deactivate+0x82/0x150
    >> [] _spin_lock+0x31/0x60
    >> [] dev_deactivate+0x82/0x150
    >> [] dev_close+0x65/0xc0
    >> [] ieee80211_stop+0x339/0x4e0 [mac80211]
    >> [] dev_close+0x76/0xc0
    >> [] dev_change_flags+0xa1/0x1e0
    >> [] do_setlink+0x214/0x3a0
    >> [] ? sub_preempt_count+0x80/0x120
    >> [] ? _read_unlock+0x30/0x60
    >> [] rtnl_setlink+0x10d/0x150
    >> [] rtnetlink_rcv_msg+0x18d/0x240
    >> [] ? rtnetlink_rcv_msg+0x0/0x240
    >> [] netlink_rcv_skb+0x89/0xb0
    >> [] rtnetlink_rcv+0x29/0x40
    >> [] netlink_unicast+0x2cd/0x2e0
    >> [] ? __alloc_skb+0x6e/0x150
    >> [] netlink_sendmsg+0x204/0x300
    >> [] ? _read_unlock+0x4e/0x60
    >> [] sock_sendmsg+0x127/0x140
    >> [] ? autoremove_wake_function+0x0/0x40
    >> [] ? trace_hardirqs_on+0xd/0x10
    >> [] ? trace_hardirqs_on_caller+0x14b/0x1b0
    >> [] ? move_addr_to_kernel+0x57/0x60
    >> [] ? verify_iovec+0x3f/0xe0
    >> [] sys_sendmsg+0x189/0x320
    >> [] ? sys_sendto+0xfd/0x120
    >> [] ? d_free+0x6c/0x80
    >> [] ? __fput+0x171/0x1c0
    >> [] ? trace_hardirqs_on_caller+0x14b/0x1b0
    >> [] ? trace_hardirqs_on_thunk+0x3a/0x3f
    >> [] system_call_fastpath+0x16/0x1b
    >>
    >> iwl3945 0000:03:00.0: PCI INT A disabled

    >
    >

    --
    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/

+ Reply to Thread