From: "Bryan Donlan" <bdonlan@gmail.com>
To: Nick Piggin <npiggin@suse.de>
Cc: 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: Wed, 14 Jan 2009 16:05:45 -0500 [thread overview]
Message-ID: <3e8340490901141305x7155cf10ueed386646d6e21ee@mail.gmail.com> (raw)
In-Reply-To: <20090114025910.GA17395@wotan.suse.de>
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:
>> On Mon, Jan 12, 2009 at 12:26 PM, Bryan Donlan <bdonlan@gmail.com> wrote:
>> > [resending with log/config inline as my previous message seems to have
>> > been eaten by vger's spam filters]
>> >
>> > Hi,
>> >
>> > After testing 2.6.29-rc1 on xen-x86 with a btrfs root filesystem, I
>> > got the OOPS quoted below and a hard freeze shortly after boot.
>> > Boot messages and config are attached.
>> >
>> > This is on a test system, so I'd be happy to test any patches.
>> >
>> > Thanks,
>> >
>> > Bryan Donlan
>>
>> 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 :)
>>
>> >
>> > ------------[ cut here ]------------
>> > Kernel BUG at c05ef80d [verbose debug info unavailable]
>> > invalid opcode: 0000 [#1] SMP
>> > last sysfs file: /sys/block/xvdc/size
>> > Modules linked in:
>
> It is bugging in schedule somehow, but you don't have verbose debug
> info compiled in. Can you compile that in and reproduce if you have
> the time?
Sure - which config option would that be? CONFIG_DEBUG_BUGVERBOSE?
> Going bug here might indicate that there is some other problem with
> the Xen and/or vmalloc code, regardless of reverting this patch.
>
> Thanks,
> Nick
>
--
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>
next prev parent reply other threads:[~2009-01-14 21:05 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 [this message]
2009-01-15 0:19 ` Bryan Donlan
2009-01-15 16:36 ` Christophe Saout
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=3e8340490901141305x7155cf10ueed386646d6e21ee@mail.gmail.com \
--to=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).