Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761069AbYG3KBw (ORCPT ); Wed, 30 Jul 2008 06:01:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756632AbYG3KBk (ORCPT ); Wed, 30 Jul 2008 06:01:40 -0400 Received: from po-out-1718.google.com ([72.14.252.157]:16702 "EHLO po-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755789AbYG3KBi (ORCPT ); Wed, 30 Jul 2008 06:01:38 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=wqb8FeAAokrFrPDsMF+I5yWJmA8R3KDlyozxjl8ZTJHOeSqN6xb6r3SXrthpjNdDPP AfP+QnMFuNb/+s/ZPUy/XaRdfyLVSQPUALOgehgvH22OckNFcHxS019kqrCJ3Mg4Umm3 /yyl1IBpDg6QoLdiAe4tNLpHWK/ZjIGO1NH9I= Message-ID: Date: Wed, 30 Jul 2008 12:01:37 +0200 From: "Zdenek Kabelac" To: "Andrew Morton" Subject: Re: INFO: possible recursive locking detected dev_deactivate Cc: "Linux Kernel Mailing List" , linux-wireless@vger.kernel.org, netdev@vger.kernel.org In-Reply-To: <20080730024724.519f0662.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080730024724.519f0662.akpm@linux-foundation.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3560 Lines: 100 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/