[Linuxptp-users] Fwd: PHC clock not getting syncup

[Raveendra M. <rav...@gm...>]

System information:

--------------------------

[root@mavdu ~]# uname -a

Linux mavdu.local 3.10.0-693.2.2.rt56.623.el7.x86_64 #1 SMP PREEMPT RT Tue
Jun 19 08:25:50 IST 2018 x86_64 x86_64 x86_64 GNU/Linux



 [root@mavdu ~]# cat /etc/os-release

NAME="CentOS Linux"

VERSION="7 (Core)"

ID="centos"

ID_LIKE="rhel fedora"

VERSION_ID="7"

PRETTY_NAME="CentOS Linux 7 (Core)"

ANSI_COLOR="0;31"

CPE_NAME="cpe:/o:centos:centos:7"

HOME_URL="https://www.centos.org/"

BUG_REPORT_URL="https://bugs.centos.org/"



Hardware details:



04:00.0 Ethernet controller: Intel Corporation Ethernet Connection X552 10
GbE SFP+

04:00.1 Ethernet controller: Intel Corporation Ethernet Connection X552 10
GbE SFP+





Ptp4l  & phc2sys service running fine in the system. System clokc getting
sync up with master clock fine.  But the hardware clock is not getting
synched up with system clock.



[root@mavdu ~]# systemctl status ptp4l

â— ptp4l.service - Precision Time Protocol (PTP) service

   Loaded: loaded (/usr/lib/systemd/system/ptp4l.service; enabled; vendor
preset: disabled)

   Active: active (running) since Tue 2019-03-19 18:15:12 IST; 1h 35min ago

Main PID: 29211 (ptp4l)

   CGroup: /system.slice/ptp4l.service

           └─29211 /usr/sbin/ptp4l -f /etc/ptp4l.conf -i eth1 -m -S



Mar 19 19:50:00 mavdu.local ptp4l[29211]: ptp4l[163769.633]: rms
36075099498 max 36075891386 freq -100000000 +/-   0 delay -8819267 +/-
523050

Mar 19 19:50:00 mavdu.local ptp4l[29211]: [163769.633] rms 36075099498 max
36075891386 freq -100000000 +/-   0 delay -8819267 +/- 523050

Mar 19 19:50:04 mavdu.local ptp4l[29211]: ptp4l[163773.634]: rms
36067670988 max 36067981017 freq -100000000 +/-   0 delay -14732157 +/-
1681292

Mar 19 19:50:04 mavdu.local ptp4l[29211]: [163773.634] rms 36067670988 max
36067981017 freq -100000000 +/-   0 delay -14732157 +/- 1681292

Mar 19 19:50:08 mavdu.local ptp4l[29211]: ptp4l[163777.634]: rms
36073869240 max 36074931495 freq -100000000 +/-   0 delay -9057727 +/-
1681292

Mar 19 19:50:08 mavdu.local ptp4l[29211]: [163777.634] rms 36073869240 max
36074931495 freq -100000000 +/-   0 delay -9057727 +/- 1681292

Mar 19 19:50:12 mavdu.local ptp4l[29211]: ptp4l[163781.635]: rms
36073608050 max 36073779207 freq -100000000 +/-   0 delay -9193167 +/-
802784

Mar 19 19:50:12 mavdu.local ptp4l[29211]: [163781.635] rms 36073608050 max
36073779207 freq -100000000 +/-   0 delay -9193167 +/- 802784

Mar 19 19:50:16 mavdu.local ptp4l[29211]: ptp4l[163785.636]: rms
36070971221 max 36071372180 freq -100000000 +/-   0 delay -10862422 +/-   0

Mar 19 19:50:16 mavdu.local ptp4l[29211]: [163785.636] rms 36070971221 max
36071372180 freq -100000000 +/-   0 delay -10862422 +/-   0







[root@mavdu ~]# systemctl status phc2sys

â— phc2sys.service - Synchronize system clock or PTP hardware clock (PHC)

   Loaded: loaded (/usr/lib/systemd/system/phc2sys.service; enabled; vendor
preset: disabled)

   Active: active (running) since Tue 2019-03-19 19:30:23 IST; 20min ago

Main PID: 29824 (phc2sys)

   CGroup: /system.slice/phc2sys.service

           └─29824 /usr/sbin/phc2sys -c CLOCK_REALTIME -s eth1 -O -35



Mar 19 19:50:23 mavdu.local phc2sys[29824]: [163792.187] phc offset
509829745 s2 freq +100000000 delay   1605

Mar 19 19:50:24 mavdu.local phc2sys[29824]: [163793.187] phc offset
509865759 s2 freq +100000000 delay   1346

Mar 19 19:50:25 mavdu.local phc2sys[29824]: [163794.187] phc offset
509901413 s2 freq +100000000 delay   1342

Mar 19 19:50:26 mavdu.local phc2sys[29824]: [163795.187] phc offset
509936319 s2 freq +100000000 delay   1582

Mar 19 19:50:27 mavdu.local phc2sys[29824]: [163796.188] phc offset
509972905 s2 freq +100000000 delay   1599

Mar 19 19:50:28 mavdu.local phc2sys[29824]: [163797.188] phc offset
510207505 s2 freq +100000000 delay   1587

Mar 19 19:50:29 mavdu.local phc2sys[29824]: [163798.188] phc offset
510443120 s2 freq +100000000 delay   1605

Mar 19 19:50:30 mavdu.local phc2sys[29824]: [163799.188] phc offset
510559135 s2 freq +100000000 delay   1338

Mar 19 19:50:31 mavdu.local phc2sys[29824]: [163800.188] phc offset
510794512 s2 freq +100000000 delay   1594

Mar 19 19:50:32 mavdu.local phc2sys[29824]: [163801.188] phc offset
510832463 s2 freq +100000000 delay   1599







But the system & hardware clock not getting synched up



[root@mavdu ~]# hwclock

Wed 20 Mar 2019 01:19:54 AM IST  -0.954795 seconds

[root@mavdu ~]# date

Tue Mar 19 19:49:58 IST 2019

[root@mavdu ~]#







Questions:

1. Any configuration missing for system clock & hardware clock not getting
sync up with software time stamp option for ptp4l i.e “ptp4l -f
/etc/ptp4l.conf -i eth1 -m –S”

2.  When hardware time stamping option used  i.e “ptp4l -f /etc/ptp4l.conf
-i eth1 –m”  then hardware clock in slave is not getting synched up.
Any recompilation of kernel or ptp4l module required for hardware time
stamp sync with system clock in the system?



Thank you in advance for help.


Raveendra