From owner-freebsd-stable  Thu Apr  8 19:45:38 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from netrinsics.com (unknown [210.74.174.205])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9C55C1515E; Thu,  8 Apr 1999 19:43:01 -0700 (PDT)
	(envelope-from robinson@netrinsics.com)
Received: (from robinson@localhost)
	by netrinsics.com (8.9.2/8.8.7) id KAA46490;
	Fri, 9 Apr 1999 10:41:28 +0800 (CST)
	(envelope-from robinson)
Date: Fri, 9 Apr 1999 10:41:28 +0800 (CST)
From: Michael Robinson <robinson@netrinsics.com>
Message-Id: <199904090241.KAA46490@netrinsics.com>
To: mike@smith.net.au
Subject: Re: Real time clock problem in 3.1-STABLE
Cc: freebsd-hackers@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
In-Reply-To: <199904081930.MAA01011@dingo.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mike Smith <mike@smith.net.au> writes:
>The problem is probably our "advanced" timecounter code being screwed 
>by the Apricot's firmware.  You might try
>
>sysctl -w kern.timecounter.method=1

Could this also be used to get rid of "negative calcru" and clock drift
problems?

	-Michael Robinson



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message