Subject: Re: LP64 bug of ntp? (Re: mk48txx(4) tod clock driver cleanup)
To: None <M.Drochner@fz-juelich.de>
From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
List: port-sparc64
Date: 11/16/2003 02:56:22
In article <200311101131.MAA0000255227@zel459.zel.kfa-juelich.de>
M.Drochner@fz-juelich.de wrote:
> > % ntpdc -c loop
> > offset: -0.063699 s
> > frequency: -500.000 ppm
>
> This doesn't happen on alpha. Probably an endian thing, but
> the (4.2) code looks OK at a first glance. (NTOHL_FP uses ntohl
> internally)
Now my U5 shows:
---
# ntpdc -c loop
offset: -0.023243 s
frequency: -496.981 ppm
poll adjust: 10
watchdog timer: 71 s
---
This means crystal clock used on my U5 has actually bad accuracy?
Or "using %tick at 269MHz as system clock" is the problem?
---
Izumi Tsutsui
tsutsui@ceres.dti.ne.jp