[chrony-users] Fwd: Chrony malfunctioning at beaglebones |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] Fwd: Chrony malfunctioning at beaglebones
- From: Nuno Gonçalves <nunojpg@xxxxxxxxx>
- Date: Sun, 16 Aug 2015 19:51:01 +0100
- Cc: dl4mea@xxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Ei/F/qN+l1d2YDwLkx7DsoiC+L5udT6bs0quQR/5QRk=; b=I5HinZXMILafUN8So9KL39DI2Kekm9jgO9i8rD+w4f5MmPfDapn1FYyduGEmrdopb6 ThYs37LNymw4c51WoZalG+7miaPhINRUcrn13HB1tjuIHMLDvG860HcT+GUd+D6k7cxK t/UHP7AG0lI1dkeX0Tlj5cHVxSWNMm23YhiLq5S+DHi245pjFBUKWMXHbmzD0/HyDtHC Htvr6fwdBozLzeZYUY771WPnkdPZQuu4LZE5IVjSCTa68cza5RxwV+3KfDT859wfN24c U4d32OE3DAWTB3nHMdTHqM0Af+F4+2pbqhVpSbPoBS5FKpaz/GbFCWpdFDHOrq9li2xF JfRg==
Hi,
Chrony at armv7l, a Beaglebone running Debian 8.1 (linux 4.1.5) looks
to be broken.
I have tested both a Beaglebone white and a Beaglebone black.
I have tested with the Debian package (1.30), 2.1.1, and git HEAD.
So, usually Chrony does sync the clock, but gives weird frequency estimates.
Since this devices don't have a RTC, I have tried to start chrony both
with a time way in the past, but also with a "correct" time already
set.
Machine 1:
debian@bbw1:~$ chronyc tracking
Reference ID : 5.135.59.152 (ntp1.unixcraft.org)
Stratum : 3
Ref time (UTC) : Sun Aug 16 18:32:27 2015
System time : 0.000288986 seconds slow of NTP time
Last offset : +0.199954823 seconds
RMS offset : 0.199954823 seconds
Frequency : 92.190 ppm fast
Residual freq : +42658.770 ppm
Skew : 1000000.000 ppm
Root delay : 0.070693 seconds
Root dispersion : 175.260788 seconds
Update interval : 2.3 seconds
Leap status : Normal
debian@bbw1:~$ chronyc sources
210 Number of sources = 3
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^+ a88-157-128-22.cpe.netcab 3 8 37 174 +68ms[ +268ms] +/- 66ms
^+ adsl-62-48-148-210.ptprim 3 8 37 174 +52ms[ +252ms] +/- 71ms
^* ntp1.unixcraft.org 2 8 37 173 +114ms[ +314ms] +/- 68ms
debian@bbw1:~$ chronyc sourcestats
210 Number of sources = 3
Name/IP Address NP NR Span Frequency Freq Skew Offset Std Dev
==============================================================================
a88-157-128-22.cpe.netcab 5 3 9 +43847.180 151084 +7882ms 65ms
adsl-62-48-148-210.ptprim 5 3 8 +45060.492 169101 +8104ms 75ms
ntp1.unixcraft.org 5 3 9 +37482.402 234556 +6671ms 83ms
Machine 2:
debian@bbb1:~$ chronyc tracking
Reference ID : 193.136.164.1 (ns.rnl.tecnico.ulisboa.pt)
Stratum : 4
Ref time (UTC) : Sun Aug 16 18:32:22 2015
System time : 0.000045670 seconds fast of NTP time
Last offset : -0.075360224 seconds
RMS offset : 0.075360224 seconds
Frequency : 500.000 ppm fast
Residual freq : -27241.334 ppm
Skew : 1000000.000 ppm
Root delay : 0.026741 seconds
Root dispersion : 155.273239 seconds
Update interval : 2.0 seconds
Leap status : Normal
debian@bbb1:~$ chronyc sources
210 Number of sources = 2
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
^* ns.rnl.tecnico.ulisboa.pt 3 8 37 155 -9917us[ -85ms] +/- 15ms
^- a88-157-128-22.cpe.netcab 3 8 37 154 -35ms[ -35ms] +/- 64ms
debian@bbb1:~$ chronyc sourcestats
210 Number of sources = 2
Name/IP Address NP NR Span Frequency Freq Skew Offset Std Dev
==============================================================================
ns.rnl.tecnico.ulisboa.pt 5 3 8 -27241.334 74445.352 -4354ms 30ms
a88-157-128-22.cpe.netcab 5 3 8 -29209.541 74561.016 -4684ms 31ms
What kind of debug info should I collect?
Best regards,
Nuno
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.