System clock running too fast
Hello,
I'm running Debian Sid on a system that seems to be having clock
problems: the system clock is running too fast by about 5 seconds per
hour. The system is always powered on, so from my limited understanding
the hardware clock doesn't play a role in this.
I have installed ntp-simple without result, the clock remains too fast
even though ntpd seems to be syncing correctly. "ntpdate eskarina"
(eskarina = my ntpd-running, properly-synced server) does seem to sync
the clock correctly, but the time jumps resulting from running that
regularly, even automated, don't seem like a very attractive idea to me.
I've also tried running ntpdate right before starting ntpd, as well as
running openntpd instead, neither of which solved the problem.
I put some system info & log dumps I thought might be relevant at the
bottom of this mail. Ofcourse I'll gladly provide any other information
that might be useful in solving this problem.
regards,
Arjen
--- System info & logfiles ---
The system is a Shuttle XPC SN45G (Athlon-based) with an Nforce2
chipset.
# uname -a
Linux greebo 2.6.10-1-k7 #1 Fri Mar 11 03:13:32 EST 2005 i686 GNU/Linux
(this is Debian package version 2.6.10-6)
# cat /etc/timezone
Etc/UTC
some daemon.log entries from ntpd:
Apr 30 03:19:47 greebo ntpd[30014]: ntpd 4.2.0a@1:4.2.0a+stable-8-r Sat Mar 19 14:14:09 CET 2005 (1)
Apr 30 03:19:47 greebo ntpd[30014]: precision = 3.000 usec
Apr 30 03:19:47 greebo ntpd[30014]: Listening on interface wildcard, 0.0.0.0#123
Apr 30 03:19:47 greebo ntpd[30014]: Listening on interface wildcard, ::#123
Apr 30 03:19:47 greebo ntpd[30014]: Listening on interface lo, 127.0.0.1#123
Apr 30 03:19:47 greebo ntpd[30014]: Listening on interface eth0, 10.0.1.3#123
Apr 30 03:19:47 greebo ntpd[30014]: kernel time sync status 0040
Apr 30 03:19:47 greebo ntpd[30014]: frequency initialized 0.000 PPM from /var/lib/ntp/ntp.drift
Apr 30 03:23:03 greebo ntpd[30014]: synchronized to LOCAL(0), stratum 13
Apr 30 03:23:03 greebo ntpd[30014]: kernel time sync disabled 0041
Apr 30 03:24:08 greebo ntpd[30014]: kernel time sync enabled 0001
Apr 30 03:25:13 greebo ntpd[30014]: synchronized to 193.77.147.115, stratum 3
Apr 30 03:26:16 greebo ntpd[30014]: synchronized to LOCAL(0), stratum 13
Apr 30 03:28:27 greebo ntpd[30014]: synchronized to 193.77.147.115, stratum 3
Apr 30 03:32:38 greebo ntpd[30014]: synchronized to 10.0.0.1, stratum 3
Apr 30 03:32:48 greebo ntpd[30014]: synchronized to LOCAL(0), stratum 13
Apr 30 03:34:58 greebo ntpd[30014]: synchronized to 193.77.147.115, stratum 3
Apr 30 03:41:24 greebo ntpd[30014]: synchronized to LOCAL(0), stratum 13
(then some 7 hours of no new log entries until I started messing around
with it again since there was no change in the problem)
"dmesg" output at http://xyx.nl/~arjen/greebo_dmesg.txt (the last 20 or
so lines are mostly a result of my experimenting).
/var/log/{messages,syslog} don't seem to contain anything that can't be
found in daemon.log or "dmesg" output.
# adjtimex -p
mode: 0
offset: -5122
frequency: -1269633
maxerror: 1346795
esterror: 52355
status: 1
time_constant: 2
precision: 1
tolerance: 33554432
tick: 9986
raw time: 1114863900s 924719us = 1114863900.924719
Using adjtimexconfig results in wildly varying adjustment values from
one moment to the next, random example:
# adjtimexconfig; adjtimexconfig
Comparing clocks (this will take 70 sec)...done.
Adjusting system time by -267.641 sec/day to agree with CMOS clock...done.
Comparing clocks (this will take 70 sec)...done.
Adjusting system time by -129.66 sec/day to agree with CMOS clock...done.
# cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 8
model name : AMD Athlon(tm) XP 2200+
stepping : 1
cpu MHz : 1797.146
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 mmx fxsr sse pni syscall mmxext 3dnowext 3dnow
bogomips : 3555.32
# lspci
0000:00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1)
0000:00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
0000:00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
0000:00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
0000:00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
0000:00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
0000:00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
0000:00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
0000:00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
0000:00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
0000:00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4)
0000:00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
0000:00:05.0 Multimedia audio controller: nVidia Corporation nForce MultiMedia audio [Via VT82C686B] (rev a2)
0000:00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)
0000:00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
0000:00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
0000:00:0d.0 FireWire (IEEE 1394): nVidia Corporation nForce2 FireWire (IEEE 1394) Controller (rev a3)
0000:00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
0000:03:00.0 VGA compatible controller: nVidia Corporation NV31 [GeForce FX 5600] (rev a1)
--- End ---
Reply to: