I start phc2sys with the following arguments ...
phc2sys -a -r -l6 -n1 -u240 -E linreg
The ptp4l config file ...
[global]
#
# Default Data Set
#
twoStepFlag 1
slaveOnly 1
priority1 128
priority2 128
domainNumber 1
clockClass 248
clockAccuracy 0xFE
offsetScaledLogVariance 0xFFFF
free_running 0
freq_est_interval 1
dscp_event 0
dscp_general 0
#
# Port Data Set
#
logAnnounceInterval 0
logSyncInterval 2
logMinDelayReqInterval 2
logMinPdelayReqInterval 0
announceReceiptTimeout 3
syncReceiptTimeout 0
delayAsymmetry 0
fault_reset_interval 4
neighborPropDelayThresh 20000000
#
# Run time options
#
assume_two_step 0
logging_level 6
path_trace_enabled 0
follow_up_info 0
tx_timestamp_timeout 100
use_syslog 1
verbose 0
summary_interval 8
kernel_leap 0
# was 1
check_fup_sync 0
#
# Servo Options
#
pi_proportional_const 0.0
pi_integral_const 0.0
pi_proportional_scale 0.0
pi_proportional_exponent -0.3
pi_proportional_norm_max 0.7
pi_integral_scale 0.0
pi_integral_exponent 0.4
pi_integral_norm_max 0.3
step_threshold 1.0
first_step_threshold 0.00002
max_frequency 900000000
clock_servo linreg
sanity_freq_limit 200000000
ntpshm_segment 0
#
# Transport options
#
transportSpecific 0x0
udp_ttl 128
#
# Default interface options
#
network_transport UDPv4
delay_mechanism E2E
time_stamping hardware
tsproc_mode filter
delay_filter moving_median
delay_filter_length 10
egressLatency 0
ingressLatency 0
boundary_clock_jbod 0
[eth0]
hybrid_e2e 1
One board did this after 33 hours ...
Jul 28 00:47:22 buildroot user.notice ptp4l: [118806.334] selected best master
clock 000cec.fffe.0a0f8d
Jul 28 00:47:29 buildroot user.info ptp4l: [118813.834] rms 17 max 82 freq
-355 +/- 1 delay 3338 +/- 4
Jul 28 00:48:17 buildroot user.info phc2sys: [118861.985] rms 28 max 65
freq -355 +/- 1 delay 1179 +/- 11
Jul 28 00:51:45 buildroot user.info ptp4l: [119069.834] rms 16 max 48 freq
-355 +/- 1 delay 3343 +/- 3
Jul 28 00:52:17 buildroot user.info phc2sys: [119102.033] rms 27 max 66
freq -354 +/- 1 delay 1178 +/- 9
Jul 28 00:56:01 buildroot user.info ptp4l: [119325.834] rms 16 max 48 freq
-355 +/- 1 delay 3340 +/- 3
Jul 28 00:56:04 buildroot user.notice ptp4l: [119328.334] selected best master
clock 000cec.fffe.0a0f8d
Jul 28 00:56:17 buildroot user.info phc2sys: [119342.097] rms 28 max 62
freq -354 +/- 1 delay 1178 +/- 10
Jul 28 01:00:17 buildroot user.info ptp4l: [119581.877] rms 17 max 60 freq
-355 +/- 2 delay 3341 +/- 4
Jul 28 01:00:18 buildroot user.info phc2sys: [119582.164] rms 66337921 max
999999964 freq +6447547 +/- 24465135 delay 1179 +/- 10
Jul 28 01:04:18 buildroot user.info phc2sys: [119822.202] rms 63546018 max
95547870 freq -32621219 +/- 91570846 delay 1177 +/- 10
Jul 28 01:04:33 buildroot user.info ptp4l: [119837.836] rms 16 max 49 freq
-355 +/- 2 delay 3341 +/- 4
Jul 28 01:08:18 buildroot user.info phc2sys: [120062.256] rms 110632817 max
153063095 freq +78018721 +/- 58697459 delay 1178 +/- 9
Jul 28 01:08:49 buildroot user.info ptp4l: [120093.779] rms 15 max 46 freq
-355 +/- 1 delay 3340 +/- 5
Jul 28 01:12:18 buildroot user.info phc2sys: [120302.297] rms 167801527 max
217811940 freq -82002338 +/- 53443770 delay 1176 +/- 8
Jul 28 01:13:05 buildroot user.info ptp4l: [120349.818] rms 17 max 48 freq
-355 +/- 1 delay 3342 +/- 4
Jul 28 01:13:32 buildroot user.notice ptp4l: [120376.403] selected best master
clock 000cec.fffe.0a0f8d
Jul 28 01:16:18 buildroot user.info phc2sys: [120542.352] rms 197699240 max
284534316 freq +48623430 +/- 85140229 delay 1180 +/- 10
I'm checking that there are no system factors causing this.
We now have 54 boards in the network and I'd estimate that this happens on
three boards every 24 hours.
Ian T.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
