From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <jbeulich@novell.com>
Subject: Re: [RESEND] Linux 2.3.23-rc3 on Xen 3.1 crashs
Date: Wed, 29 Aug 2007 11:39:25 +0100
Message-ID: <46D568FD.76E4.0078.0@novell.com>
References: <20070825154617.GA27424@wavehammer.waldi.eu.org>
	<20070829100259.GA25709@wavehammer.waldi.eu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20070829100259.GA25709@wavehammer.waldi.eu.org>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/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/cgi-bin/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: Bastian Blank <bastian@waldi.eu.org>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

>There seems to be two code adresses in the trace:
>| c027abd0 T page_fault
>| c0107a20 T invalid_op

These aren't really meaningful, as the VM was obviously in a loop getting
repeated exceptions (and the stack pointer clearly went bad meanwhile).
You'd need to catch the state much earlier, when the first (or just very =
few)
of these exceptions happened, so that looking at the stack can actually
provide some insight.

Jan