From: Andrew Morton <akpm@osdl.org>
To: Martin Bligh <mbligh@mbligh.org>
Cc: linux-kernel@vger.kernel.org, apw@shadowen.org
Subject: Re: 2.6.17-rc5-mm1 panic on p-series
Date: Wed, 31 May 2006 14:06:21 -0700 [thread overview]
Message-ID: <20060531140621.2dabe7fb.akpm@osdl.org> (raw)
In-Reply-To: <447DEE53.2010301@mbligh.org>
Martin Bligh <mbligh@mbligh.org> wrote:
>
> Get a different panic on -mm1 from mainline (and much
> earlier)
>
> http://test.kernel.org/abat/33808/debug/console.log
>
> Badness in local_bh_disable at kernel/softirq.c:86
That's a WARN_ON which should be removed.
--- devel/kernel/softirq.c~lock-validator-irqtrace-core-remove-softirqc-warn_on 2006-05-30 14:35:53.000000000 -0700
+++ devel-akpm/kernel/softirq.c 2006-05-30 14:35:53.000000000 -0700
@@ -83,7 +83,6 @@ static void __local_bh_disable(unsigned
void local_bh_disable(void)
{
- WARN_ON_ONCE(irqs_disabled());
__local_bh_disable((unsigned long)__builtin_return_address(0));
}
> Call Trace:
> [C00000000051F280] [C00000000000EEC8] .show_stack+0x74/0x1b4 (unreliable)
> [C00000000051F330] [C000000000338664] .program_check_exception+0x1f4/0x65c
> [C00000000051F410] [C0000000000044EC] program_check_common+0xec/0x100
> --- Exception: 700 at .local_bh_disable+0x34/0x4c
But what's up with that? Does it mean that local_bh_disable() went BUG(),
or what?
> LR = .do_softirq+0x64/0xd0
> [C00000000051F790] [C000000000063B64] .irq_exit+0x64/0x7c
> [C00000000051F810] [C0000000000228E0] .timer_interrupt+0x464/0x48c
> [C00000000051F8E0] [C0000000000034EC] decrementer_common+0xec/0x100
> --- Exception: 901 at .memset+0x80/0xfc
> LR = .__alloc_bootmem_core+0x39c/0x3dc
> [C00000000051FBD0] [C0000000004460E8] 0xc0000000004460e8 (unreliable)
> [C00000000051FC90] [C0000000003D51B0] .__alloc_bootmem_nopanic+0x44/0xb0
> [C00000000051FD30] [C0000000003D523C] .__alloc_bootmem+0x20/0x5c
> [C00000000051FDB0] [C0000000003D6124] .alloc_large_system_hash+0x130/0x268
> [C00000000051FE70] [C0000000003D78D4] .vfs_caches_init_early+0x5c/0xd4
> [C00000000051FEF0] [C0000000003BD718] .start_kernel+0x220/0x320
> [C00000000051FF90] [C000000000008594] .start_here_common+0x88/0x8c
I don't know if this is a consequence of earlier happenings or a
consequence of Andy ;)
prev parent reply other threads:[~2006-05-31 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-31 19:28 2.6.17-rc5-mm1 panic on p-series Martin Bligh
2006-05-31 21:06 ` Andrew Morton [this message]
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=20060531140621.2dabe7fb.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.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