Date: Thu, 8 Apr 1999 10:36:59 +0100 (BST) From: Mark Powell <M.S.Powell@ais.salford.ac.uk> To: freebsd-hackers@freebsd.org Cc: freebsd-stable@freebsd.org Subject: Real time clock problem in 3.1-STABLE Message-ID: <Pine.BSF.4.05.9904081028330.27718-100000@plato.salford.ac.uk>
next 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. Mark Powell - System Administrator (UNIX) - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key M.S.Powell@ais.salfrd.ac.uk (spell salford correctly to reply to me) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9904081028330.27718-100000>