From owner-freebsd-current Thu Jul 16 02:16:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13942 for freebsd-current-outgoing; Thu, 16 Jul 1998 02:16:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns2.cetlink.net (root@ns2.cetlink.net [209.54.54.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13931 for ; Thu, 16 Jul 1998 02:16:21 -0700 (PDT) (envelope-from jak@cetlink.net) Received: from EXIT10 (i485-gw.cetlink.net [209.198.15.97]) by ns2.cetlink.net (8.9.1/8.9.1) with SMTP id FAA18778; Thu, 16 Jul 1998 05:15:59 -0400 (EDT) From: jak@cetlink.net (John Kelly) To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Date: Thu, 16 Jul 1998 09:17:58 GMT Message-ID: <35adc33e.212647565@mail.cetlink.net> References: <199807160853.SAA31913@godzilla.zeta.org.au> In-Reply-To: <199807160853.SAA31913@godzilla.zeta.org.au> X-Mailer: Forte Agent 1.5/32.451 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id CAA13936 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Jul 1998 18:53:34 +1000, Bruce Evans 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