In article <20031103092338.A16799@sec.sprint.net>
rquinn@sec.sprint.net wrote:

>  Could this change have caused an error like this?  This morning my Ultra10
> gave a bogus NTP time warning shortly after I booted my new sparc64-current
> kernel:
> 
> Nov  3 07:23:52 struck /netbsd: root file system type: ffs
> Nov  3 07:23:52 struck savecore: no core dump
> Nov  3 07:23:53 struck ntpd[402]: ntpd 4.0.99i Tue Oct 28 21:27:54 EST 2003 (1)
>  [...]
> Nov  3 07:27:24 struck ntpd[402]: time reset 1.405487 s
> Nov  3 07:27:24 struck ntpd[402]: kernel pll status change 41
> Nov  3 07:38:09 struck ntpd[402]: time error 2069188655 over 1000 seconds; set clock manually

Could you try to boot an old kernel after the new kernel (or vice versa)?

If the kernel doesn't print any WARNINGs about clock on mountroot,
I don't think mk48txx changes (which are only internal API changes)
have any problem and I'm afraid ntp would have some bugs (around LP64BE?)
because ntpd itself shows correct date before the time error message.
---
Izumi Tsutsui
tsutsui@ceres.dti.ne.jp