On Tue, Mar 10, 2009 at 11:18:07AM +0100, Andreas Herrmann wrote:On Tue, Jan 20, 2009 at 04:16:10PM +0200, Mika Tiainen wrote:Hi,
I built a new machine with Gigabyte GA-MA74GM-S2H motherboard that ntpd
can't keep synced. Could this be a kernel bug or is it a hardware
problem?
Installed with Debian 2.6.27 kernel and currently running a self built
2.6.28.1, both have the problem. It's falling behind over 2s/15min:
Jan 19 22:08:23 aeon ntpd[31468]: time reset +2.226349 s
Jan 19 22:24:11 aeon ntpd[31468]: time reset +2.185085 s
Jan 19 22:40:08 aeon ntpd[31468]: time reset +2.308958 s
Jan 19 22:56:23 aeon ntpd[31468]: time reset +2.253836 s
Jan 19 23:13:03 aeon ntpd[31468]: time reset +2.291917 s
Jan 19 23:28:14 aeon ntpd[31468]: time reset +2.091014 s
Jan 19 23:43:47 aeon ntpd[31468]: time reset +2.209660 s
Jan 19 23:59:09 aeon ntpd[31468]: time reset +2.150145 s
Jan 20 00:15:44 aeon ntpd[31468]: time reset +2.256261 s
Jan 20 00:31:47 aeon ntpd[31468]: time reset +2.253873 s
I have tried different clocksources. The machine defaults to hpet,
acpi_pm makes no difference and
That's annoying but I can't really help you with this. Maybe using
adjtimex as described in section 9.1.6 in
http://support.ntp.org/bin/view/Support/KnownHardwareIssues is an
option for you.
So it's "mere a question" of calibration on your system. AFAIK
you have to increase the tick value to not fall behind ntp-time, e.g.
increasing tick value from 10000 to 10025