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 crash with unstable

To: "Bryan D. Payne" <bryan@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] dom0 crash with unstable
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 06 Oct 2009 10:54:42 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 06 Oct 2009 10:55:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <64bddf0e0910061023t58828929i99da6a63155e82c@xxxxxxxxxxxxxx>
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: <64bddf0e0909301105l18c6a3f6ie59af261b1532fe2@xxxxxxxxxxxxxx> <4AC3EE07.3010000@xxxxxxxx> <64bddf0e0910010635wc085961tf55000d4305da2bf@xxxxxxxxxxxxxx> <4AC518A1.8080905@xxxxxxxx> <64bddf0e0910060813v2f2d4149wf2898653719d6ba3@xxxxxxxxxxxxxx> <4ACB70F0.5020502@xxxxxxxx> <64bddf0e0910061023t58828929i99da6a63155e82c@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3
On 10/06/09 10:23, Bryan D. Payne wrote:
>> Is it ever stable?  What happens if you set dom0_mem to 4G or less?
>>     
> It still crashes, even with 2G of dom0 memory.
>   

What console output do you get?

>> Is the console responsive when the kernel hangs?  That is, can you type
>> "Ctrl-A Ctrl-A Ctrl-A" to get Xen, then enter debug keys?  '0' (zero)
>> should dump the context for dom0 and give some clue about where it is dying.
>>     
> Yes, this seems to work.  Typing 0 dumped info for each of the cores
> (i.e., 15 vcpu states).  I've attached the output.
>   

Could you map the RIP values to a symbol with gdb?  From a quick look,
it seems that most or all of the cpus are at the same place.  No, vcpu 8
is doing something else at least.

What happens if you boot dom0 with fewer cpus?

Do you have CONFIG_PARAVIRT_SPINLOCKS enabled?

    J

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