hi Richard,
Email in sent folder seems to be fine. But the email received seems to have
become unreadable. I'm re-attaching the email below. I hope this looks fine.
Also, have attached same as text file.
Regards,Ramesh
hello,
Have a testline where ptp4l application is running as master on a server and is
connected to remote end running ptp as support/slave unit.
When the remote end application is restarted, the interface between ptp master
and support/slave ptp is going down. This is resulting in phc2sys jumping to a
huge value. Mar 23 07:53:21 k8s-worker-0 ptp4l: [434064.223] port 1: link
downMar 23 07:53:21 k8s-worker-0 ptp4l: [434064.223] port 1: MASTER to FAULTY
on FAULT_DETECTED (FT_UNSPECIFIED)Mar 23 07:53:21 k8s-worker-0 ptp4l:
[434064.253] selected local clock 40a6b7.fffe.0d9811 as best masterMar 23
07:53:21 k8s-worker-0 ptp4l: [434064.253] assuming the grand master roleMar 23
07:53:21 k8s-worker-0 phc2sys: [434064.519] enp95s0f0 phc offset 0 s2
freq -1538 delay 3641Mar 23 07:53:21 k8s-worker-0 phc2sys: [434064.536]
clockcheck: clock jumped backward or running slower than expected!Mar 23
07:53:21 k8s-worker-0 phc2sys: [434064.536] enp95s0f1 phc offset -275041761 s0
freq -1535 delay 187Mar 23 07:53:21 k8s-worker-0 ptp4l: [434064.586] rms
5 max 10 freq +1533 +/- 9 delay 378 +/- 0
Verified the above by doing ifconfig down on master server, in this case
phc2sys remained fine.
Mar 23 08:04:34 k8s-worker-0 phc2sys: [434737.079] CLOCK_REALTIME phc offset
-13 s2 freq -80180 delay 1153Mar 23 08:04:34 k8s-worker-0 ptp4l:
[434737.331] timed out while polling for tx timestampMar 23 08:04:34
k8s-worker-0 ptp4l: [434737.331] increasing tx_timestamp_timeout may correct
this issue, but it is likely caused by a driver bugMar 23 08:04:34 k8s-worker-0
ptp4l: [434737.331] port 1: send sync failedMar 23 08:04:34 k8s-worker-0 ptp4l:
[434737.331] port 1: MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)Mar 23
08:04:34 k8s-worker-0 ptp4l: [434737.480] port 1: link downMar 23 08:04:34
k8s-worker-0 ptp4l: [434737.480] selected local clock 40a6b7.fffe.0d9811 as
best masterMar 23 08:04:34 k8s-worker-0 ptp4l: [434737.480] assuming the grand
master roleMar 23 08:04:34 k8s-worker-0 ptp4l: [434737.480] selected local
clock 40a6b7.fffe.0d9811 as best masterMar 23 08:04:34 k8s-worker-0 ptp4l:
[434737.480] assuming the grand master roleMar 23 08:04:34 k8s-worker-0 ptp4l:
[434737.569] rms 6 max 12 freq +1534 +/- 10 delay 377 +/- 2Mar 23
08:04:34 k8s-worker-0 phc2sys: [434737.590] enp95s0f0 phc offset -9 s2
freq -1566 delay 3629Mar 23 08:04:34 k8s-worker-0 phc2sys: [434737.599]
enp95s0f1 phc offset -2 s2 freq -1560 delay 3635Mar 23 08:04:35
k8s-worker-0 phc2sys: [434738.079] CLOCK_REALTIME phc offset 7 s2 freq
-80164 delay 1146
Below are ptp4l and phc2sys process
running##############################################root 86670 1 0
07:37 ? 00:00:04 /usr/sbin/ptp4l -2 -A -i enp175s0f1 -f
ptp4l_support.conf -sroot 127594 90793 0 07:49 pts/2 00:00:03
/usr/sbin/ptp4l -2 -A -i enp95s0f1 -f ptp4l_master.confroot 128028 90793
0 07:49 pts/2 00:00:03 /usr/sbin/ptp4l -2 -A -i enp95s0f0 -f
ptp4l_master.conf
root 92724 90793 0 07:39 pts/2 00:00:00 /usr/sbin/phc2sys -s
enp175s0f1 -c CLOCK_REALTIME -w -r -n 24root 123206 90793 0 07:48 pts/2
00:00:00 /usr/sbin/phc2sys -s enp175s0f1 -c enp95s0f1 -r -w -n 24root
123397 90793 0 07:48 pts/2 00:00:00 /usr/sbin/phc2sys -s enp175s0f1 -c
enp95s0f0 -r -w -n 24#############################################
Can you please suggest if this known issue or what is wrong with this
configuration?
Regards,Ramesh
On Wednesday, March 24, 2021, 09:34:53 AM GMT+5:30, Richard Cochran
<richardcoch...@gmail.com> wrote:
On Tue, Mar 23, 2021 at 05:33:39PM +0000, ramesh t via Linuxptp-users wrote:
> hello,
> Please suggest.
Your mailer has totally mangled the logs, making them unreadable.
Fix that, and then maybe somebody will respond.
Thanks,
Richard
> Regards,Ramesh
> On Tuesday, March 23, 2021, 02:23:06 PM GMT+5:30, ramesh t via
>Linuxptp-users <linuxptp-users@lists.sourceforge.net> wrote:
>
> hello,
> Have a testline where ptp4l application is running as master on a server and
> is connected to remote end running ptp as support/slave unit.
> When the remote end application is restarted, the interface between ptp
> master and support/slave ptp is going down. This is resulting in phc2sys
> jumping to a huge value.
> Mar 23 07:53:21 k8s-worker-0 ptp4l: [434064.223] port 1: link downMar 23
> 07:53:21 k8s-worker-0 ptp4l: [434064.223] port 1: MASTER to FAULTY on
> FAULT_DETECTED (FT_UNSPECIFIED)Mar 23 07:53:21 k8s-worker-0 ptp4l:
> [434064.253] selected local clock 40a6b7.fffe.0d9811 as best masterMar 23
> 07:53:21 k8s-worker-0 ptp4l: [434064.253] assuming the grand master roleMar
> 23 07:53:21 k8s-worker-0 phc2sys: [434064.519] enp95s0f0 phc offset 0
> s2 freq -1538 delay 3641Mar 23 07:53:21 k8s-worker-0 phc2sys:
> [434064.536] clockcheck: clock jumped backward or running slower than
> expected!Mar 23 07:53:21 k8s-worker-0 phc2sys: [434064.536] enp95s0f1 phc
> offset -275041761 s0 freq -1535 delay 187Mar 23 07:53:21 k8s-worker-0
> ptp4l: [434064.586] rms 5 max 10 freq +1533 +/- 9 delay 378 +/- 0
> Verified the above by doing ifconfig down on master server, in this case
> phc2sys remained fine.
> Mar 23 08:04:34 k8s-worker-0 phc2sys: [434737.079] CLOCK_REALTIME phc offset
> -13 s2 freq -80180 delay 1153Mar 23 08:04:34 k8s-worker-0 ptp4l:
> [434737.331] timed out while polling for tx timestampMar 23 08:04:34
> k8s-worker-0 ptp4l: [434737.331] increasing tx_timestamp_timeout may correct
> this issue, but it is likely caused by a driver bugMar 23 08:04:34
> k8s-worker-0 ptp4l: [434737.331] port 1: send sync failedMar 23 08:04:34
> k8s-worker-0 ptp4l: [434737.331] port 1: MASTER to FAULTY on FAULT_DETECTED
> (FT_UNSPECIFIED)Mar 23 08:04:34 k8s-worker-0 ptp4l: [434737.480] port 1: link
> downMar 23 08:04:34 k8s-worker-0 ptp4l: [434737.480] selected local clock
> 40a6b7.fffe.0d9811 as best masterMar 23 08:04:34 k8s-worker-0 ptp4l:
> [434737.480] assuming the grand master roleMar 23 08:04:34 k8s-worker-0
> ptp4l: [434737.480] selected local clock 40a6b7.fffe.0d9811 as best masterMar
> 23 08:04:34 k8s-worker-0 ptp4l: [434737.480] assuming the grand master
> roleMar 23 08:04:34 k8s-worker-0 ptp4l: [434737.569] rms 6 max 12 freq
> +1534 +/- 10 delay 377 +/- 2Mar 23 08:04:34 k8s-worker-0 phc2sys:
> [434737.590] enp95s0f0 phc offset -9 s2 freq -1566 delay 3629Mar
> 23 08:04:34 k8s-worker-0 phc2sys: [434737.599] enp95s0f1 phc offset -2
> s2 freq -1560 delay 3635Mar 23 08:04:35 k8s-worker-0 phc2sys:
> [434738.079] CLOCK_REALTIME phc offset 7 s2 freq -80164 delay 1146
> Below are ptp4l and phc2sys process running.
> ##############################################root 86670 1 0 07:37
> ? 00:00:04 /usr/sbin/ptp4l -2 -A -i enp175s0f1 -f ptp4l_support.conf
> -sroot 127594 90793 0 07:49 pts/2 00:00:03 /usr/sbin/ptp4l -2 -A -i
> enp95s0f1 -f ptp4l_master.confroot 128028 90793 0 07:49 pts/2
> 00:00:03 /usr/sbin/ptp4l -2 -A -i enp95s0f0 -f ptp4l_master.conf
> root 92724 90793 0 07:39 pts/2 00:00:00 /usr/sbin/phc2sys -s
> enp175s0f1 -c CLOCK_REALTIME -w -r -n 24root 123206 90793 0 07:48 pts/2
> 00:00:00 /usr/sbin/phc2sys -s enp175s0f1 -c enp95s0f1 -r -w -n 24root
> 123397 90793 0 07:48 pts/2 00:00:00 /usr/sbin/phc2sys -s enp175s0f1 -c
> enp95s0f0 -r -w -n 24#############################################
> Can you please suggest if this known issue or what is wrong with this
> configuration?
> Regards,Ramesh_______________________________________________
hello,
Have a testline where ptp4l application is running as master on a server and is
connected to remote end running ptp as support/slave unit.
When the remote end application is restarted, the interface between ptp master
and support/slave ptp is going down. This is resulting in phc2sys jumping to a
huge value.
Mar 23 07:53:21 k8s-worker-0 ptp4l: [434064.223] port 1: link down
Mar 23 07:53:21 k8s-worker-0 ptp4l: [434064.223] port 1: MASTER to FAULTY on
FAULT_DETECTED (FT_UNSPECIFIED)
Mar 23 07:53:21 k8s-worker-0 ptp4l: [434064.253] selected local clock
40a6b7.fffe.0d9811 as best master
Mar 23 07:53:21 k8s-worker-0 ptp4l: [434064.253] assuming the grand master role
Mar 23 07:53:21 k8s-worker-0 phc2sys: [434064.519] enp95s0f0 phc offset
0 s2 freq -1538 delay 3641
Mar 23 07:53:21 k8s-worker-0 phc2sys: [434064.536] clockcheck: clock jumped
backward or running slower than expected!
Mar 23 07:53:21 k8s-worker-0 phc2sys: [434064.536] enp95s0f1 phc offset
-275041761 s0 freq -1535 delay 187
Mar 23 07:53:21 k8s-worker-0 ptp4l: [434064.586] rms 5 max 10 freq +1533
+/- 9 delay 378 +/- 0
Verified the above by doing ifconfig down on master server, in this case
phc2sys remained fine.
Mar 23 08:04:34 k8s-worker-0 phc2sys: [434737.079] CLOCK_REALTIME phc offset
-13 s2 freq -80180 delay 1153
Mar 23 08:04:34 k8s-worker-0 ptp4l: [434737.331] timed out while polling for tx
timestamp
Mar 23 08:04:34 k8s-worker-0 ptp4l: [434737.331] increasing
tx_timestamp_timeout may correct this issue, but it is likely caused by a
driver bug
Mar 23 08:04:34 k8s-worker-0 ptp4l: [434737.331] port 1: send sync failed
Mar 23 08:04:34 k8s-worker-0 ptp4l: [434737.331] port 1: MASTER to FAULTY on
FAULT_DETECTED (FT_UNSPECIFIED)
Mar 23 08:04:34 k8s-worker-0 ptp4l: [434737.480] port 1: link down
Mar 23 08:04:34 k8s-worker-0 ptp4l: [434737.480] selected local clock
40a6b7.fffe.0d9811 as best master
Mar 23 08:04:34 k8s-worker-0 ptp4l: [434737.480] assuming the grand master role
Mar 23 08:04:34 k8s-worker-0 ptp4l: [434737.480] selected local clock
40a6b7.fffe.0d9811 as best master
Mar 23 08:04:34 k8s-worker-0 ptp4l: [434737.480] assuming the grand master role
Mar 23 08:04:34 k8s-worker-0 ptp4l: [434737.569] rms 6 max 12 freq +1534
+/- 10 delay 377 +/- 2
Mar 23 08:04:34 k8s-worker-0 phc2sys: [434737.590] enp95s0f0 phc offset
-9 s2 freq -1566 delay 3629
Mar 23 08:04:34 k8s-worker-0 phc2sys: [434737.599] enp95s0f1 phc offset
-2 s2 freq -1560 delay 3635
Mar 23 08:04:35 k8s-worker-0 phc2sys: [434738.079] CLOCK_REALTIME phc offset
7 s2 freq -80164 delay 1146
Below are ptp4l and phc2sys process running
##############################################
root 86670 1 0 07:37 ? 00:00:04 /usr/sbin/ptp4l -2 -A -i
enp175s0f1 -f ptp4l_support.conf -s
root 127594 90793 0 07:49 pts/2 00:00:03 /usr/sbin/ptp4l -2 -A -i
enp95s0f1 -f ptp4l_master.conf
root 128028 90793 0 07:49 pts/2 00:00:03 /usr/sbin/ptp4l -2 -A -i
enp95s0f0 -f ptp4l_master.conf
root 92724 90793 0 07:39 pts/2 00:00:00 /usr/sbin/phc2sys -s
enp175s0f1 -c CLOCK_REALTIME -w -r -n 24
root 123206 90793 0 07:48 pts/2 00:00:00 /usr/sbin/phc2sys -s
enp175s0f1 -c enp95s0f1 -r -w -n 24
root 123397 90793 0 07:48 pts/2 00:00:00 /usr/sbin/phc2sys -s
enp175s0f1 -c enp95s0f0 -r -w -n 24
#############################################
Can you please suggest if this known issue or what is wrong with this
configuration?
Regards,
Ramesh_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
