[LinuxPPS] Why is my ATOM clock a falseticker?

Hal V. Engel hvengel at astound.net
Mon Feb 2 05:36:27 CET 2009


On Sunday 01 February 2009 05:03:17 pm Cirilo Bernardo wrote:
> On 2/2/09, Paul Simons <paul at thesimonet.org> wrote:
> > Surprizingly, it is CONFIG_HZ=250.  Is that the default?  Should I change
> > it to 100?
> >
> > On 01/31/2009, "Cirilo Bernardo" stated:
>
> [snip]
>
> >  > What is your setting for CONFIG_HZ in the kernel options?
> >  >
> >  > - Cirilo
>
> There was some discussion a few months ago about the Linux CONFIG_HZ
> and problems associated with it.  I can't recall the specific issues
> and can't find the discussions in my email.  You might try rebuilding
> with CONFIG_HZ_100=y and see if that fixes the problem; if it does
> then we definitely have a kernel problem.
>
> - Cirilo

My experience is that 100Hz works better but the OPs clock was off by amost 
0.5 seconds and the difference between 100Hz and 250Hz was on the order of 
perhaps 50 microseconds for me.  So I don't think this is the issue with the 
large offsets.

Hal



More information about the LinuxPPS mailing list