From: Christophe Saout <christophe@saout.de>
To: Bryan Donlan <bdonlan@gmail.com>
Cc: Nick Piggin <npiggin@suse.de>,
linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
linux-mm@kvack.org
Subject: Re: OOPS and panic on 2.6.29-rc1 on xen-x86
Date: Thu, 15 Jan 2009 17:36:32 +0100 [thread overview]
Message-ID: <1232037392.4604.4.camel@leto.intern.saout.de> (raw)
In-Reply-To: <3e8340490901141619g3c32ebads482d1176efbd98a3@mail.gmail.com>
Am Mittwoch, den 14.01.2009, 19:19 -0500 schrieb Bryan Donlan:
> On Tue, Jan 13, 2009 at 9:59 PM, Nick Piggin <npiggin@suse.de> wrote:
> > On Mon, Jan 12, 2009 at 11:54:32PM -0500, Bryan Donlan wrote:
> >>
> >> I've bisected the bug in question, and the faulty commit appears to be:
> >> commit e97a630eb0f5b8b380fd67504de6cedebb489003
> >> Author: Nick Piggin <npiggin@suse.de>
> >> Date: Tue Jan 6 14:39:19 2009 -0800
> >>
> >> mm: vmalloc use mutex for purge
> >>
> >> The vmalloc purge lock can be a mutex so we can sleep while a purge is
> >> going on (purge involves a global kernel TLB invalidate, so it can take
> >> quite a while).
> >>
> >> Signed-off-by: Nick Piggin <npiggin@suse.de>
> >> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> >> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> >>
> >> The bug is easily reproducable by a kernel build on -j4 - it will
> >> generally OOPS and panic before the build completes.
> >> Also, I've tested it with ext3, and it still occurs, so it seems
> >> unrelated to btrfs at least :)
> >>
>
> Here's one from a config with CONFIG_DEBUG_BUGVERBOSE:
>
> ------------[ cut here ]------------
> kernel BUG at /root/linux-2.6/arch/x86/include/asm/mmu_context_32.h:39!
For the record, I was getting the same bug on x86_64:
(in mmu_context_64.h):
...
#ifdef CONFIG_SMP
else {
write_pda(mmu_state, TLBSTATE_OK);
if (read_pda(active_mm) != next)
BUG();
...
Christophe
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2009-01-15 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090112172613.GA8746@shion.is.fushizen.net>
2009-01-13 4:54 ` OOPS and panic on 2.6.29-rc1 on xen-x86 Bryan Donlan
2009-01-13 9:25 ` [Xen-devel] " Christophe Saout
2009-01-13 11:50 ` Ingo Molnar
2009-01-14 2:59 ` Nick Piggin
2009-01-14 21:05 ` Bryan Donlan
2009-01-15 0:19 ` Bryan Donlan
2009-01-15 16:36 ` Christophe Saout [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=1232037392.4604.4.camel@leto.intern.saout.de \
--to=christophe@saout.de \
--cc=bdonlan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).