[9848.472]: selected best master clock 3c5282.fffe.5abe30
I think that means ptp4l is not receiving or is ignoring the PTP
messages. Maybe it's a different PTP domain?
Running ptp4l in strace and/or with -l 7 might give us more clues.
--
Miroslav Lichvar
-
"ptp4l -H -i eno1 -s" ?
Do you see any ptp-event and ptp-general messages in tcpdump output?
It might be a firewall issue.
--
Miroslav Lichvar
--
Check out the vibrant tech community on one of the world's most
en
On Mon, Oct 30, 2017 at 08:07:49PM -0700, Gary E. Miller wrote:
> Miroslav Lichvar <mlich...@redhat.com> wrote:
> > Is there a "LISTENING to UNCALIBRATED on RS_SLAVE" message in the log?
> > If not, ptp4l is probably not receiving master's messages, e.g. due to
>
pcoming rollover issue.
Hm, which rollover issue? The fields are not supposed to have values
outside interval [0, 9]. ptp4l and phc2sys follow that, so it
does not matter if the fields are declared as signed or unsi
/rtnl.c
> +++ b/rtnl.c
> @@ -17,6 +17,7 @@
> * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
> */
> #include
> +#include
> #include
> #include
> #include
It would be nice to fix this too.
Thanks,
--
Miroslav Lichvar
--
ogs it seems the problem is that clock_adjtime() returns
zero ticks instead of 1 for the REALTIME clock. I suspect it's a
kernel or possibly glibc bug.
--
Miroslav Lichvar
--
Check out the vibrant tech community on one of the world's
and libc is this? Can you please check what value
has the realtime_hz variable in clockadj.c?
--
Miroslav Lichvar
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://s
rces like NTP. It is
recommended by the Enterprise profile. You can easily do this with the
timemaster program from linuxptp.
--
Miroslav Lichvar
--
Check out the vibrant tech community on one of the world's most
enga
shouldn't, possibly triggering some feedback loop between ptp4l and
phc2sys.
What HW/driver and linuxptp version is this? Can you please post your
ptp4l config and command-line options used for ptp4l and phc2sys?
Having full logs with
phc2sys doesn't care which servo is selected. With the
ntpshm servo, it's another process controlling the clock instead of
phc2sys. If timemaster started phc2sys without -r, it wouldn't try to
synchronize the system clock and the ntpshm servo wouldn't write
ld use HW timestamping on eth0, but if there is no master
in domain 1 on your network, it wouldn't do anything.
--
Miroslav Lichvar
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot
left side you have one 3.3V pin and two ground pins.
>
> The signal level is CMOS, and there is no ESD protection at all.
> Be careful!
Great, thanks for the information. I'll see if I can get an i210 and
connect a GPS PPS signal to it. The PPS is at the TTL level so I guess
I just
is that wise.
It depends on the kernel overcommit configuration. In the default
configuration getting NULL is unlikely, but that doesn't mean it
should result in a segfault. I'm just not convinced there is any point
in trying to recover from that.
--
Miroslav Lichvar
) when the allocation fails, and use the
wrappers everywhere in the code.
--
Miroslav Lichvar
--
___
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https
to be synchronized by chronyd,
using a PTP domain as the only time source and serving time over
NTP to clients, the timemaster configuration file could be:
[ptp_domain 0]
interfaces eth0
[chrony.conf]
makestep 1 3
rtcsync
allow
driftfile /var/lib/chrony/drift
--
Miroslav Lichvar
time with the LOCAL driver/local
stratum option with no other time sources listed in the config.
For example:
ptp4l -i eth0
phc2sys -a -r -r
chronyd 'local stratum 1' 'allow'
--
Miroslav Lichvar
to configure timemaster to serve local time
over PTP. phc2sys would need to allow that first.
--
Miroslav Lichvar
--
___
Linuxptp-users mailing list
Linuxptp-users
% is a safe value for SW
timestamping. If you see clockcheck warning messages, it's probably a
bug in the kernel/driver. With HW timestamping a limit of a few
hundreds of ppm should be enough to cover the frequency offset between
a typical system clock and PTP clock.
--
Miroslav Lichvar
unstable clocks or large
jitters, with careful PI configuration keeping the frequency error
below 50 ppb shouldn't be difficult even at the default 1Hz sync rate.
--
Miroslav Lichvar
--
Dive into the World of Parallel
.
That option needs to be set on master. On slaves it sets only the
initial value, after receiving first delay response message they will
switch to the value announced by the master.
--
Miroslav Lichvar
--
Dive into the World
than summary_interval (1
second by default). See the summary_interval description in the ptp4l
man page.
--
Miroslav Lichvar
--
___
Linuxptp-users mailing list
Linuxptp-users
201 - 221 of 221 matches
Mail list logo