Date: Tue, 14 Nov 2017 08:10:39 +0100 From: Henri Hennebert <hlh@restart.be> To: freebsd-arm@FreeBSD.org Subject: Re: PINE64 - 12.0-CURRENT r324563 - ntpd can't keep time Message-ID: <45c53cf7-14f7-f1ec-038f-48fed7248146@restart.be> In-Reply-To: <4afdde9c747.319ba732@mail.schwarzes.net> References: <d85f883f-84c2-5051-1996-2a0e73a2c1e7@restart.be> <4BF75B1E-318C-414A-B5D4-4BA7D6578316@dsl-only.net> <1509029871.56824.49.camel@freebsd.org> <c2bff518-89ce-4956-2548-e56afab5d83d@restart.be> <4af740148ca.47a474e3@mail.schwarzes.net> <04b67007-a95a-9e40-28b4-764adf8b2ded@restart.be> <FCA144E8-121A-48A5-8CDB-101FBDE6E84C@dsl-only.net> <4afdde9c747.319ba732@mail.schwarzes.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/13/2017 22:33, Andreas Schwarz wrote: > On 13.11.17, Mark Millard wrote: > >> On 2017-Nov-13, at 9:01 AM, Henri Hennebert <hlh at restart.be> wrote: > >>> remote refid st t when poll reach delay offset jitter >>> ============================================================================== >>> 0.freebsd.pool. .POOL. 16 p - 64 0 0.000 0.000 0.000 >>> -webhost2.mitht. 193.67.79.202 2 u 948 1024 177 58.815 1.451 0.932 >>> +ns2.telecom.lt 212.59.3.3 2 u 13 1024 177 43.400 -357912 357913. >>> +ntp.bserved.nl 193.67.79.202 2 u 1111 1024 37 17.664 0.980 0.379 >>> -178.32.44.208 ( 193.190.230.65 2 u 81 1024 177 14.930 1.087 135278. >>> *stratum2-1.NTP. 129.70.130.71 2 u 1077 1024 77 28.135 1.998 0.570 >>> -linode.ibendit. 199.102.46.77 2 u 2048 1024 76 129.945 0.307 0.584 >>> #193.104.37.238 193.190.230.66 2 u 799 1024 77 14.977 1.321 0.821 >>> >>> And after a half hour the clock was 5 minutes in the future. >> >> Did you notice the huge offset and jitter in your listing: >> (last 2 numerals in the line below) >> >> +ns2.telecom.lt 212.59.3.3 2 u 13 1024 177 43.400 -357912 357913. > > Yes, this peer causes the problem, the offset jumps between your pollings from > ~0 to -350k, all other peers are in range. The jitter was the result of this jump. > In your previous emails, other peers had the same problem, so it's probaly not > a problem with the peer itself. Maybe a strange network problem, ntp is UDP, > do you have a real IP Adress, without NAT/CGN or other packet rewriting? > The Pine64+ is directly connected to the internet (mpd5 with a b-box3 in bridge mode). Moreover if I rollback to r320599 all run smoothly for more than 8 days. Henri > -asc > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45c53cf7-14f7-f1ec-038f-48fed7248146>