LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linux-kernel@vger.kernel.org,
jfs-discussion@lists.sourceforge.net, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: 2.6.24-rc6: possible recursive locking detected
Date: Fri, 4 Jan 2008 00:06:47 +0100 [thread overview]
Message-ID: <200801040006.47979.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.DEB.0.999999.0801032349190.4821@sheep.housecafe.de>
[Added some CCs]
On Thursday, 3 of January 2008, Christian Kujau wrote:
> hi,
>
> a few minutes after upgrading from -rc5 to -rc6 I got:
>
> [ 1310.670986] =============================================
> [ 1310.671690] [ INFO: possible recursive locking detected ]
> [ 1310.672097] 2.6.24-rc6 #1
> [ 1310.672421] ---------------------------------------------
> [ 1310.672828] FahCore_a0.exe/3692 is trying to acquire lock:
> [ 1310.673238] (&q->lock){++..}, at: [<c011544b>] __wake_up+0x1b/0x50
> [ 1310.673869]
> [ 1310.673870] but task is already holding lock:
> [ 1310.674567] (&q->lock){++..}, at: [<c011544b>] __wake_up+0x1b/0x50
> [ 1310.675267]
> [ 1310.675268] other info that might help us debug this:
> [ 1310.675952] 5 locks held by FahCore_a0.exe/3692:
> [ 1310.676334] #0: (rcu_read_lock){..--}, at: [<c038b620>] net_rx_action+0x60/0x1b0
> [ 1310.677251] #1: (rcu_read_lock){..--}, at: [<c0388d60>] netif_receive_skb+0x100/0x470
> [ 1310.677924] #2: (rcu_read_lock){..--}, at: [<c03a7fb2>] ip_local_deliver_finish+0x32/0x210
> [ 1310.678460] #3: (clock-AF_INET){-.-?}, at: [<c038164e>] sock_def_readable+0x1e/0x80
> [ 1310.679250] #4: (&q->lock){++..}, at: [<c011544b>] __wake_up+0x1b/0x50
> [ 1310.680151]
> [ 1310.680152] stack backtrace:
> [ 1310.680772] Pid: 3692, comm: FahCore_a0.exe Not tainted 2.6.24-rc6 #1
> [ 1310.681209] [<c01038aa>] show_trace_log_lvl+0x1a/0x30
> [ 1310.681659] [<c0104322>] show_trace+0x12/0x20
> [ 1310.682085] [<c0104cba>] dump_stack+0x6a/0x70
> [ 1310.682512] [<c0138ec1>] __lock_acquire+0x971/0x10c0
> [ 1310.682961] [<c013966e>] lock_acquire+0x5e/0x80
> [ 1310.683392] [<c0419b78>] _spin_lock_irqsave+0x38/0x50
> [ 1310.683914] [<c011544b>] __wake_up+0x1b/0x50
> [ 1310.684337] [<c018e2ba>] ep_poll_safewake+0x9a/0xc0
> [ 1310.684822] [<c018f11b>] ep_poll_callback+0x8b/0xe0
> [ 1310.685265] [<c0114418>] __wake_up_common+0x48/0x70
> [ 1310.685712] [<c0115467>] __wake_up+0x37/0x50
> [ 1310.686136] [<c03816aa>] sock_def_readable+0x7a/0x80
> [ 1310.686579] [<c0381c2b>] sock_queue_rcv_skb+0xeb/0x150
> [ 1310.687028] [<c03c7d99>] udp_queue_rcv_skb+0x139/0x2a0
> [ 1310.687554] [<c03c81f1>] __udp4_lib_rcv+0x2f1/0x7e0
> [ 1310.687996] [<c03c86f2>] udp_rcv+0x12/0x20
> [ 1310.688415] [<c03a80a5>] ip_local_deliver_finish+0x125/0x210
> [ 1310.688881] [<c03a84ed>] ip_local_deliver+0x2d/0x90
> [ 1310.689323] [<c03a7d6b>] ip_rcv_finish+0xeb/0x300
> [ 1310.689760] [<c03a8425>] ip_rcv+0x195/0x230
> [ 1310.690182] [<c0388fdc>] netif_receive_skb+0x37c/0x470
> [ 1310.690632] [<c038ba39>] process_backlog+0x69/0xc0
> [ 1310.691175] [<c038b6f7>] net_rx_action+0x137/0x1b0
> [ 1310.691681] [<c011e5c2>] __do_softirq+0x52/0xb0
> [ 1310.692006] [<c0104e94>] do_softirq+0x94/0xe0
> [ 1310.692301] =======================
>
>
> This is a single CPU machine, and the box was quite busy due to disk I/O
> (load 6-8). The machine continues to run and all is well now. Even the
> application mentioned above (FahCore_a0.exe) is running fine
> ("Folding@Home", cpu bound). The binary is located on an jfs filesystem,
> which was also under heavy I/O. Can someone tell me why the backtrace
> shows so much net* stuff? There was not much net I/O...
>
> more details and .config: http://nerdbynature.de/bits/2.6.24-rc6
>
> Thanks,
> Christian.
next prev parent reply other threads:[~2008-01-03 23:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 22:58 Christian Kujau
2008-01-03 23:06 ` Rafael J. Wysocki [this message]
2008-01-04 8:30 ` Ingo Molnar
2008-01-05 7:12 ` Herbert Xu
2008-01-05 16:53 ` Peter Zijlstra
2008-01-05 17:01 ` Peter Zijlstra
2008-01-05 21:35 ` Davide Libenzi
2008-01-06 0:20 ` Christian Kujau
2008-01-07 21:35 ` Davide Libenzi
2008-01-06 21:44 ` Cyrill Gorcunov
2008-01-06 21:53 ` Cyrill Gorcunov
2008-01-07 17:22 ` Oleg Nesterov
2008-01-07 17:49 ` Oleg Nesterov
2008-01-13 16:32 ` Peter Zijlstra
2008-01-14 21:27 ` Oleg Nesterov
2008-01-30 10:34 ` hrtimers and lockdep (was: Re: 2.6.24-rc6: possible recursive locking detected) Peter Zijlstra
2008-01-30 17:36 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200801040006.47979.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=a.p.zijlstra@chello.nl \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=mingo@elte.hu \
--subject='Re: 2.6.24-rc6: possible recursive locking detected' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).