From owner-freebsd-bugs@FreeBSD.ORG Mon Jan 23 20:40:14 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0BB6106566B for ; Mon, 23 Jan 2012 20:40:14 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1613A8FC19 for ; Mon, 23 Jan 2012 20:40:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q0NKeDCR017602 for ; Mon, 23 Jan 2012 20:40:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0NKeDFi017597; Mon, 23 Jan 2012 20:40:13 GMT (envelope-from gnats) Date: Mon, 23 Jan 2012 20:40:13 GMT Message-Id: <201201232040.q0NKeDFi017597@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Bruce Cran Cc: Subject: Re: misc/164419: 9.0-RELEASE clock stops in Xen 3.2.1 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bruce Cran List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2012 20:40:15 -0000 The following reply was made to PR misc/164419; it has been noted by GNATS. From: Bruce Cran To: Robert Lampe Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: misc/164419: 9.0-RELEASE clock stops in Xen 3.2.1 Date: Mon, 23 Jan 2012 20:31:13 +0000 On 23/01/2012 20:14, Robert Lampe wrote: > After following the freebsd-update instructions > (http://www.freebsd.org/releases/9.0R/installation.html) to upgrade to > 9.0-RELEASE, we have found that VMs running in HVM mode in Xen 3.2.1 > have an issue where the clock stops working after about 3 minutes: # > date Mon Jan 23 20:06:21 UTC 2012 # date Mon Jan 23 20:09:48 UTC 2012 > Any other call of date after this outputs the same result. New > processes cannot be started and the machine is essentially frozen. The timecounter code was overhauled for 9.0, making progress towards a 'tickless' kernel. As a quick workaround you should be able to set kern.eventtimer.periodic=1 to get ticks going again. You might want to add it to /etc/sysctl.conf to make it permanent until a proper fix can be made. -- Bruce Cran