From owner-freebsd-stable@FreeBSD.ORG Sun Mar 18 18:36:52 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7BF31065670 for ; Sun, 18 Mar 2012 18:36:52 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (unknown [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b2]) by mx1.freebsd.org (Postfix) with ESMTP id 617178FC0A for ; Sun, 18 Mar 2012 18:36:52 +0000 (UTC) Received: from meatwad.mouf.net (cpe-024-162-230-236.nc.res.rr.com [24.162.230.236]) (authenticated bits=0) by mouf.net (8.14.4/8.14.4) with ESMTP id q2IIalon061752 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 18 Mar 2012 14:36:48 -0400 (EDT) (envelope-from swills@FreeBSD.org) Message-ID: <4F662B38.4030700@FreeBSD.org> Date: Sun, 18 Mar 2012 14:36:40 -0400 From: Steve Wills User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120302 Thunderbird/10.0.2 MIME-Version: 1.0 To: Adam Strohl References: <4F5B0BB5.5010406@ateamsystems.com> <6D0B99CE-AE11-4250-A8D9-EF66E03E19BB@lists.zabbadoz.net> <4F5B5DAB.3010905@ateamsystems.com> In-Reply-To: <4F5B5DAB.3010905@ateamsystems.com> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mouf.net [204.109.58.86]); Sun, 18 Mar 2012 14:36:49 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.97.2 at mouf.net X-Virus-Status: Clean Cc: "Bjoern A. Zeeb" , FreeBSD-Stable ML Subject: Re: Time Clock Stops in FreeBSD 9.0 guest running under ESXi 5.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2012 18:36:52 -0000 On 03/10/12 08:56, Adam Strohl wrote: > On 3/10/2012 17:10, Bjoern A. Zeeb wrote: >> On 10. Mar 2012, at 08:07 , Adam Strohl wrote: >> >>> I've now seen this on two different VMs on two different ESXi servers >>> (Xeon based hosts but different hardware otherwise and at different >>> facilities): >>> >>> Everything runs fine for weeks then (seemingly) suddenly/randomly the >>> clock STOPS. >> >> Apart from the ntp vs. openvm-tools thing, do you have an idea what >> "for weeks" means in more detail? Can you check based on last/daily >> mails/.. how many days it was since last reboot to a) see if it's >> close to a integer wrap-around or b) to give anyone who wants to >> reproduce this maybe a clue on how long they'll have to wait? For >> that matter, is it a stock 9.0 or your own kernel? What other modules >> are loaded? > > Uptime was 31 days on the first incident / server (occurred 5 days ago) > Uptime was 4 days on the second incident / server (occurred last night) > I've experienced something similar once or twice with ESXi 5.0. The second time it happened, I found that kern.timecounter.tc.HPET.counter stopped changing. I was told on IRC that this indicated a "hardware" problem, which I took to indicate a possible bug in ESXi. I haven't upgraded to ESXi 5.0 Update 1 yet to see if that changes anything. Rebooting of course fixed it, it has been a while since this happened and it hasn't happened again since so I haven't pursued it. Just another data point, hope it hopes. Steve