Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757633AbYGVTch (ORCPT ); Tue, 22 Jul 2008 15:32:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755945AbYGVTai (ORCPT ); Tue, 22 Jul 2008 15:30:38 -0400 Received: from mtiwmhc12.worldnet.att.net ([204.127.131.116]:62563 "EHLO mtiwmhc12.worldnet.att.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755519AbYGVTag (ORCPT ); Tue, 22 Jul 2008 15:30:36 -0400 Message-ID: <48863559.1090104@lwfinger.net> Date: Tue, 22 Jul 2008 14:30:33 -0500 From: Larry Finger User-Agent: Thunderbird 2.0.0.12 (X11/20071114) MIME-Version: 1.0 To: Patrick McHardy CC: David Miller , torvalds@linux-foundation.org, akpm@linux-foundation.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org Subject: Re: Kernel WARNING: at net/core/dev.c:1330 __netif_schedule+0x2c/0x98() References: <4885104A.2070201@lwfinger.net> <20080721.161517.27161039.davem@davemloft.net> <48857F74.2040406@lwfinger.net> <20080722.043220.247312412.davem@davemloft.net> <4885DA49.50703@lwfinger.net> <48860D4B.8070003@lwfinger.net> <488616C0.8070505@trash.net> <4886294C.4060905@lwfinger.net> <48862A76.8030307@trash.net> In-Reply-To: <48862A76.8030307@trash.net> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1476 Lines: 42 Patrick McHardy wrote: > Larry Finger wrote: >> Patrick McHardy wrote: >>> Larry Finger wrote: >>>> >>>> ============================================= >>>> [ INFO: possible recursive locking detected ] >>>> 2.6.26-Linus-git-05752-g93ded9b #49 >>> >>> ^^^^^^^^^^^^^^ dirty? >>> >>> This kernel is not using the patches we sent. >> >> No, but they didn't make any difference. I tried with all 3 applied, >> then backed them out one by one. That was the state when I posted before. > > Well, this is a completely different warning. > >> >> Here are the dumps with all 3 patches applied: >> >> ============================================= >> [ INFO: possible recursive locking detected ] >> 2.6.26-Linus-05752-g93ded9b-dirty #53 >> --------------------------------------------- >> b43/1997 is trying to acquire lock: >> (_xmit_IEEE80211#2){-...}, at: [] >> ieee80211_scan_completed+0x130/0x2e1 [mac80211] >> >> but task is already holding lock: >> (_xmit_IEEE80211#2){-...}, at: [] >> ieee80211_scan_completed+0x130/0x2e1 [mac80211] Sorry. After all those kernel builds I got bleary-eyed and just looked for recursive locking without any regard for the details. Larry -- 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/