<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - timesyncd: clock is off"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80582#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - timesyncd: clock is off"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80582">bug 80582</a>
from <span class="vcard"><a class="email" href="mailto:registo.mailling@gmail.com" title="Mauro Santos <registo.mailling@gmail.com>"> <span class="fn">Mauro Santos</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=80582#c10">comment #10</a>)
<span class="quote">> All the 0s are still an indication that something with the floating
> point arithmetic is broken on that machine, or with the systemd
> compilation:
> interval/delta/delay/jitter/drift 64s/+0.000s/0.000s/0.000s/+0ppm</span >
You were on to something, I have rebuilt the whole systemd package on the
raspberry itself and reinstalled it, now it seems to be working (hope I'm not
talking too soon). For good measure I've removed ntp, rebooted and checked if
there were any ntp processes running that could be masking the problem.
<span class="quote">> journalctl -b --no-pager -u systemd-timesyncd </span >
-- Logs begin at Qui 1970-01-01 01:00:04 CET, end at Ter 2014-07-15 12:02:16
WEST. --
Jan 01 01:00:08 archrpi systemd[1]: Starting Network Time Synchronization...
Jan 01 01:00:08 archrpi systemd-timesyncd[136]: System clock time unset or
jumped backwards, restoring from recorded timestamp: Tue 2014-07-15 10:19:29
WEST
Jul 15 10:19:29 archrpi systemd[1]: Started Network Time Synchronization.
Jul 15 10:19:34 archrpi systemd-timesyncd[136]: Network configuration changed,
trying to establish connection.
Jul 15 10:19:34 archrpi systemd-timesyncd[136]: Network configuration changed,
trying to establish connection.
Jul 15 10:19:35 archrpi systemd-timesyncd[136]: Network configuration changed,
trying to establish connection.
Jul 15 10:20:06 archrpi systemd-timesyncd[136]: Using NTP server
216.239.36.15:123 (time3.google.com).
Jul 15 10:20:22 archrpi systemd-timesyncd[136]:
interval/delta/delay/jitter/drift 32s/+16.811s/0.059s/0.000s/+0ppm
Jul 15 10:20:55 archrpi systemd-timesyncd[136]:
interval/delta/delay/jitter/drift 64s/-0.001s/0.058s/0.000s/+0ppm
Jul 15 10:21:59 archrpi systemd-timesyncd[136]:
interval/delta/delay/jitter/drift 128s/-0.002s/0.059s/0.001s/-7ppm
Jul 15 10:24:07 archrpi systemd-timesyncd[136]:
interval/delta/delay/jitter/drift 256s/-0.003s/0.058s/0.002s/-12ppm
Jul 15 10:28:23 archrpi systemd-timesyncd[136]:
interval/delta/delay/jitter/drift 512s/-0.004s/0.059s/0.002s/-16ppm
Jul 15 10:36:56 archrpi systemd-timesyncd[136]:
interval/delta/delay/jitter/drift 1024s/+0.007s/0.085s/0.004s/-16ppm (ignored)
Jul 15 10:54:00 archrpi systemd-timesyncd[136]:
interval/delta/delay/jitter/drift 2048s/-0.000s/0.095s/0.004s/-16ppm
Jul 15 11:28:08 archrpi systemd-timesyncd[136]:
interval/delta/delay/jitter/drift 2048s/-0.042s/0.059s/0.016s/-16ppm (ignored)
Jul 15 12:02:16 archrpi systemd-timesyncd[136]:
interval/delta/delay/jitter/drift 2048s/-0.068s/0.057s/0.063s/-37ppm
If you agree that timesyncd is now working as it should, we have to go complain
somewhere else as this isn't a problem with systemd.
Just another related question, is it intended that there is no man page for
timesyncd.conf or might it be that it is just missing from arch's package?
Thanks for your quick response on this and pointing me on the right direction.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>