Thread: [Linuxptp-users] inconsistent Message rates
PTP IEEE 1588 stack for Linux
Brought to you by:
rcochran
Menu
▾
▴
linuxptp-users
|
From: Gururaj B. <gur...@gm...> - 2022-08-08 09:05:20
|
Hello, I have been using ptp4l with the below config file. What I noticed was - In Follower mode, when 'Announce Interval' set to more than 4Hz (4 messages per second config value -2) and 'Sync Interval' set to more than 8Hz (8messages per second config value -3), I see ptp4l lock status toggling between "Faulty" to "ÜnCalibrated" to "Slave" to "Faulty" and cycle repeats. The lock status is not getting stabilized. Below is the config file I'm using to run ptp4l in Follower mode. *[global]twoStepFlag 1slaveOnly 1masterOnly 0priority1 128priority2 128domainNumber 120maxStepsRemoved 252clockClass 248clockAccuracy 0xFEoffsetScaledLogVariance 0xFFFFfree_running 0freq_est_interval 1dscp_event 0dscp_general 0clock_type OClogAnnounceInterval -7logSyncInterval -7logMinDelayReqInterval -3logMinPdelayReqInterval 0announceReceiptTimeout 3syncReceiptTimeout 0delayAsymmetry 0fault_reset_interval 4neighborPropDelayThresh 20000000assume_two_step 0logging_level 6path_trace_enabled 0follow_up_info 0hybrid_e2e 0tx_timestamp_timeout 1use_syslog 1verbose 1summary_interval -3kernel_leap 1check_fup_sync 0pi_proportional_const 0pi_integral_const 0pi_proportional_scale 0pi_proportional_exponent -0.3pi_proportional_norm_max 0.7pi_integral_scale 0pi_integral_exponent 0.4pi_integral_norm_max 0.3step_threshold 0first_step_threshold 0.00002max_frequency 900000000clock_servo pisanity_freq_limit 200000000ntpshm_segment 0transportSpecific 0ptp_dst_mac 01:1B:19:00:00:00p2p_dst_mac 01:80:C2:00:00:0Eudp_ttl 64udp6_scope 0x0Euds_address /var/run/ptp4l@eth1network_transport UDPv4delay_mechanism E2Etime_stamping hardwaretsproc_mode filterdelay_filter moving_mediandelay_filter_length 10egressLatency 0ingressLatency 0boundary_clock_jbod 0timeSource 0xA0manufacturerIdentity 00:00:00[fm1-mac10]* Could you please let me know if any of the parameters in this config item could be causing this issue? OR if this issue is known and some fix available in the latest ptp4l version? Thanks in advance. -Guru |
|
From: Miroslav L. <mli...@re...> - 2022-08-08 09:31:58
|
On Mon, Aug 08, 2022 at 02:34:32PM +0530, Gururaj Badiger wrote: > Hello, > > I have been using ptp4l with the below config file. What I noticed was - > > In Follower mode, when 'Announce Interval' set to more than 4Hz (4 messages > per second config value -2) and 'Sync Interval' set to more than 8Hz > (8messages per second config value -3), I see ptp4l lock status toggling > between "Faulty" to "ÜnCalibrated" to "Slave" to "Faulty" and cycle > repeats. The lock status is not getting stabilized. Is the server configured with the same logAnnounceInterval? If the client had a shorter interval, it would time out and lead to the uncalibrated state. I'm not sure about faulty. Can you post the client log? -- Miroslav Lichvar |
|
From: Gururaj B. <gur...@gm...> - 2022-08-08 10:00:22
|
Is the server configured with the same logAnnounceInterval?: <guru> Do you mean both Leader and Follower config files should be configured with the same Sync and Announce interval values? Client log meaning, are you asking console logs on Leader? <guru> Here is the console log on Leader shell: *root@TSG:~# ptp4l -i eth1 -m -f /home/root/ptp-manager/source/linuxptp_config_0.confptp4l[249823.075]: ioctl SIOCETHTOOL failed: No such deviceptp4l[249823.076]: selected /dev/ptp0 as PTP clockptp4l[249823.076]: port 2: get_ts_info not supportedptp4l[249823.088]: port 1: INITIALIZING to LISTENING on INIT_COMPLETEptp4l[249823.093]: ioctl SIOCGIFHWADDR failed: No such deviceptp4l[249823.098]: ioctl SIOCGIFINDEX failed: No such deviceptp4l[249823.098]: port 2: INITIALIZING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)ptp4l[249823.098]: port 0: INITIALIZING to LISTENING on INIT_COMPLETEptp4l[249823.854]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRESptp4l[249823.854]: selected local clock ced607.fffe.20f9e8 as best masterptp4l[249823.854]: port 1: assuming the grand master roleptp4l[249823.855]: port 2: assuming the grand master roleptp4l[249886.491]: timed out while polling for tx timestampptp4l[249886.491]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bugptp4l[249886.491]: port 1: send sync failedptp4l[249886.491]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)ptp4l[249902.504]: port 1: FAULTY to LISTENING on INIT_COMPLETEptp4l[249903.366]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRESptp4l[249903.367]: selected local clock ced607.fffe.20f9e8 as best masterptp4l[249903.367]: port 1: assuming the grand master roleptp4l[249903.367]: port 2: assuming the grand master roleptp4l[249952.501]: timed out while polling for tx timestampptp4l[249952.501]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bugptp4l[249952.501]: port 1: send sync failedptp4l[249952.501]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)ptp4l[249968.513]: port 1: FAULTY to LISTENING on INIT_COMPLETEptp4l[249969.288]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRESptp4l[249969.288]: selected local clock ced607.fffe.20f9e8 as best masterptp4l[249969.288]: port 1: assuming the grand master roleptp4l[249969.288]: port 2: assuming the grand master roleptp4l[250080.057]: timed out while polling for tx timestampptp4l[250080.057]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bugptp4l[250080.057]: port 1: send sync failedptp4l[250080.057]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)ptp4l[250096.075]: port 1: FAULTY to LISTENING on INIT_COMPLETEptp4l[250096.969]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRESptp4l[250096.969]: selected local clock ced607.fffe.20f9e8 as best masterptp4l[250096.969]: port 1: assuming the grand master roleptp4l[250096.969]: port 2: assuming the grand master roleptp4l[250137.727]: timed out while polling for tx timestampptp4l[250137.727]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bugptp4l[250137.727]: port 1: send sync failedptp4l[250137.727]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)ptp4l[250153.739]: port 1: FAULTY to LISTENING on INIT_COMPLETEptp4l[250154.646]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRESptp4l[250154.646]: selected local clock ced607.fffe.20f9e8 as best masterptp4l[250154.646]: port 1: assuming the grand master roleptp4l[250154.646]: port 2: assuming the grand master roleptp4l[250165.024]: timed out while polling for tx timestampptp4l[250165.024]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bugptp4l[250165.024]: port 1: send sync failedptp4l[250165.024]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)ptp4l[250181.042]: port 1: FAULTY to LISTENING on INIT_COMPLETEptp4l[250181.837]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRESptp4l[250181.837]: selected local clock ced607.fffe.20f9e8 as best masterptp4l[250181.838]: port 1: assuming the grand master roleptp4l[250181.838]: port 2: assuming the grand master roleptp4l[250183.214]: timed out while polling for tx timestampptp4l[250183.214]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bugptp4l[250183.214]: port 1: send sync failedptp4l[250183.214]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)ptp4l[250199.245]: port 1: FAULTY to LISTENING on INIT_COMPLETEptp4l[250200.098]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRESptp4l[250200.098]: selected local clock ced607.fffe.20f9e8 as best masterptp4l[250200.099]: port 1: assuming the grand master roleptp4l[250200.099]: port 2: assuming the grand master roleptp4l[250357.626]: timed out while polling for tx timestampptp4l[250357.626]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bugptp4l[250357.626]: port 1: send sync failedptp4l[250357.626]: port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)* *ptp4l[250373.638]: port 1: FAULTY to LISTENING on INIT_COMPLETE* Regards, Guru On Mon, 8 Aug 2022 at 15:01, Miroslav Lichvar <mli...@re...> wrote: > On Mon, Aug 08, 2022 at 02:34:32PM +0530, Gururaj Badiger wrote: > > Hello, > > > > I have been using ptp4l with the below config file. What I noticed was - > > > > In Follower mode, when 'Announce Interval' set to more than 4Hz (4 > messages > > per second config value -2) and 'Sync Interval' set to more than 8Hz > > (8messages per second config value -3), I see ptp4l lock status toggling > > between "Faulty" to "ÜnCalibrated" to "Slave" to "Faulty" and cycle > > repeats. The lock status is not getting stabilized. > > Is the server configured with the same logAnnounceInterval? If the > client had a shorter interval, it would time out and lead to > the uncalibrated state. I'm not sure about faulty. Can you post the > client log? > > -- > Miroslav Lichvar > > |
|
From: Miroslav L. <mli...@re...> - 2022-08-08 10:09:06
|
On Mon, Aug 08, 2022 at 03:29:26PM +0530, Gururaj Badiger wrote: > Is the server configured with the same logAnnounceInterval?: > <guru> Do you mean both Leader and Follower config files should be > configured with the same Sync and Announce interval values? The announce interval needs to be the same in the whole PTP domain. The sync interval doesn't have to be, but usually it is. > Client log meaning, are you asking console logs on Leader? I think client is follower in the leader/follower terminology (we use the server/client terminology in linuxptp). > <guru> Here is the console log on Leader shell: Your log shows many tx timestamp timeouts, so that needs to be resolved first. What hardware and driver are you using? -- Miroslav Lichvar |
|
From: Gururaj B. <gur...@gm...> - 2022-08-08 10:28:03
|
On Mon, 8 Aug 2022 at 15:38, Miroslav Lichvar <mli...@re...> wrote: > On Mon, Aug 08, 2022 at 03:29:26PM +0530, Gururaj Badiger wrote: > > Is the server configured with the same logAnnounceInterval?: > > <guru> Do you mean both Leader and Follower config files should be > > configured with the same Sync and Announce interval values? > > The announce interval needs to be the same in the whole PTP domain. > The sync interval doesn't have to be, but usually it is. > <guru> I tried to keep both Client and Server same but I didnt see any > improvement. > > > Client log meaning, are you asking console logs on Leader? > > I think client is follower in the leader/follower terminology (we use > the server/client terminology in linuxptp). > ok Client log is as below: ptp4l[252579.286]: port 2: master state recommended in slave only mode ptp4l[252579.286]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252579.786]: selected local clock ced607.fffe.20f9e8 as best master ptp4l[252579.786]: port 2: assuming the grand master role ptp4l[252579.786]: port 2: master state recommended in slave only mode ptp4l[252579.786]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252580.182]: selected local clock ced607.fffe.20f9e8 as best master ptp4l[252580.182]: port 2: assuming the grand master role ptp4l[252580.182]: port 2: master state recommended in slave only mode ptp4l[252580.182]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252580.346]: selected best master clock 080011.fffe.21b927 ptp4l[252580.346]: updating UTC offset to 37 ptp4l[252580.346]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE ptp4l[252580.346]: port 2: master state recommended in slave only mode ptp4l[252580.346]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252580.373]: port 1: minimum delay request interval 2^-4 ptp4l[252580.534]: rms 1659701576982259968 max 1659701576982259968 freq +0 +/- 0 delay 7588 +/- 0 ptp4l[252580.659]: rms 1659701576982259968 max 1659701576982259968 freq -24 +/- 24 delay 7625 +/- 5 ptp4l[252580.722]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED ptp4l[252580.784]: rms 1890 max 2008 freq -3367 +/- 109 delay 7613 +/- 0 ptp4l[252580.908]: rms 1493 max 1598 freq -3042 +/- 107 delay 7612 +/- 0 ptp4l[252581.034]: rms 1101 max 1185 freq -2647 +/- 92 delay 7604 +/- 5 ptp4l[252581.156]: port 1: SLAVE to LISTENING on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES ptp4l[252581.156]: selected local clock ced607.fffe.20f9e8 as best master ptp4l[252581.156]: port 2: assuming the grand master role ptp4l[252581.156]: port 2: master state recommended in slave only mode ptp4l[252581.156]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252581.595]: selected local clock ced607.fffe.20f9e8 as best master ptp4l[252581.595]: port 2: assuming the grand master role ptp4l[252581.595]: port 2: master state recommended in slave only mode ptp4l[252581.595]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252581.986]: selected local clock ced607.fffe.20f9e8 as best master ptp4l[252581.986]: port 2: assuming the grand master role ptp4l[252581.986]: port 2: master state recommended in slave only mode ptp4l[252581.986]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252582.346]: selected best master clock 080011.fffe.21b927 ptp4l[252582.346]: updating UTC offset to 37 ptp4l[252582.346]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE ptp4l[252582.346]: port 2: master state recommended in slave only mode ptp4l[252582.346]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252582.471]: rms 1820 max 2447 freq +433 +/- 2732 delay 7574 +/- 38 ptp4l[252582.471]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED ptp4l[252582.597]: rms 2137 max 2258 freq +2983 +/- 102 delay 7590 +/- 0 ptp4l[252582.722]: rms 1720 max 1779 freq +2674 +/- 15 delay 7652 +/- 6 ptp4l[252582.846]: rms 1379 max 1453 freq +2415 +/- 58 delay 7671 +/- 0 ptp4l[252582.890]: port 1: SLAVE to LISTENING on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES ptp4l[252582.890]: selected local clock ced607.fffe.20f9e8 as best master ptp4l[252582.890]: port 2: assuming the grand master role ptp4l[252582.890]: port 2: master state recommended in slave only mode ptp4l[252582.890]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252583.390]: selected local clock ced607.fffe.20f9e8 as best master ptp4l[252583.390]: port 2: assuming the grand master role ptp4l[252583.390]: port 2: master state recommended in slave only mode ptp4l[252583.390]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252583.869]: selected local clock ced607.fffe.20f9e8 as best master ptp4l[252583.869]: port 2: assuming the grand master role ptp4l[252583.869]: port 2: master state recommended in slave only mode ptp4l[252583.870]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252584.247]: selected local clock ced607.fffe.20f9e8 as best master ptp4l[252584.247]: port 2: assuming the grand master role ptp4l[252584.247]: port 2: master state recommended in slave only mode ptp4l[252584.247]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252584.346]: selected best master clock 080011.fffe.21b927 ptp4l[252584.346]: updating UTC offset to 37 ptp4l[252584.346]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE ptp4l[252584.346]: port 2: master state recommended in slave only mode ptp4l[252584.346]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252584.513]: clockcheck: clock jumped backward or running slower than expected! ptp4l[252584.534]: rms 2538 max 2634 freq +2357 +/- 0 delay 7678 +/- 4 ptp4l[252584.659]: clockcheck: clock jumped forward or running faster than expected! ptp4l[252584.660]: rms 2829 max 2880 freq +2357 +/- 0 delay 7676 +/- 2 ptp4l[252584.787]: port 1: UNCALIBRATED to LISTENING on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES ptp4l[252584.788]: selected local clock ced607.fffe.20f9e8 as best master ptp4l[252584.788]: port 2: assuming the grand master role ptp4l[252584.788]: port 2: master state recommended in slave only mode ptp4l[252584.788]: port 2: defaultDS.priority1 probably misconfigured ptp4l[252585.213]: selected local clock ced607.fffe.20f9e8 as best master ptp4l[252585.213]: port 2: assuming the grand master role ptp4l[252585.213]: port 2: master state recommended in slave only mode ptp4l[252585.213]: port 2: defaultDS.priority1 probably misconfigured > <guru> Here is the console log on Leader shell: > > Your log shows many tx timestamp timeouts, so that needs to be > resolved first. What hardware and driver are you using? > <guru> I'm not if I understand this question. Is there a command to get > the driver info? > -- > Miroslav Lichvar > > |
|
From: Gururaj B. <gur...@gm...> - 2022-08-09 08:25:47
|
Hi Miroslav Lichvar, Here is the HW and Driver info, HW: ARMv8 Cortex-A53 processor (quad-core) in the Stratix10 SoC FPGA Driver: intel_fpga_qse_ll (10gb/s) -Guru On Mon, 8 Aug 2022 at 15:57, Gururaj Badiger <gur...@gm...> wrote: > > > On Mon, 8 Aug 2022 at 15:38, Miroslav Lichvar <mli...@re...> wrote: > >> On Mon, Aug 08, 2022 at 03:29:26PM +0530, Gururaj Badiger wrote: >> > Is the server configured with the same logAnnounceInterval?: >> > <guru> Do you mean both Leader and Follower config files should be >> > configured with the same Sync and Announce interval values? >> >> The announce interval needs to be the same in the whole PTP domain. >> The sync interval doesn't have to be, but usually it is. >> <guru> I tried to keep both Client and Server same but I didnt see any >> improvement. > > > >> >> > Client log meaning, are you asking console logs on Leader? >> >> I think client is follower in the leader/follower terminology (we use >> the server/client terminology in linuxptp). >> > ok Client log is as below: > > ptp4l[252579.286]: port 2: master state recommended in slave only mode > ptp4l[252579.286]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252579.786]: selected local clock ced607.fffe.20f9e8 as best master > ptp4l[252579.786]: port 2: assuming the grand master role > ptp4l[252579.786]: port 2: master state recommended in slave only mode > ptp4l[252579.786]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252580.182]: selected local clock ced607.fffe.20f9e8 as best master > ptp4l[252580.182]: port 2: assuming the grand master role > ptp4l[252580.182]: port 2: master state recommended in slave only mode > ptp4l[252580.182]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252580.346]: selected best master clock 080011.fffe.21b927 > ptp4l[252580.346]: updating UTC offset to 37 > ptp4l[252580.346]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE > ptp4l[252580.346]: port 2: master state recommended in slave only mode > ptp4l[252580.346]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252580.373]: port 1: minimum delay request interval 2^-4 > ptp4l[252580.534]: rms 1659701576982259968 max 1659701576982259968 freq > +0 +/- 0 delay 7588 +/- 0 > ptp4l[252580.659]: rms 1659701576982259968 max 1659701576982259968 freq > -24 +/- 24 delay 7625 +/- 5 > ptp4l[252580.722]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED > ptp4l[252580.784]: rms 1890 max 2008 freq -3367 +/- 109 delay 7613 +/- > 0 > ptp4l[252580.908]: rms 1493 max 1598 freq -3042 +/- 107 delay 7612 +/- > 0 > ptp4l[252581.034]: rms 1101 max 1185 freq -2647 +/- 92 delay 7604 +/- > 5 > ptp4l[252581.156]: port 1: SLAVE to LISTENING on > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES > ptp4l[252581.156]: selected local clock ced607.fffe.20f9e8 as best master > ptp4l[252581.156]: port 2: assuming the grand master role > ptp4l[252581.156]: port 2: master state recommended in slave only mode > ptp4l[252581.156]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252581.595]: selected local clock ced607.fffe.20f9e8 as best master > ptp4l[252581.595]: port 2: assuming the grand master role > ptp4l[252581.595]: port 2: master state recommended in slave only mode > ptp4l[252581.595]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252581.986]: selected local clock ced607.fffe.20f9e8 as best master > ptp4l[252581.986]: port 2: assuming the grand master role > ptp4l[252581.986]: port 2: master state recommended in slave only mode > ptp4l[252581.986]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252582.346]: selected best master clock 080011.fffe.21b927 > ptp4l[252582.346]: updating UTC offset to 37 > ptp4l[252582.346]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE > ptp4l[252582.346]: port 2: master state recommended in slave only mode > ptp4l[252582.346]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252582.471]: rms 1820 max 2447 freq +433 +/- 2732 delay 7574 +/- > 38 > ptp4l[252582.471]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED > ptp4l[252582.597]: rms 2137 max 2258 freq +2983 +/- 102 delay 7590 +/- > 0 > ptp4l[252582.722]: rms 1720 max 1779 freq +2674 +/- 15 delay 7652 +/- > 6 > ptp4l[252582.846]: rms 1379 max 1453 freq +2415 +/- 58 delay 7671 +/- > 0 > ptp4l[252582.890]: port 1: SLAVE to LISTENING on > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES > ptp4l[252582.890]: selected local clock ced607.fffe.20f9e8 as best master > ptp4l[252582.890]: port 2: assuming the grand master role > ptp4l[252582.890]: port 2: master state recommended in slave only mode > ptp4l[252582.890]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252583.390]: selected local clock ced607.fffe.20f9e8 as best master > ptp4l[252583.390]: port 2: assuming the grand master role > ptp4l[252583.390]: port 2: master state recommended in slave only mode > ptp4l[252583.390]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252583.869]: selected local clock ced607.fffe.20f9e8 as best master > ptp4l[252583.869]: port 2: assuming the grand master role > ptp4l[252583.869]: port 2: master state recommended in slave only mode > ptp4l[252583.870]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252584.247]: selected local clock ced607.fffe.20f9e8 as best master > ptp4l[252584.247]: port 2: assuming the grand master role > ptp4l[252584.247]: port 2: master state recommended in slave only mode > ptp4l[252584.247]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252584.346]: selected best master clock 080011.fffe.21b927 > ptp4l[252584.346]: updating UTC offset to 37 > ptp4l[252584.346]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE > ptp4l[252584.346]: port 2: master state recommended in slave only mode > ptp4l[252584.346]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252584.513]: clockcheck: clock jumped backward or running slower > than expected! > ptp4l[252584.534]: rms 2538 max 2634 freq +2357 +/- 0 delay 7678 +/- > 4 > ptp4l[252584.659]: clockcheck: clock jumped forward or running faster than > expected! > ptp4l[252584.660]: rms 2829 max 2880 freq +2357 +/- 0 delay 7676 +/- > 2 > ptp4l[252584.787]: port 1: UNCALIBRATED to LISTENING on > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES > ptp4l[252584.788]: selected local clock ced607.fffe.20f9e8 as best master > ptp4l[252584.788]: port 2: assuming the grand master role > ptp4l[252584.788]: port 2: master state recommended in slave only mode > ptp4l[252584.788]: port 2: defaultDS.priority1 probably misconfigured > ptp4l[252585.213]: selected local clock ced607.fffe.20f9e8 as best master > ptp4l[252585.213]: port 2: assuming the grand master role > ptp4l[252585.213]: port 2: master state recommended in slave only mode > ptp4l[252585.213]: port 2: defaultDS.priority1 probably misconfigured > > > <guru> Here is the console log on Leader shell: >> >> Your log shows many tx timestamp timeouts, so that needs to be >> resolved first. What hardware and driver are you using? >> <guru> I'm not if I understand this question. Is there a command to get >> the driver info? >> -- >> Miroslav Lichvar >> >> |
|
From: Gururaj B. <gur...@gm...> - 2022-08-09 10:30:58
|
> HW: ARMv8 Cortex-A53 processor (quad-core) in the Stratix10 SoC FPGA > > Driver: intel_fpga_qse_ll (10gb/s) It seems to be an out-of-tree driver. Try increasing tx_timestamp_timeout. If that doesn't help, you will need to ask the vendor or where you got the driver to look at the issue you have with missing TX timestamps. -- Miroslav Lichvar On Tue, 9 Aug 2022 at 13:55, Gururaj Badiger <gur...@gm...> wrote: > Hi Miroslav Lichvar, > > Here is the HW and Driver info, > > HW: ARMv8 Cortex-A53 processor (quad-core) in the Stratix10 SoC FPGA > > Driver: intel_fpga_qse_ll (10gb/s) > > > -Guru > > On Mon, 8 Aug 2022 at 15:57, Gururaj Badiger <gur...@gm...> > wrote: > >> >> >> On Mon, 8 Aug 2022 at 15:38, Miroslav Lichvar <mli...@re...> >> wrote: >> >>> On Mon, Aug 08, 2022 at 03:29:26PM +0530, Gururaj Badiger wrote: >>> > Is the server configured with the same logAnnounceInterval?: >>> > <guru> Do you mean both Leader and Follower config files should be >>> > configured with the same Sync and Announce interval values? >>> >>> The announce interval needs to be the same in the whole PTP domain. >>> The sync interval doesn't have to be, but usually it is. >>> <guru> I tried to keep both Client and Server same but I didnt see any >>> improvement. >> >> >> >>> >>> > Client log meaning, are you asking console logs on Leader? >>> >>> I think client is follower in the leader/follower terminology (we use >>> the server/client terminology in linuxptp). >>> >> ok Client log is as below: >> >> ptp4l[252579.286]: port 2: master state recommended in slave only mode >> ptp4l[252579.286]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252579.786]: selected local clock ced607.fffe.20f9e8 as best master >> ptp4l[252579.786]: port 2: assuming the grand master role >> ptp4l[252579.786]: port 2: master state recommended in slave only mode >> ptp4l[252579.786]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252580.182]: selected local clock ced607.fffe.20f9e8 as best master >> ptp4l[252580.182]: port 2: assuming the grand master role >> ptp4l[252580.182]: port 2: master state recommended in slave only mode >> ptp4l[252580.182]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252580.346]: selected best master clock 080011.fffe.21b927 >> ptp4l[252580.346]: updating UTC offset to 37 >> ptp4l[252580.346]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE >> ptp4l[252580.346]: port 2: master state recommended in slave only mode >> ptp4l[252580.346]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252580.373]: port 1: minimum delay request interval 2^-4 >> ptp4l[252580.534]: rms 1659701576982259968 max 1659701576982259968 freq >> +0 +/- 0 delay 7588 +/- 0 >> ptp4l[252580.659]: rms 1659701576982259968 max 1659701576982259968 freq >> -24 +/- 24 delay 7625 +/- 5 >> ptp4l[252580.722]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED >> ptp4l[252580.784]: rms 1890 max 2008 freq -3367 +/- 109 delay 7613 +/- >> 0 >> ptp4l[252580.908]: rms 1493 max 1598 freq -3042 +/- 107 delay 7612 +/- >> 0 >> ptp4l[252581.034]: rms 1101 max 1185 freq -2647 +/- 92 delay 7604 +/- >> 5 >> ptp4l[252581.156]: port 1: SLAVE to LISTENING on >> ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES >> ptp4l[252581.156]: selected local clock ced607.fffe.20f9e8 as best master >> ptp4l[252581.156]: port 2: assuming the grand master role >> ptp4l[252581.156]: port 2: master state recommended in slave only mode >> ptp4l[252581.156]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252581.595]: selected local clock ced607.fffe.20f9e8 as best master >> ptp4l[252581.595]: port 2: assuming the grand master role >> ptp4l[252581.595]: port 2: master state recommended in slave only mode >> ptp4l[252581.595]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252581.986]: selected local clock ced607.fffe.20f9e8 as best master >> ptp4l[252581.986]: port 2: assuming the grand master role >> ptp4l[252581.986]: port 2: master state recommended in slave only mode >> ptp4l[252581.986]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252582.346]: selected best master clock 080011.fffe.21b927 >> ptp4l[252582.346]: updating UTC offset to 37 >> ptp4l[252582.346]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE >> ptp4l[252582.346]: port 2: master state recommended in slave only mode >> ptp4l[252582.346]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252582.471]: rms 1820 max 2447 freq +433 +/- 2732 delay 7574 +/- >> 38 >> ptp4l[252582.471]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED >> ptp4l[252582.597]: rms 2137 max 2258 freq +2983 +/- 102 delay 7590 +/- >> 0 >> ptp4l[252582.722]: rms 1720 max 1779 freq +2674 +/- 15 delay 7652 +/- >> 6 >> ptp4l[252582.846]: rms 1379 max 1453 freq +2415 +/- 58 delay 7671 +/- >> 0 >> ptp4l[252582.890]: port 1: SLAVE to LISTENING on >> ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES >> ptp4l[252582.890]: selected local clock ced607.fffe.20f9e8 as best master >> ptp4l[252582.890]: port 2: assuming the grand master role >> ptp4l[252582.890]: port 2: master state recommended in slave only mode >> ptp4l[252582.890]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252583.390]: selected local clock ced607.fffe.20f9e8 as best master >> ptp4l[252583.390]: port 2: assuming the grand master role >> ptp4l[252583.390]: port 2: master state recommended in slave only mode >> ptp4l[252583.390]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252583.869]: selected local clock ced607.fffe.20f9e8 as best master >> ptp4l[252583.869]: port 2: assuming the grand master role >> ptp4l[252583.869]: port 2: master state recommended in slave only mode >> ptp4l[252583.870]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252584.247]: selected local clock ced607.fffe.20f9e8 as best master >> ptp4l[252584.247]: port 2: assuming the grand master role >> ptp4l[252584.247]: port 2: master state recommended in slave only mode >> ptp4l[252584.247]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252584.346]: selected best master clock 080011.fffe.21b927 >> ptp4l[252584.346]: updating UTC offset to 37 >> ptp4l[252584.346]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE >> ptp4l[252584.346]: port 2: master state recommended in slave only mode >> ptp4l[252584.346]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252584.513]: clockcheck: clock jumped backward or running slower >> than expected! >> ptp4l[252584.534]: rms 2538 max 2634 freq +2357 +/- 0 delay 7678 +/- >> 4 >> ptp4l[252584.659]: clockcheck: clock jumped forward or running faster >> than expected! >> ptp4l[252584.660]: rms 2829 max 2880 freq +2357 +/- 0 delay 7676 +/- >> 2 >> ptp4l[252584.787]: port 1: UNCALIBRATED to LISTENING on >> ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES >> ptp4l[252584.788]: selected local clock ced607.fffe.20f9e8 as best master >> ptp4l[252584.788]: port 2: assuming the grand master role >> ptp4l[252584.788]: port 2: master state recommended in slave only mode >> ptp4l[252584.788]: port 2: defaultDS.priority1 probably misconfigured >> ptp4l[252585.213]: selected local clock ced607.fffe.20f9e8 as best master >> ptp4l[252585.213]: port 2: assuming the grand master role >> ptp4l[252585.213]: port 2: master state recommended in slave only mode >> ptp4l[252585.213]: port 2: defaultDS.priority1 probably misconfigured >> >> > <guru> Here is the console log on Leader shell: >>> >>> Your log shows many tx timestamp timeouts, so that needs to be >>> resolved first. What hardware and driver are you using? >>> <guru> I'm not if I understand this question. Is there a command to get >>> the driver info? >>> -- >>> Miroslav Lichvar >>> >>> |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X