Date: Sat, 5 Aug 2023 21:22:07 +0100 From: Steve O'Hara-Smith <steve@sohara.org> To: questions@freebsd.org Subject: Re: NTPD frequency error Message-ID: <20230805212207.8ecbb6c2d7327fea15b260f5@sohara.org> In-Reply-To: <20230805155517.000024c3@seibercom.net> References: <20230805133309.00007dfa@seibercom.net> <20230805191458.61ad15f4267596538c6c8055@sohara.org> <20230805155517.000024c3@seibercom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 5 Aug 2023 15:55:17 -0400 "Gerard E. Seibert" <jerry@seibercom.net> wrote: > On Sat, 5 Aug 2023 19:14:58 +0100, Steve O'Hara-Smith stated: > > On Sat, 5 Aug 2023 13:33:09 -0400 > > You might need a new clock battery. > > > It may be possible that the battery is getting weak. It is strange that > this problem only manifested immediately after I updated the system. How long had it been running before you updated the system ? > Besides, if the system is up and running, does the battery do anything? I've seen it to be the only power source for the RTC, and I've known it not be the only power source. > I will swap it out tomorrow when I get a replacement and see if it > makes any difference. Cheap and worth a try - unless ntpd has grown a nasty bug it pretty much has to be the hardware running out of spec - hmm or refusing to pull! Now there is a possibility if the code that drives the frequency changing is broken that would also do this. I've pushed all my systems to 13.2-p2 recently they're all running ntpd without complaint. -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20230805212207.8ecbb6c2d7327fea15b260f5>