Date: Thu, 08 Apr 1999 12:30:32 -0700 From: Mike Smith <mike@smith.net.au> To: Mark Powell <M.S.Powell@ais.salford.ac.uk> Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Real time clock problem in 3.1-STABLE Message-ID: <199904081930.MAA01011@dingo.cdrom.com> In-Reply-To: Your message of "Thu, 08 Apr 1999 10:36:59 BST." <Pine.BSF.4.05.9904081028330.27718-100000@plato.salford.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> Installed 3.1-STABLE on an Apricot Shogun server. xntpd wouldn't sync time > correctly though. I set it up just as I do on any other machine. However, > on the same machine RedHat 5.2 can sync the time just fine. > FreeBSD had problems both before and after the recent kernel clock mods. > I notice that with 3.1-S looking at the clocks at boot up, it would appear > that over 40 reboots, the TSC clock has varied from 126668897 to > 132002659, a variance of almost 5%. Is this normal? Whereas when Linux > boots up the variance in processor clock speed is only about 1000Hz. Could > this be causing the time problems, and if so is there anyway I can fiddle > with tickadj or something to let xntpd work on this machine? > Unfortunately I'm going to have to go with Linux on this machine if > 3.1-S can't sync the time correctly. Anyone help? Cheers. The problem is probably our "advanced" timecounter code being screwed by the Apricot's firmware. You might try sysctl -w kern.timecounter.method=1 and see if that helps. Also talk to phk@freebsd.org about this if you haven't already. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904081930.MAA01011>