Date: Tue, 14 Nov 2017 14:50:38 -0800 From: Mark Millard <markmi@dsl-only.net> To: Andreas Schwarz <freebsd.asc@strcmp.org> Cc: freebsd-arm@FreeBSD.org, ian@freebsd.org Subject: Re: PINE64 - 12.0-CURRENT r324563 - ntpd can't keep time Message-ID: <4AB259A5-F00A-408F-968A-26AD8D776708@dsl-only.net> In-Reply-To: <4aff37249b6.70779c93@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> <dceb4702-8ede-aadd-17d8-ed41436955ad@restart.be> <4aff37249b6.70779c93@mail.schwarzes.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[FYI: my sysctl dev.ctl.0 is not like Andreas showed.] On 2017-Nov-14, at 2:03 PM, Andreas Schwarz <freebsd.asc@strcmp.org> = wrote: > On 14.11.17, Henri Hennebert wrote: >> On 11/13/2017 21:03, Mark Millard wrote: >>>=20 >>> So it looks like you are getting bad times from at >>> least 2 servers. Note that the other servers seem >>> fine as far as your e-mailed material goes. >>=20 >> I believe that the clock of the Pine64+ is going too fast and that = the 2=20 >> servers where polled and so show this offset/jitter. In an other=20 >> occurrence of this problem, if I wait long enough, all servers = display=20 >> huge offset. >=20 > But they step not simultaneous to this offset (which is ~300s), why = should some=20 > servers have such offset and others not?. >=20 > Can you provide your "ntpq -c rl" output? >=20 > If you disable the ntpd, what time drift do you measure per day? >=20 >> In a old version of Freebsd12, when dev.cpu.0.freq was accessible, = the=20 >> problem appear when I force the frequency to 1200. >=20 >=20 > The dev.cpu.0.freq is already there in head/current. >=20 > root@pinelot:~ # sysctl dev.cpu.0 > dev.cpu.0.freq_levels: 1200/-1 1008/-1 816/-1 648/-1 408/-1 > dev.cpu.0.freq: 408 > dev.cpu.0.%parent: cpulist0 > dev.cpu.0.%pnpinfo: name=3Dcpu@0 compat=3Darm,cortex-a53 > dev.cpu.0.%location: > dev.cpu.0.%driver: cpu > dev.cpu.0.%desc: Open Firmware CPU >=20 > root@pinelot:~ # uname -v > FreeBSD 12.0-CURRENT #0 r325561: Thu Nov 9 11:24:55 CET 2017 = root@pinelot.schwarzes.net:/usr/obj/usr/src/arm64.aarch64/sys/PINE64-ASC I'm not the one with the clock problem but I'll note that the -r325700 Pine64+ 2GB with a production-style kernel (not debug) that I'm using has rather different dev.cpu.0 output from sysctl as far as "freq" goes (no such): # uname -apKU FreeBSD pine64 12.0-CURRENT FreeBSD 12.0-CURRENT r325700M arm64 = aarch64 1200053 1200053 # sysctl dev.cpu.0 dev.cpu.0.%parent: cpulist0 dev.cpu.0.%pnpinfo: name=3Dcpu@0 compat=3Darm,cortex-a53 dev.cpu.0.%location:=20 dev.cpu.0.%driver: cpu dev.cpu.0.%desc: Open Firmware CPU Looking, /usr/ports -r447122 moved sysutils/u-boot-pine64 over to be us-boot-master based back on 2017-Aug-2. May be we have differing: u-boot-sunxi-with-spl.bin vintages dd'd to seek=3D8 on the sdcards? Some other difference someplace else? =3D=3D=3D Mark Millard markmi at dsl-only.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AB259A5-F00A-408F-968A-26AD8D776708>