Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751074AbWI3HEN (ORCPT ); Sat, 30 Sep 2006 03:04:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751092AbWI3HEN (ORCPT ); Sat, 30 Sep 2006 03:04:13 -0400 Received: from smtp103.plus.mail.re2.yahoo.com ([206.190.53.28]:19296 "HELO smtp103.plus.mail.re2.yahoo.com") by vger.kernel.org with SMTP id S1751074AbWI3HEM convert rfc822-to-8bit (ORCPT ); Sat, 30 Sep 2006 03:04:12 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.de; h=Received:Received:Date:From:To:Cc:Subject:Message-ID:Reply-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:User-Agent:Content-Transfer-Encoding; b=0/hNxWitRYVUc4oPQRBJJyrKW6WLH2mRr86m01imxUkwYJzag+fWS4aIr07LezOx8IxcJlN66lR1flj9QNEJoWpV/2gPKgiu0JrmgNC5SCEa1HQAbuNvbxUGLuQwnsu/FBkWzneBXGGQEVtPbFqWzgNbV2tXAAtss6rDxhEQXQ8= ; Date: Sat, 30 Sep 2006 09:04:06 +0200 From: Borislav Petkov To: Andrew Morton Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.18-mm2 - possible recursive locking detected Message-ID: <20060930070406.GA7090@gollum.tnic> Reply-To: petkov@math.uni-muenster.de References: <20060928014623.ccc9b885.akpm@osdl.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20060928014623.ccc9b885.akpm@osdl.org> User-Agent: Mutt/1.5.13 (2006-08-11) Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 4977 Lines: 76 On Thu, Sep 28, 2006 at 01:46:23AM -0700, Andrew Morton wrote: Hi, .config is at http://tim.dnsalias.org/2.6.18-mm2.cfg. Sep 30 08:38:17 zmei kernel: [ 285.197902] Sep 30 08:38:19 zmei kernel: [ 285.197905] ============================================= Sep 30 08:38:19 zmei kernel: [ 285.204776] [ INFO: possible recursive locking detected ] Sep 30 08:38:19 zmei kernel: [ 285.210163] 2.6.18-mm2 #1 Sep 30 08:38:19 zmei kernel: [ 285.212782] --------------------------------------------- Sep 30 08:38:19 zmei kernel: [ 285.218168] swapper/0 is trying to acquire lock: Sep 30 08:38:19 zmei kernel: [ 285.222777] (&q->lock){++..}, at: [] __wake_up+0x15/0x3b Sep 30 08:38:19 zmei kernel: [ 285.229114] Sep 30 08:38:19 zmei kernel: [ 285.229115] but task is already holding lock: Sep 30 08:38:19 zmei kernel: [ 285.234952] (&q->lock){++..}, at: [] __wake_up+0x15/0x3b Sep 30 08:38:19 zmei kernel: [ 285.241290] Sep 30 08:38:19 zmei kernel: [ 285.241291] other info that might help us debug this: Sep 30 08:38:19 zmei kernel: [ 285.247817] 4 locks held by swapper/0: Sep 30 08:38:19 zmei kernel: [ 285.251561] #0: (&tp->rx_lock){-+..}, at: [] rtl8139_poll+0x42/0x405 Sep 30 08:38:19 zmei kernel: [ 285.259041] #1: (slock-AF_INET/1){-+..}, at: [] tcp_v4_rcv+0x3fa/0x8eb Sep 30 08:38:19 zmei kernel: [ 285.266700] #2: (af_callback_keys + sk->sk_family#3){-.-?}, at: [] sock_def_readable+0x15/0x69 Sep 30 08:38:19 zmei kernel: [ 285.276454] #3: (&q->lock){++..}, at: [] __wake_up+0x15/0x3b Sep 30 08:38:19 zmei kernel: [ 285.283241] Sep 30 08:38:19 zmei kernel: [ 285.283242] stack backtrace: Sep 30 08:38:19 zmei kernel: [ 285.287688] [] dump_trace+0x64/0x1cd Sep 30 08:38:19 zmei kernel: [ 285.292243] [] show_trace_log_lvl+0x12/0x25 Sep 30 08:38:19 zmei kernel: [ 285.297405] [] show_trace+0xd/0x10 Sep 30 08:38:19 zmei kernel: [ 285.301780] [] dump_stack+0x19/0x1b Sep 30 08:38:19 zmei kernel: [ 285.306250] [] __lock_acquire+0x750/0x96c Sep 30 08:38:19 zmei kernel: [ 285.311304] [] lock_acquire+0x4b/0x6b Sep 30 08:38:19 zmei kernel: [ 285.316005] [] _spin_lock_irqsave+0x2c/0x3c Sep 30 08:38:19 zmei kernel: [ 285.321233] [] __wake_up+0x15/0x3b Sep 30 08:38:19 zmei kernel: [ 285.325638] [] ep_poll_safewake+0x91/0xc3 Sep 30 08:38:19 zmei kernel: [ 285.330760] [] ep_poll_callback+0x83/0x8e Sep 30 08:38:19 zmei kernel: [ 285.335888] [] __wake_up_common+0x2f/0x53 Sep 30 08:38:19 zmei kernel: [ 285.340898] [] __wake_up+0x28/0x3b Sep 30 08:38:19 zmei kernel: [ 285.345312] [] sock_def_readable+0x3a/0x69 Sep 30 08:38:20 zmei kernel: [ 285.350778] [] tcp_data_queue+0x50f/0xa53 Sep 30 08:38:20 zmei kernel: [ 285.356232] [] tcp_rcv_established+0x5aa/0x64f Sep 30 08:38:20 zmei kernel: [ 285.362077] [] tcp_v4_do_rcv+0x26/0x2f2 Sep 30 08:38:20 zmei kernel: [ 285.367322] [] tcp_v4_rcv+0x87b/0x8eb Sep 30 08:38:20 zmei kernel: [ 285.372432] [] ip_local_deliver+0x19c/0x265 Sep 30 08:38:20 zmei kernel: [ 285.378033] [] ip_rcv+0x453/0x48f Sep 30 08:38:20 zmei kernel: [ 285.382769] [] netif_receive_skb+0x1a6/0x239 Sep 30 08:38:20 zmei kernel: [ 285.388440] [] rtl8139_poll+0x297/0x405 Sep 30 08:38:20 zmei kernel: [ 285.393553] [] net_rx_action+0x76/0x109 Sep 30 08:38:20 zmei kernel: [ 285.398782] [] __do_softirq+0x70/0xf0 Sep 30 08:38:20 zmei kernel: [ 285.403459] [] do_softirq+0x39/0x55 Sep 30 08:38:20 zmei kernel: [ 285.407963] [] irq_exit+0x49/0x56 Sep 30 08:38:20 zmei kernel: [ 285.412295] [] do_IRQ+0x8f/0x9c Sep 30 08:38:20 zmei kernel: [ 285.416408] [] common_interrupt+0x25/0x2c Sep 30 08:38:20 zmei kernel: [ 285.421393] DWARF2 unwinder stuck at common_interrupt+0x25/0x2c Sep 30 08:38:20 zmei kernel: [ 285.427298] Sep 30 08:38:20 zmei kernel: [ 285.428786] Leftover inexact backtrace: Sep 30 08:38:20 zmei kernel: [ 285.428787] Sep 30 08:38:20 zmei kernel: [ 285.434103] [] cpu_idle+0x72/0x9b Sep 30 08:38:20 zmei kernel: [ 285.438383] [] rest_init+0x37/0x39 Sep 30 08:38:20 zmei kernel: [ 285.442742] [] start_kernel+0x356/0x35e Sep 30 08:38:20 zmei kernel: [ 285.447549] [<00000000>] 0x0 Sep 30 08:38:20 zmei kernel: [ 285.450541] ======================= -- Regards/Gru?, Boris. ___________________________________________________________ Der fr?he Vogel f?ngt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de - 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/