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

Re: [Xen-devel] dom0 panic on xen 4.0.1-rc3

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] dom0 panic on xen 4.0.1-rc3
From: Cris Daniluk <cris.daniluk@xxxxxxxxx>
Date: Mon, 21 Jun 2010 08:42:04 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 21 Jun 2010 05:43:08 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=n3f2m0ymZhae1mnK1x7v400HxgyV7B1cSnKcTKu96kY=; b=DT0lx0umYHsopimszO6FrF9TImY9vOlLDCrTpl/mW9k9wT/kAxF53l5+g/kozLfgIv 4DM9zdqmPWClvtg99GRR5kwN5MSp1OPGBd9W63K9SUCxzC5gA0fdi4q7yRpl/eyyDQ3z o16X+lPVo/w1RtKi4XjGqszicT5n5HODTTcDQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=FS47otI/j5dNoujirJjfAf2uh//Z77Y4s3DrcN5wbwStF2L9MY37UZn2ECbyODzmca dvyJUAI9yWHnz0ffBCbTB1gY8X25Q22f4Xhc6gkTWXPstCRQ2W2adTzSzCfubLmEUgEA s0BfMHEx6apdOLioK6ZJabKb5Qmx9OfD26kEM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C1F3660.1040303@xxxxxxxx>
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: <AANLkTinn8vdKxrcn_wpXhw5um2tFPl9hZ-XubcVBXgA1@xxxxxxxxxxxxxx> <4C1F3660.1040303@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>> BUG: unable to handle kernel paging request at 0000000000005b08
>> IP: [<ffffffff810e8f05>] __alloc_pages_nodemask+0x107/0x696
>> PGD 0
>> Thread overran stack, or stack corrupted
>> Oops: 0000 [#1] SMP
>> last sysfs file:
>> CPU 0
>> Modules linked in:
>> Pid: 0, comm: swapper Not tainted 2.6.32.15 #1 PowerEdge R410
>> RIP: e030:[<ffffffff810e8f05>]  [<ffffffff810e8f05>]
>> __alloc_pages_nodemask+0x107/0x696
>>
>
> That's odd.  Could you map that to a particular line in in
> __alloc_pages_nodemask?  What's your kernel config?
>
>

I'm using a reference config at:

http://pasik.reaktio.net/xen/pv_ops-dom0-debug/config-2.6.32.15-pvops-dom0-xen-stable-x86_64

I set the processor explicitly to Intel Core+ instead of generic
x86_64 and removed some extraneous drivers such as ISDN and wireless,
but made no other changes. I also tried it with no modifications
whatsoever for good measure and had the same result.

I will run with some debugging to get the line that is occurring on.

Cris

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

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