Re: [Linuxptp-users] sanity_freq_limit

[Daniel Le <dan...@ex...>]

Below is my ptp4l config file.

$cat ptp4l.conf
[global]
domainNumber                   0
slaveOnly                               1
priority1                                  128
priority2                                  128
clockClass                               248
clockAccuracy                        254
offsetScaledLogVariance  65535
freq_est_interval                 1
time_stamping                      software
tx_timestamp_timeout     1
logging_level                         6
verbose                                    0
use_syslog                              1
summary_interval               0
[eth2]
delay_mechanism                  E2E
network_transport                UDPv4
delayAsymmetry                    0
logAnnounceInterval            1
logSyncInterval                        0
logMinDelayReqInterval      0
logMinPdelayReqInterval    0
announceReceiptTimeout   3
syncReceiptTimeout              0
delay_filter                                moving_average
delay_filter_length                10
path_trace_enabled              0
fault_reset_interval              4

And the log messages at start in "good case". I didn't save the log where my system time was initially off a few minutes, though I remember the master offsets were above 200000000. I'll need to reproduce such condition in order to capture the exact log messages.

ptp4l[792695.130]: port 1: get_ts_info not supported
ptp4l[792695.131]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[792695.131]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[792697.130]: port 1: new foreign master 00b0ae.fffe.02d103-1
ptp4l[792701.130]: selected best master clock 00b0ae.fffe.02d103
ptp4l[792701.130]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[792701.991]: port 1: minimum delay request interval 2^-7
ptp4l[792703.068]: master offset   -1555032 s0 freq  -13556 path delay     -5078
ptp4l[792704.068]: master offset   -1563606 s0 freq  -13556 path delay      1196
ptp4l[792705.068]: master offset   -1565962 s0 freq  -13556 path delay      1212
ptp4l[792706.068]: master offset   -1568258 s0 freq  -13556 path delay      1204
ptp4l[792707.068]: master offset   -1570542 s0 freq  -13556 path delay      1184
ptp4l[792708.068]: master offset   -1553450 s0 freq  -13556 path delay     -5284
ptp4l[792709.068]: master offset   -1562224 s0 freq  -13556 path delay      1186
ptp4l[792710.068]: master offset   -1564536 s0 freq  -13556 path delay      1198
ptp4l[792711.068]: master offset   -1566872 s0 freq  -13556 path delay      1194
ptp4l[792712.068]: master offset   -1569158 s0 freq  -13556 path delay      1180
ptp4l[792713.068]: master offset   -1571482 s0 freq  -13556 path delay      1196
ptp4l[792714.068]: master offset   -1554204 s0 freq  -13556 path delay     -5330
ptp4l[792715.068]: master offset   -1563042 s0 freq  -13556 path delay      1204
ptp4l[792716.068]: master offset   -1565384 s0 freq  -13556 path delay      1210
ptp4l[792717.068]: master offset   -1567668 s0 freq  -13556 path delay      1194
ptp4l[792718.068]: master offset   -1569978 s0 freq  -13556 path delay      1200
ptp4l[792719.068]: master offset   -1554292 s1 freq  -13510 path delay     -4826
ptp4l[792720.068]: master offset   -1556592 s2 freq -170726 path delay     -4826
ptp4l[792720.068]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[792721.068]: master offset   -1564970 s2 freq -173128 path delay      1212
ptp4l[792722.068]: master offset   -1567220 s2 freq -174921 path delay      1162
ptp4l[792723.068]: master offset   -1569548 s2 freq -176723 path delay      1186
ptp4l[792724.068]: master offset   -1571854 s2 freq -178525 path delay      1188
ptp4l[792725.068]: master offset    -523684 s2 freq  -74232 path delay   -348970

/Daniel

-----Original Message-----
From: Miroslav Lichvar [mailto:mli...@re...] 
Sent: Thursday, June 18, 2015 4:20 AM
To: Daniel Le
Cc: Lin...@li...
Subject: Re: [Linuxptp-users] sanity_freq_limit

On Thu, Jun 18, 2015 at 07:18:53AM +0000, Daniel Le wrote:
> > On Jun 18, 2015, at 2:58 AM, Miroslav Lichvar <mli...@re...> wrote:
> > 
> >> On Thu, Jun 18, 2015 at 01:58:13AM +0000, Daniel Le wrote:
> >> Additionally, in slave clock operation and software time stamping mode, how (and where in the code) ptp4l can be forced to step the system clock with the time it first receives from a grandmaster clock?
> > 
> > ptp4l should do that by default, it's set by the 
> > first_step_threshold option.
> 
> Somehow when my system clock is initially (for example after a reboot) off the GM time by a couple of minutes, the master offset is huge and ptp4l takes hours to converge.

That's odd. Can you post your ptp4l config and log when it starts?

--
Miroslav Lichvar