Date: Mon, 3 Feb 2003 14:15:23 +0100 (CET) From: Roderick van Domburg <roderick@stud187236.mobiel.utwente.nl> To: FreeBSD-gnats-submit@FreeBSD.org Subject: sparc64/47845: 4 second daily clock drift Message-ID: <200302031315.h13DFNLB007484@stud187236.mobiel.utwente.nl>
next in thread | raw e-mail | index | archive | help
>Number: 47845 >Category: sparc64 >Synopsis: 4 second daily clock drift >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-sparc >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Feb 03 05:20:19 PST 2003 >Closed-Date: >Last-Modified: >Originator: Roderick van Domburg >Release: FreeBSD 5.0-CURRENT sparc64 >Organization: University of Twente >Environment: System: FreeBSD stud187236.mobiel.utwente.nl 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Feb 2 21:52:27 CET 2003 roderick@stud187236.mobiel.utwente.nl:/usr/obj/usr/src/sys/E250 sparc64 Sun Ultra 250 (1x UltraSPARC-II 400 MHz) >Description: Each day, the system shows a 4-second clock drift. I noticed this because I set up a nightly ntpdate cron job. Unfortunately, it isn't much use to me because I'm running on securelevel 3 and the clock drift is so significant: the correction is clamped to 1 second. I can't imagine my system timer to be hosed, so is perhaps the timer calibration hosed? >How-To-Repeat: Just leave the system up and running and ntpdate daily. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-sparc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200302031315.h13DFNLB007484>