From owner-freebsd-stable Mon Aug 28 11:12:33 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sf-gw.envolved.com (w018.z064220173.sjc-ca.dsl.cnc.net [64.220.173.18]) by hub.freebsd.org (Postfix) with ESMTP id 894A837B42C for ; Mon, 28 Aug 2000 11:12:23 -0700 (PDT) Received: from envolved.com (IDENT:sbeitzel@[192.168.0.51]) by sf-gw.envolved.com (8.9.3/8.9.3) with ESMTP id LAA10016; Mon, 28 Aug 2000 11:09:35 -0700 (PDT) (envelope-from sbeitzel@envolved.com) Message-Id: <200008281809.LAA10016@sf-gw.envolved.com> Date: Mon, 28 Aug 2000 11:09:28 -0700 (PDT) From: Stephen Beitzel Reply-To: Stephen Beitzel Subject: Re: Time is being weird To: mitayai@bricsnet.com Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28 Aug, Will Mitayai Keeso Rowe wrote: > This is likely a hardware issue, but in case it's not... > > My clock keeps getting ahead and won't stay on time... any ideas? Last night I was configuring a new box. I started out with FreeBSD 4.0-RELEASE (from CD) and cvsupped to 4.1-STABLE. During the cvsup and the subsequent builds, the clock went nuts several times, spewing kernel messages about microuptime going negative and meanwhile moving the system clock forward at about 3:1. Anyway, once I restarted with the updated world and kernel, the nastiness went away. I don't remember what's been committed to -STABLE since the 18th, but I do remember seeing dates of 8/21 and later flash by during the cvsup, so you might try updating and rebuilding. Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message