From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Crash with paravirt-ops 2.6.31.6 kernel
Date: Wed, 18 Nov 2009 09:45:18 -0500
Message-ID: <20091118144518.GD15585@phenom.dumpdata.com>
References: <28846609.721258484676784.JavaMail.root@ifrit.dereferenced.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <28846609.721258484676784.JavaMail.root@ifrit.dereferenced.org>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: William Pitcock <nenolod@dereferenced.org>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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

That is what caused it. It would be of interest if you could disassemble init
and see what is the offending instruction (and around a couple of lines before it).
Use objdump for that purpose.

Also, please add these to your bootline to get more debug information (obviously
change your com1 and root line):

	root (hd0,0)
	kernel	/xen-3.5-unstable.4.gz com1=115200,8n1,0xd800,0 console=com1,vga guest_loglvl=all loglvl=all sync_console console_to_ring dom0_mem=2GB
	module /bzImage ro root=UUID=d6d08653-4a4f-4d41-87f2-f42fb7fe3ad5 initrd_ignore_loglevel sysrq_always_enable earlyprintk=xen console=tty console=hvc0 loglevel=10 debug
	module /initrd-2.6.31-5.img