Yo All! Long time, not much traffic here.
I have been looking at linuxptp again. Some old issues, and some
new ones.
Old issue: I reported the Intel i217 ethernet card broken for hardware
and software PTP back in 2017. Still broken.
New issue, when I run ptp4l in hardware mode, master and slave,
connected to ntpd, I get these errors in the logs:
2020-05-12T18:14:08 ntpd[8126]: SHM(2): stale/bad receive time, delay=-36s
When I convert both ends to software mode, that goes away. But the
accuracy is not good. Something under 10 micro seconds jitter.
Any way to get hardware mode working?
My master is running this:
ptp4l -i eno1 -S
My slave is running this:
ptp4l -i eno2 -s --clock_servo ntpshm --ntpshm_segment 2 -S
And the slave sees the master:
# pmc -u -b 0 'GET TIME_STATUS_NP'
sending: GET TIME_STATUS_NP
002590.fffe.f355db-0 seq 0 RESPONSE MANAGEMENT TIME_STATUS_NP
master_offset -9217
ingress_time 1589340375337427409
cumulativeScaledRateOffset +0.000000000
scaledLastGmPhaseChange 0
gmTimeBaseIndicator 0
lastGmPhaseChange 0x0000'0000000000000000.0000
gmPresent true
gmIdentity ac1f6b.fffe.026d32
If I run the masster is software mode, and the slave in hardware mode
like this:
ptp4l -i eno2 -s --clock_servo ntpshm --ntpshm_segment 2
I get this in the slave ntpd log:
2020-05-12T20:27:54 ntpd[9090]: SHM(2): stale/bad receive time, delay=18s
Any ideas how to run in hardware mode and get ntpd/shm to work?
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can't measure it, you can't improve it." - Lord Kelvin
pgpPVmjMMuRBm.pgp
Description: OpenPGP digital signature
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
