From: "Eric Rannaud" <eric.rannaud@gmail.com>
To: "Andrew Morton" <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org,
"Linus Torvalds" <torvalds@osdl.org>,
mingo@elte.hu, nagar@watson.ibm.com
Subject: Re: BUG-lockdep and freeze (was: Arrr! Linux 2.6.18)
Date: Sun, 1 Oct 2006 00:00:45 +0200 [thread overview]
Message-ID: <5f3c152b0609301500l52a4c6c5o2052b88621dc7ca3@mail.gmail.com> (raw)
In-Reply-To: <20060930140426.37918062.akpm@osdl.org>
On 9/30/06, Andrew Morton <akpm@osdl.org> wrote:
> You could set CONFIG_UNWIND_INFO=n and CONFIG_STACK_UNWIND=n and reenable
> lockdep. That will a) tell us if there's some lockdep problem and b) will
> give us a clearer look at any locking problems which your kernel is
> detecting.
All right. Here is the stacktrace I get with config
CONFIG_UNWIND_INFO=n and CONFIG_STACK_UNWIND=n and v2.6.18 (all the
rest being equal http://engm.ath.cx/kernel/config-2.6.18). (and no
freeze)
[ 153.552157] BUG: warning at
kernel/lockdep.c:565/print_infinite_recursion_bug()
[ 153.552252]
[ 153.552253] Call Trace:
[ 153.552346] [<ffffffff8024b84d>] print_infinite_recursion_bug+0x3d/0x50
[ 153.552398] [<ffffffff8024b95f>] find_usage_backwards+0x2f/0xd0
[ 153.552447] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.552496] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.552545] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.552594] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.552643] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.552704] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.552767] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.552835] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.552896] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.552958] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.553019] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.553081] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.553145] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.553206] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.553268] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.553330] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.553392] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.553454] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.553515] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.553578] [<ffffffff8024b9c3>] find_usage_backwards+0x93/0xd0
[ 153.553643] [<ffffffff804aa97a>] trace_hardirqs_on_thunk+0x35/0x37
[ 153.553706] [<ffffffff8024c370>] check_usage+0x40/0x2b0
[ 153.553768] [<ffffffff8024dc40>] __lock_acquire+0xa50/0xd20
[ 153.553830] [<ffffffff8024de2f>] __lock_acquire+0xc3f/0xd20
[ 153.553894] [<ffffffff80227c2b>] double_rq_lock+0x2b/0x50
[ 153.553955] [<ffffffff8024e29b>] lock_acquire+0x8b/0xc0
[ 153.554016] [<ffffffff80227c2b>] double_rq_lock+0x2b/0x50
[ 153.554077] [<ffffffff804aae25>] _spin_lock+0x25/0x40
[ 153.554138] [<ffffffff80227c2b>] double_rq_lock+0x2b/0x50
[ 153.554199] [<ffffffff8022af8b>] migration_thread+0x22b/0x2e0
[ 153.554260] [<ffffffff8022ad60>] migration_thread+0x0/0x2e0
[ 153.554322] [<ffffffff80246b9a>] kthread+0xda/0x110
[ 153.554384] [<ffffffff8020aaa0>] child_rip+0xa/0x12
[ 153.554443] [<ffffffff804ab30b>] _spin_unlock_irq+0x2b/0x40
[ 153.554507] [<ffffffff8020a0dc>] restore_args+0x0/0x30
[ 153.554568] [<ffffffff80246ac0>] kthread+0x0/0x110
[ 153.554628] [<ffffffff8020aa96>] child_rip+0x0/0x12
Thanks.
er.
next prev parent reply other threads:[~2006-09-30 22:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 19:20 Eric Rannaud
2006-09-30 19:49 ` Peter Zijlstra
2006-09-30 20:23 ` Linus Torvalds
2006-09-30 20:57 ` Eric Rannaud
2006-09-30 19:54 ` Linus Torvalds
2006-09-30 20:21 ` Al Viro
2006-09-30 20:28 ` Linus Torvalds
2006-09-30 20:30 ` Andi Kleen
2006-09-30 20:47 ` Linus Torvalds
2006-09-30 20:49 ` Ingo Molnar
2006-09-30 21:11 ` Linus Torvalds
2006-09-30 21:25 ` Ingo Molnar
2006-09-30 21:57 ` Andi Kleen
2006-09-30 22:09 ` BUG-lockdep and freeze (was: Arrr! Linux 2.6.18) II Andi Kleen
2006-09-30 22:19 ` Eric Rannaud
2006-09-30 22:24 ` Andi Kleen
2006-09-30 22:54 ` BUG-lockdep and freeze (was: Arrr! Linux 2.6.18) Linus Torvalds
2006-10-04 9:21 ` Jan Beulich
2006-10-04 15:12 ` Linus Torvalds
2006-09-30 21:43 ` Eric Rannaud
2006-09-30 22:03 ` Andi Kleen
2006-09-30 21:56 ` Linus Torvalds
2006-09-30 22:02 ` Andi Kleen
2006-09-30 22:10 ` Ingo Molnar
2006-09-30 22:23 ` Andi Kleen
2006-09-30 22:55 ` Linus Torvalds
2006-09-30 22:59 ` Linus Torvalds
2006-09-30 23:56 ` Andi Kleen
2006-10-01 0:25 ` Linus Torvalds
2006-10-01 0:51 ` Linus Torvalds
2006-10-01 9:27 ` Andi Kleen
2006-10-04 9:25 ` Jan Beulich
2006-10-04 10:52 ` Andi Kleen
2006-10-04 11:58 ` Jan Beulich
2006-10-04 12:03 ` Andi Kleen
2006-10-04 12:10 ` Jan Beulich
2006-09-30 20:43 ` Linus Torvalds
2006-10-04 9:15 ` Jan Beulich
2006-09-30 20:13 ` Andrew Morton
2006-09-30 20:52 ` Eric Rannaud
2006-09-30 21:04 ` Andrew Morton
2006-09-30 22:00 ` Eric Rannaud [this message]
2006-09-30 22:05 ` Ingo Molnar
2006-10-01 0:59 ` Eric Rannaud
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=5f3c152b0609301500l52a4c6c5o2052b88621dc7ca3@mail.gmail.com \
--to=eric.rannaud@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nagar@watson.ibm.com \
--cc=torvalds@osdl.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®