Date: Thu, 16 Jul 1998 09:17:58 GMT From: jak@cetlink.net (John Kelly) To: Bruce Evans <bde@zeta.org.au> Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Message-ID: <35adc33e.212647565@mail.cetlink.net> In-Reply-To: <199807160853.SAA31913@godzilla.zeta.org.au> References: <199807160853.SAA31913@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Jul 1998 18:53:34 +1000, Bruce Evans <bde@zeta.org.au> wrote: >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? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35adc33e.212647565>