From owner-freebsd-questions@FreeBSD.ORG Mon Nov 17 20:29:05 2008 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CE8C106564A for ; Mon, 17 Nov 2008 20:29:05 +0000 (UTC) (envelope-from thomas@zaph.org) Received: from zaph.org (zaph.org [208.86.224.136]) by mx1.freebsd.org (Postfix) with ESMTP id 66C048FC20 for ; Mon, 17 Nov 2008 20:29:05 +0000 (UTC) (envelope-from thomas@zaph.org) Received: by zaph.org (Postfix, from userid 1002) id 16683B96D; Mon, 17 Nov 2008 15:29:05 -0500 (EST) Date: Mon, 17 Nov 2008 15:29:05 -0500 From: "N.J. Thomas" To: Jeremy Chadwick Message-ID: <20081117202905.GO91662@zaph.org> References: <5635aa0d0811140711t6af42ef8i762a37eb059ede19@mail.gmail.com> <20081117173845.GM91662@zaph.org> <26ddd1750811171147u5cc8f9b3k35f25c6caf9bc14f@mail.gmail.com> <20081117200102.GN91662@zaph.org> <20081117200849.GA38672@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081117200849.GA38672@icarus.home.lan> User-Agent: Mutt/1.4.2.3i Cc: questions@freebsd.org Subject: Re: FreeBSD not stable enough for Xen environments? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2008 20:29:05 -0000 * Jeremy Chadwick [2008-11-17 12:08:49+0000]: > > Intersting, I see the same in my logs, but the frequency seems to be > > much less than yours, e.g. for the month of November: > > What time counter source does this box have available? kern.timecounter.choice: TSC(-100) i8254(0) dummy(-1000000) kern.timecounter.hardware: i8254 > Other ideas: > Look into the "fudge" operator of ntp.conf. Yeah, I'm already fudging my local clock a bit. From my ntp.conf: # local clock server 127.127.1.0 # don't trust local clock too much fudge 127.127.1.0 stratum 10 > Try deleting your ntp driftfile. Note that if you do this, it will take > a day or two for things to "level out". It tries to figure out the > "average" skew rate your system clock has. Hmm, my drift file looks decent enough: $ cat /var/db/ntp.drift 10.047 And it's being updated regularly enough. > Then there's a very good possibility it's hardware-related. I'll ask the hosting company about it though to see if anyone has brought this up. Thomas