From owner-freebsd-current Sun Jul 29 0:22:59 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 1D7DE37B403; Sun, 29 Jul 2001 00:22:54 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id RAA28513; Sun, 29 Jul 2001 17:22:48 +1000 Date: Sun, 29 Jul 2001 17:20:27 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Mike Smith Cc: Daniel Rock , current@FreeBSD.ORG Subject: Re: ACPI: Clock problems in -current In-Reply-To: <200107282006.f6SK6RJ01779@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 28 Jul 2001, Mike Smith wrote: > You could also try building a kernel with CLK_CALIBRATION_LOOP defined > and then booting with -v (without the timer disabled). This might be > instructive (I don't know for certain that it'll calibrate the ACPI > timer, since it may not have been probed yet). It won't. CLK_CALIBRATION_LOOP only iterates calibration of the i8254 and TSC timers relative to the RTC. None of the clock calibration stuff is very useful. All the clock frequencies depend on the temperature, so their values at boot time are only slightly more related to their values at run time than their values at a random time. Average values are probably better than boot time values. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message