https://support.ntp.org/bugs/show_bug.cgi?id=1075
Appears to have fixed the problem..
The PPS Width is too small, and this patch / bug report, fixes the
issue :)
On Tue, 2010-08-31 at 11:34 +0100, George Ross wrote:
> > > Have you tried running the daemon in debugging mode, per the
> > > dri
I think I was too excited too soon.
First packet appeared, subsequent packets failed :)
On Wed, 2010-09-01 at 19:14 +1200, Chris H wrote:
> https://support.ntp.org/bugs/show_bug.cgi?id=1075
>
> Appears to have fixed the problem..
>
> The PPS Width is too small, and this patch / bug report,
Have you looked at both firmware docs to insure that there is no
changes in the packet data.
I had to play with this driver to talk to a resolution SMT and just a
few changes in bits definition gave me
the same error. the driver will fail even if the error is from another
packet (secondary ti
Dave,
Looks like you got impaled on my own bug. The intent was indeed to
express the minimum headway, aka guard time (ntp_minpkt), in seconds,
not as exponent. This is so folks could specify 3 s, for instance. This
is what the configuration code assumes. On the other hand, the minimum
average
If I do this while running ntpd
while true = '1'; do echo " " > /dev/ttyS0 sleep 10; done
I get:
addto_syslog: select(): nfound=-1, error: Interrupted system call
addto_syslog: select(): nfound=-1, error: Interrupted system call
addto_syslog: select(): nfound=-1, error: Interrupted system call
a
