Date: Fri, 16 Oct 2009 15:55:11 -0400 From: Miles Nordin <carton@Ivy.NET> To: freebsd-sparc64@freebsd.org Subject: Re: FreeBSD/sparc64 on SunFire V215 - clock (?) problem Message-ID: <oqvdifktb4.fsf@castrovalva.Ivy.NET> In-Reply-To: <3979a4b0910142324s5158a7f9g91ca45298738730c@mail.gmail.com> (KOT MATPOCKuH's message of "Thu, 15 Oct 2009 10:24:30 %2B0400") References: <3979a4b0910142324s5158a7f9g91ca45298738730c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--pgp-sign-Multipart_Fri_Oct_16_15:55:11_2009-1
Content-Type: text/plain; charset=US-ASCII
>>>>> "km" == KOT MATPOCKuH <matpockuh@gmail.com> writes:
km> The time in NVRAM's clock is not synced after reboot,
km> and time difference increases after each system restart.
km> 14 Oct 18:31:27 ntpdate[963]: step time server 192.168.2.1
km> offset 343.494018 sec
[reboot]
km> 15 Oct 10:22:53 ntpdate[962]: step time server 192.168.2.1
km> offset 345.509317 sec
so you are finding two separate problems:
1. if NVRAM clock were synced after reboot, the step on 15 Oct would
be close to zero, not 300.
2. accepting that bug exists, and the NVRAM time is never updated to
system time, the step should be the same size on the 14th and
15th. Instead the nvram is gaining/losing two seconds in only 16
hours which is much worse accuracy than you expect from the
battery chip.
--pgp-sign-Multipart_Fri_Oct_16_15:55:11_2009-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)
iQCUAwUAStjPn4nCBbTaW/4dAQIxMAPxAeVZ63UXCH6a1wpRPGrJaSX/Tng3Q9Hq
aLFhRkfvqYDTF/BuTnNB0Yf0QZoHwRaMBbKse47SUetmcxRL8a0/r4smtK1+QTWD
rvqf467iI09DBDr4v1BmvpMpweH2QTHbl18f1m6q4hQv8UjEd+Pv4q2+zBW2JDQq
wqdUFkMO2A==
=F/FB
-----END PGP SIGNATURE-----
--pgp-sign-Multipart_Fri_Oct_16_15:55:11_2009-1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?oqvdifktb4.fsf>