From owner-freebsd-current Wed Jul 22 12:41:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09577 for freebsd-current-outgoing; Wed, 22 Jul 1998 12:41:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09462 for ; Wed, 22 Jul 1998 12:41:07 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id VAA00907; Wed, 22 Jul 1998 21:35:46 +0200 (CEST) To: Bruce Evans cc: brian@Awfulhak.org, freebsd-current@FreeBSD.ORG, jak@cetlink.net Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Mon, 20 Jul 1998 16:42:39 +1000." <199807200642.QAA17899@godzilla.zeta.org.au> Date: Wed, 22 Jul 1998 21:35:46 +0200 Message-ID: <905.901136146@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199807200642.QAA17899@godzilla.zeta.org.au>, Bruce Evans writes: >>APM seems to be preventing use of the TSC timecounter. Otherwise >>the clock would go non-backwards 233/17 faster :-). > >The whole problem may be caused by APM. APM's time handling is of low >quality. As currently designed, there is only the RTC chip which is reliably keeping track of time on a APMized system, and only reading the registers is reliable, the number of interrupts and their frequency is subject to change without notice. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message