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 <mlich...@redhat.com> 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
>
>
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to