From owner-freebsd-xen@FreeBSD.ORG  Fri Nov 19 18:31:30 2010
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id C82FF106564A;
	Fri, 19 Nov 2010 18:31:30 +0000 (UTC)
	(envelope-from larry@kiputers.com)
Received: from web05.lax1.coolhandle.com (web05.lax1.pronethosting.net
	[209.151.224.242])
	by mx1.freebsd.org (Postfix) with ESMTP id 61B1E8FC14;
	Fri, 19 Nov 2010 18:31:30 +0000 (UTC)
Received: from c-98-248-45-176.hsd1.ca.comcast.net ([98.248.45.176]
	helo=[192.168.0.104])
	by web05.lax1.coolhandle.com with esmtpa (Exim 4.69)
	(envelope-from <larry@kiputers.com>)
	id 1PJVk2-0000jM-Tm; Fri, 19 Nov 2010 10:31:23 -0800
From: Larry Maloney <larry@kiputers.com>
To: Colin Percival <cperciva@freebsd.org>
In-Reply-To: <4CE68CD7.10804@freebsd.org>
References: <4CE68CD7.10804@freebsd.org>
Content-Type: text/plain; charset="us-ascii"
Organization: Kiputers, Inc.
Date: Fri, 19 Nov 2010 10:30:13 -0800
Message-ID: <1290191413.1758.16.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.1.2 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - web05.lax1.coolhandle.com
X-AntiAbuse: Original Domain - freebsd.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - kiputers.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: "freebsd-xen@freebsd.org" <freebsd-xen@freebsd.org>
Subject: Re: system stalls when wallclock/TOD nudged
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: larry@kiputers.com
List-Id: Discussion of the freebsd port to xen - implementation and usage
	<freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
	<mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
	<mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Nov 2010 18:31:30 -0000

Does your motherboard have a hardware watchdog timer?

Larry

On Fri, 2010-11-19 at 06:42 -0800, Colin Percival wrote:
> Hi all,
> 
> I'm seeing a weird bug here, and I'm wondering if anyone else has experienced
> this and/or has any clue how to fix it.
> 
> During the boot process, in the middle of running rc.d scripts, my FreeBSD/Xen
> instance stalls.  It does nothing until I send a shutdown signal, at which point
> > [XEN] hypervisor wallclock nudged; nudging TOD.
> and a couple buffered lines of rc.d script output are printed.  From there the
> rc.shutdown script starts running, but it too stalls after a short time; then I
> see
> > [XEN] hypervisor wallclock nudged; nudging TOD.
> > Nov 19 14:08:33 init: timeout expired for /bin/sh on /etc/rc.shutdown: Interrupted system call; going to single user mode
> printed, suggesting that the shutdown watchdog timer at least managed to not get
> stuck even though everything else did.
> 
> Any ideas?
>