From: "Gene Heskett" <gene.heskett@xxxxxxxxxxx>
> >Also, is your BIOS clock set to UTC or local time? This makes a
> >difference from my experience. One test to make is to check the
> > time in bios, shut the computer down and then check the time in
> > bios after an hour. This will give you an indication if the
> > hardware (bios) clock is running and how precise it is. If it is
> > running pretty accurate, then I would suspect that the software
> > clock is running fast/slow due to the drift setting.
> >
> >I used to use "hwclock" in the past.
>
> I too had the fast clock problem, and by tickling the tick counter
> with the 'tickadj' command, was able to stay well within 1 second per
> hour. The bare command will return the current tick value, default
> is 10000, but I'm curently setting it at 9926 for accurate time
> keeping. This seems to be 2.6 problem as the default is pretty close
> on a 2.4.29 system running on an elderly TYAN mobo at 500mhz.
Also try booting with "noapic" and "nolapic" options. (I'd LOVE to
know why the APIC screws up the ntp operations.)
{^_^}
