From owner-freebsd-stable@FreeBSD.ORG Wed Dec 7 18:25:03 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6661116A41F for ; Wed, 7 Dec 2005 18:25:03 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail10.syd.optusnet.com.au (mail10.syd.optusnet.com.au [211.29.132.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8967A43D81 for ; Wed, 7 Dec 2005 18:24:10 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail10.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jB7IN7wM016830 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Thu, 8 Dec 2005 05:23:08 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jB7IN7Hh066339 for ; Thu, 8 Dec 2005 05:23:07 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jB7IMblM066338; Thu, 8 Dec 2005 05:22:37 +1100 (EST) (envelope-from pjeremy) Date: Thu, 8 Dec 2005 05:22:36 +1100 From: Peter Jeremy To: Ed Message-ID: <20051207182236.GS32006@cirb503493.alcatel.com.au> References: <20051207071710.GQ32006@cirb503493.alcatel.com.au> <002b01c5fb24$9a802150$1132e7d8@robotslave> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002b01c5fb24$9a802150$1132e7d8@robotslave> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-stable@freebsd.org Subject: Re: cpu-timer rate 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: Wed, 07 Dec 2005 18:25:03 -0000 On Wed, 2005-Dec-07 03:51:47 -0800, Ed wrote: >I certainly do not have a full understanding of the interactions between >the various FreeBSD software timers and i386 hardware clocks, but I do know >this is not the first time we've seen a problem with the APIC/ACPI >timers/clocks. You have a totally different problem. In your case the system is not keeping correct time - this is because VMware does not provide stable clock interrupts - probably due to interactions between VMware and the host OS. In kama's case, the interrupt rate reported by vmstat -i does not match the numbers reported by kern.clockrate. There is no indication that the system is not keeping correct time. >Again, I'm no expert, but clock problems do keep cropping up here on >the -STABLE list, and the explanations for them to date have not been >consistent. AFAIR, all the problems reported here have been related to VMware clients. And as someone stated "VMware plays fast and loose with clocks". >I'm sure I'm not the only end-user who would appreciate it if the core team This is nothing to do with the core team. -- Peter Jeremy