From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Failed to reboot Dom0 kernel because of segfault
Date: Thu, 12 Nov 2009 15:46:59 -0800
Message-ID: <4AFC9E73.5010902@goop.org>
References: <6752C14F1F9044FA826522C48691CEE9@univ9080>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <6752C14F1F9044FA826522C48691CEE9@univ9080>
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: Sun Shuchun <sun.shuchun@jp.fujitsu.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 11/09/09 21:52, Sun Shuchun wrote:
> Hi xen developers,
>
> Could anyone tell me why a problem below happened?
>
> Problem:
> A kernel panic occured, when I restarted my computer after installing
> xen-unstable.
>
> I copied the serial log text and attached it to this mail.

It looks like the pvclock vsyscall stuff is playing up again. booting
with vdso=0 on the kernel command line will work around this for now.

J