WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: OOPS and panic on 2.6.29-rc1 on xen-x86

To: "Nick Piggin" <npiggin@xxxxxxx>
Subject: [Xen-devel] Re: OOPS and panic on 2.6.29-rc1 on xen-x86
From: "Bryan Donlan" <bdonlan@xxxxxxxxx>
Date: Wed, 14 Jan 2009 16:05:45 -0500
Cc: linux-mm@xxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
Delivery-date: Wed, 14 Jan 2009 13:06:12 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=lYUB3tgoWpEghK0Sx9e0m/ZqvxVaDwMijtgm/Y65KbY=; b=KAac0T2xXgkluOp+XtnXFO130Rb8Hpan/IDyW92C3B2dRe6U2O52N4j5LhwK3YJFQR RI3VwbGi+L3mQYw2hfAp8WQoQYOTiML/uRYb4H0nIYDXVZVufeVYv/jnEk1wdo2boIsU /k4Dg/zjKKuPCKdD2vOyo7S7j/XmeXoodXX9k=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=lX36draEbFC7wZyT3lZURBGX4PAFraG1+LK0AcI+cv8H6aroCZaX5L+WQPNDpWIVrB yB9OCAPj+3b8OanQZsZ9QqQtPWcisze/zEWJxpe+E+Fo120m2i/8afh6Lff4l+FK/p5h P8EljdfpuXfltoQajZqYQtRVYkT0LMMPzlSgw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20090114025910.GA17395@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20090112172613.GA8746@xxxxxxxxxxxxxxxxxxxxx> <3e8340490901122054q4af2b4cm3303c361477defc0@xxxxxxxxxxxxxx> <20090114025910.GA17395@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, Jan 13, 2009 at 9:59 PM, Nick Piggin <npiggin@xxxxxxx> 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@xxxxxxxxx> 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@xxxxxxx>
>> 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@xxxxxxx>
>>     Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
>>     Signed-off-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
>>
>> 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
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>