Crazy clock

[Atte Peltomaki]

> > > > > DragonFlyBSD doesn't seem to be able to keep the date, and it has been
> > > > > so for quite a while now. Is there a fix in horizon, or should I set up
> > > > > a cronjob for ntpdate that runs every minute? >:)
> > > > 
> > > > Can you be a bit more verbose.
> > > > 
> > > > a) Are you using VESA or APM or other stuff which results in BIOS calls?
> > > > b) Are you using SMP / HTT?
> > > > c) Your machine is ... with verbose dmesg ...
> > > 
> > > I'm not using APM, probably not VESA, but I am using ACPI. You ask
> > > difficult, I don't really know which drivers need BIOS calls :)
> > > 
> > > My box is dual p3, see below for dmesg.
> > 
> > Are you running X when the problems occur? Does it change if you are at the
> > console? Sorry, I know this is difficult :)
> 
> option. I'm right now recompiling with the TIMER_USE_1 option.. Oh and

Well, well. It seems the TIMER_USE_1 option in the kernel has made the
clock a lot more stable! I only got a half a second offset in a 5min
waiting period between ntpdate's. Before it was around few hundred ;)

I'll keep running this for a while and see how it goes.


-Atte