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] Crash with paravirt-ops 2.6.31.6 kernel

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Crash with paravirt-ops 2.6.31.6 kernel
From: William Pitcock <nenolod@xxxxxxxxxxxxxxxx>
Date: Thu, 19 Nov 2009 11:21:44 +0300 (MSK)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 19 Nov 2009 00:24:41 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20091118144518.GD15585@xxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Konrad,

----- "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx> wrote:

> > [    1.254927] init[1] general protection ip:f779042f sp:ff9b0340
> error:0
> 

This is a domU kernel only.  And I am aware that init crashing is the
reason why.  My paravirt-ops dom0 kernels boot fine, but they are 64bit
userland.

The reason why I ask is because this only happens with the paravirt-ops
tree, e.g. not with the XenLinux 2.6.18 tree or the forward ports.

I think it might be related to the stackprotector option?

William

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