From owner-freebsd-current Thu Jul 16 02:45:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16916 for freebsd-current-outgoing; Thu, 16 Jul 1998 02:45:00 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16911 for ; Thu, 16 Jul 1998 02:44:55 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA02024; Thu, 16 Jul 1998 19:44:45 +1000 Date: Thu, 16 Jul 1998 19:44:45 +1000 From: Bruce Evans Message-Id: <199807160944.TAA02024@godzilla.zeta.org.au> To: bde@zeta.org.au, jak@cetlink.net Subject: Re: tickadj -t not changing tick Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>OTOH, when you change the m-d variables, the kernel attempts to propagate >>the changes, but it doesn't succeed (it sets the active frequency, >>possibly causing a glitch due to the non-atomic update, and the change >>gets blown away at the next clock interrupt). > >I just tried this on a 486 running a 980515 SNAP, and it worked. It >*did* propagate machdep.i8254_freq to kern.timecounter.frequency. And >from checking the time deviation with ntpdate, it seems to be right on >the mark now. > >Are you saying it may propagate sometimes but not always? Perhaps it is only broken for my version of machdep.tsc_freq. For the standard version, setting machdep.tsc_freq to 0 causes a panic for division by 0 for obvious reasons instead of switching to the i8254 version like it is supposed to and does in my version. Standard versions just depend on the `tweak' timecounter being at index 0, which it is. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message