Date: Mon, 13 Jul 2015 04:31:40 +1000 From: Peter Jeremy <peter@rulingia.com> To: Ian Lepore <ian@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: Will 10.2 also ship with a very stale NTP? Message-ID: <20150712183140.GB22240@server.rulingia.com> In-Reply-To: <1436715703.1334.193.camel@freebsd.org> References: <20150710235810.GA76134@rwpc16.gfn.riverwillow.net.au> <20150712032256.GB19305@satori.lan> <20150712050443.GA22240@server.rulingia.com> <20150712154416.b9f3713893fe28bfab1dd4d7@dec.sakura.ne.jp> <CAGMYy3vKEUCD=Ssxt%2B2Vny4eQ7CNQHTxNKncyQnRk5dPQU6ZtA@mail.gmail.com> <20150712184910.2d8d5f085ae659d5b9a2aba0@dec.sakura.ne.jp> <1436715703.1334.193.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--/NkBOFFp2J2Af1nK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2015-Jul-12 09:41:43 -0600, Ian Lepore <ian@freebsd.org> wrote: >And let's all just hope that a week or two of testing is enough when >jumping a major piece of software forward several years in its >independent evolution. Whilst I support John's desire for NTP to be updated, I also do not think this is the appropriate time to do so. That said, the final decision is up to re@. >The import of 4.2.8p2 several months ago resulted in complete failure of >timekeeping on all my arm systems. Just last week I tracked it down to >a kernel bug (which I haven't committed the fix for yet). While the bug >has been in the kernel for years, it tooks a small change in ntpd >behavior to trigger it. > >Granted it's an odd corner-case problem that won't affect most users >because they just use the stock ntp.conf file (and it only affects >systems that have a large time step due to no battery-backed clock). >But it took me weeks to find enough time to track down the cause of the >problem. I'm not using the stock ntp.conf on my RPis and didn't notice any NTP issues. Are you able to provide more details of either the ntp.conf options that trigger the bug or the kernel bug itself? A quick search failed to find anything. --=20 Peter Jeremy --/NkBOFFp2J2Af1nK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJVorKMXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFRUIyOTg2QzMwNjcxRTc0RTY1QzIyN0Ux NkE1OTdBMEU0QTIwQjM0AAoJEBall6Dkogs0YiwP/2ZvBPTzQc5i8p5+lp72k0Zu RIiTCzTRu0CeDco78BXjndpCHH2smjDIqNVMixsvPbewIEX2Y3WF2k7yndFUwHvH SJQzsIzf7aR3mG0SRcAuPmq3yFy1Hozx+5hSjbotCc7AADW85KB9dtXys6jVpxVT nxJb3CQamqsgBjJeSkwIdHMs3mBQ3fTfLzhr+ovSnl/6STR+7fd9B9BCY81RHr0+ PBmlN1kPlxjiSH7JYGhXYl63sMjeeqsEZSFQOE308Xl8181PC0M6Zofvh35i5U2m FvP3UG8SNTwCzhDP9t6ngejsZMtmQAQpn2Pa3fAdA4RRTm1aFN+GM5Z6hyWC/Wck zeH+W5FWeFyglCOlAP4g2/mFMLfVlvY/mBkjQSX6OGwmKv0ynVpqYW16P/dVajTa 1IN3Cz+mKSsHNwhfP5CLrANpSMp7APmjL09vNZj5CtlHEjOMMNcpr0/5L+gjwsOP Y1o0xD8vXhAhSvqwPZ5M/GKRYSyezrNwITJfNQIL5oN/RLPmPIYlZthYOQAqEI+/ XOVtg88ad++3CltobOJTTxVlpyE9IWvb+04nXWR4/DohWy0afdTnvEenUPVvakPZ 2EYefTgxnPmSQAVneycQ/LnuE59k+mp8natw7vPVRO6mQEPnns4NEYAPqEapemY8 WZxUvsJav6lVIFmT29AK =Felr -----END PGP SIGNATURE----- --/NkBOFFp2J2Af1nK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150712183140.GB22240>