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: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] dom0 crash with unstable
From: "Bryan D. Payne" <bryan@xxxxxxxxxxxx>
Date: Tue, 6 Oct 2009 14:25:11 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 06 Oct 2009 11:25:35 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=zSmfI1m6+85HkW3tgASPTYt/YPTwHuN0CTBlfHvmD4M=; b=T7CFMKkkPmlm8OYVs6s/u+OwFH8INOMhvkLQQsNYeBs4bmJSXObUJO8FShWJ4CUz69 bSpgYvaQsbvCA9fGPzHgaGQnTA0RfMDo1QlTyPM3XpC5I1zdkoyunpO18R47K1VyMtdX SrLlIsnAM9wMXDozBSI2clRgWpyFhGnqF5gf4=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=HtyMMCyOdk+GenQ0sVXPMS7umzf2nKYg7C2OqHFIVTzA9CYa7gS3JyvtlDmLb/+5DD uImaV2RMMlB/AKGQK838K+D+VHU6l8As5qgJEcdn8s7NzG01XmW7qJefFaFqoND42qYq bM03eU4kpjF1OkeQs1JrxI51mtrjtD8MllOpw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4ACB8462.1040102@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: <64bddf0e0909301105l18c6a3f6ie59af261b1532fe2@xxxxxxxxxxxxxx> <4AC3EE07.3010000@xxxxxxxx> <64bddf0e0910010635wc085961tf55000d4305da2bf@xxxxxxxxxxxxxx> <4AC518A1.8080905@xxxxxxxx> <64bddf0e0910060813v2f2d4149wf2898653719d6ba3@xxxxxxxxxxxxxx> <4ACB70F0.5020502@xxxxxxxx> <64bddf0e0910061023t58828929i99da6a63155e82c@xxxxxxxxxxxxxx> <4ACB8462.1040102@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> What console output do you get?

It's the same as starting dom0 with 4G - 32G of memory, just freezes
at a different place in the boot each time.

> 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.

(gdb) x/i 0xffffffff8100930a
0xffffffff8100930a <hypercall_page+778>:        add    %al,(%rax)
(gdb) x/i 0xffffffff811fea48
0xffffffff811fea48 <delay_tsc+62>:      
    cmpq   $0x0,0x632538(%rip)        # 0xffffffff81830f88 <pv_cpu_ops+264>

> What happens if you boot dom0 with fewer cpus?

I tried adding "maxcpus=1" to the linux kernel line in grub.  I used
this in conjunction with the "dom0_mem=2G" option for xen.  Dom0 still
crashes the same as without the maxcpus option.

Just for kicks, I tried a few other options...

* setting mem=4G with dom0_mem=2G seemed still resulted in random dom0 crashing
* setting noapic resulted in a consistent crash within Xen:

(XEN) ----[ Xen-3.5-unstable  x86_64  debug=y  Not tainted ]----
(XEN) CPU:    0
(XEN) RIP:    e008:[<ffff82c48014fe29>] add_pin_to_irq+0x24/0xcc
(XEN) RFLAGS: 0000000000010296   CONTEXT: hypervisor

> Do you have CONFIG_PARAVIRT_SPINLOCKS enabled?

No.

-bryan

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