From owner-freebsd-xen@FreeBSD.ORG Fri Nov 19 14:42:32 2010 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 6DCC61065672 for ; Fri, 19 Nov 2010 14:42:32 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from xps.daemonology.net (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx2.freebsd.org (Postfix) with SMTP id C6EAB14E5D9 for ; Fri, 19 Nov 2010 14:42:31 +0000 (UTC) Received: (qmail 20341 invoked from network); 19 Nov 2010 14:42:31 -0000 Received: from unknown (HELO xps.daemonology.net) (127.0.0.1) by localhost with SMTP; 19 Nov 2010 14:42:31 -0000 Message-ID: <4CE68CD7.10804@freebsd.org> Date: Fri, 19 Nov 2010 06:42:31 -0800 From: Colin Percival User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.11) Gecko/20100803 Thunderbird/3.0.6 MIME-Version: 1.0 To: "freebsd-xen@freebsd.org" X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: system stalls when wallclock/TOD nudged X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2010 14:42:32 -0000 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? -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid