the phc log from ARM (MAster) system):
Dec 18 10:14:35 H2 user.info phc2sys: [244285.927] sys offset -19228841334 s2
freq -199999999 delay 900
Dec 18 10:14:36 H2 user.info phc2sys: [244286.938] sys offset -19026801184 s2
freq -199999999 delay 900
Dec 18 10:14:37 H2 user.info phc2sys: [244287.948] sys offset -18824717691 s2
freq -199999999 delay 1050
Dec 18 10:14:38 H2 user.info phc2sys: [244288.958] sys offset -18622676693 s2
freq -199999999 delay 1050
Dec 18 10:14:39 H2 user.info phc2sys: [244289.969] sys offset -18420594633 s2
freq -199999999 delay 1050
Dec 18 10:14:40 H2 user.info phc2sys: [244290.979] sys offset -18218553326 s2
freq -199999999 delay 900
Dec 18 10:14:41 H2 user.info phc2sys: [244291.989] sys offset -18016479571 s2
freq -199999999 delay 1050
Dec 18 10:14:42 H2 user.info phc2sys: [244292.999] sys offset -17814438575 s2
freq -199999999 delay 900
Dec 18 10:14:43 H2 user.info phc2sys: [244294.010] sys offset -17612350713 s2
freq -199999999 delay 900
Dec 18 10:14:44 H2 user.info phc2sys: [244295.020] sys offset -17410311352 s2
freq -199999999 delay 1050
Dec 18 10:14:45 H2 user.info phc2sys: [244296.030] sys offset -17208272682 s2
freq -199999999 delay 900
Dec 18 10:14:46 H2 user.info phc2sys: [244297.041] sys offset -17006186029 s2
freq -199999999 delay 900
Dec 18 10:14:47 H2 user.info phc2sys: [244298.051] sys offset -16804103387 s2
freq -199999999 delay 1050
Dec 18 10:14:48 H2 user.info phc2sys: [244299.062] sys offset -16602017522 s2
freq -199999999 delay 900
Dec 18 10:14:49 H2 user.info phc2sys: [244300.072] sys offset -16399974852 s2
freq -199999999 delay 900
Dec 18 10:14:50 H2 user.info phc2sys: [244301.082] sys offset -16197933246 s2
freq -199999999 delay 1050
Dec 18 10:14:51 H2 user.info phc2sys: [244302.092] sys offset -15995892555 s2
freq -199999999 delay 1050
Dec 18 10:14:52 H2 user.info phc2sys: [244303.102] sys offset -15793852325 s2
freq -199999999 delay 1050
Dec 18 10:14:53 H2 user.info phc2sys: [244304.113] sys offset -15591811698 s2
freq -199999999 delay 900
Dec 18 10:14:54 H2 user.info phc2sys: [244305.123] sys offset -15389730276 s2
freq -199999999 delay 1050
Dec 18 10:14:55 H2 user.info phc2sys: [244306.133] sys offset -15187689631 s2
freq -199999999 delay 1050
Dec 18 10:14:56 H2 user.info phc2sys: [244307.144] sys offset -14985604204 s2
freq -199999999 delay 900
Dec 18 10:14:57 H2 user.info phc2sys: [244308.154] sys offset -14783564204 s2
freq -199999999 delay 900
Dec 18 10:14:58 H2 user.info phc2sys: [244309.164] sys offset -14581477361 s2
freq -199999999 delay 1050
afer a while----
Dec 18 10:19:40 H2 user.info phc2sys: [244591.040] sys offset -13 s2 freq
-3 delay 750
Dec 18 10:19:41 H2 user.info phc2sys: [244592.050] sys offset -26 s2 freq
-20 delay 850
Dec 18 10:19:42 H2 user.info phc2sys: [244593.060] sys offset 32 s2 freq
+31 delay 850
Dec 18 10:19:43 H2 user.info phc2sys: [244594.071] sys offset -40 s2 freq
-32 delay 750
And following the PHC log from the PC when it is converging:
Dec 18 11:30:19 it-evarig-capture phc2sys: [1115478.428] phc offset
316668757766 s2 freq +100000000 delay 2892
Dec 18 11:30:20 it-evarig-capture phc2sys: [1115479.428] phc offset
316557628294 s2 freq +100000000 delay 2954
Dec 18 11:30:21 it-evarig-capture phc2sys: [1115480.428] phc offset
316446502795 s2 freq +100000000 delay 2891
Dec 18 11:30:22 it-evarig-capture phc2sys: [1115481.428] phc offset
316335374114 s2 freq +100000000 delay 2891
Dec 18 11:30:23 it-evarig-capture phc2sys: [1115482.428] phc offset
316224248442 s2 freq +100000000 delay 2891
Dec 18 11:30:24 it-evarig-capture phc2sys: [1115483.428] phc offset
316113119114 s2 freq +100000000 delay 2892
Dec 18 11:30:25 it-evarig-capture phc2sys: [1115484.428] phc offset
316001991695 s2 freq +100000000 delay 2891
Dec 18 11:30:26 it-evarig-capture phc2sys: [1115485.428] phc offset
315890861597 s2 freq +100000000 delay 2891
Dec 18 11:30:27 it-evarig-capture phc2sys: [1115486.429] phc offset
315779732665 s2 freq +100000000 delay 2891
Dec 18 11:30:28 it-evarig-capture phc2sys: [1115487.429] phc offset
315668604849 s2 freq +100000000 delay 2954
Dec 18 11:30:29 it-evarig-capture phc2sys: [1115488.429] phc offset
315557477578 s2 freq +100000000 delay 2891
Dec 18 11:30:30 it-evarig-capture phc2sys: [1115489.429] phc offset
315446348329 s2 freq +100000000 delay 2892
Dec 18 11:30:31 it-evarig-capture phc2sys: [1115490.429] phc offset
315335223399 s2 freq +100000000 delay 2891
Dec 18 11:30:32 it-evarig-capture phc2sys: [1115491.429] phc offset
315224096105 s2 freq +100000000 delay 2954
Dec 18 11:30:33 it-evarig-capture phc2sys: [1115492.429] phc offset
315112966277 s2 freq +100000000 delay 2891
Dec 18 11:30:34 it-evarig-capture phc2sys: [1115493.429] phc offset
315001839145 s2 freq +100000000 delay 2892
Dec 18 11:30:35 it-evarig-capture phc2sys: [1115494.429] phc offset
314890713131 s2 freq +100000000 delay 2954
and its ptp log:
Dec 18 11:25:34 it-evarig-capture ptp4l: [1115193.513] master offset 1538
s2 freq -5012 path delay 17939
Dec 18 11:25:35 it-evarig-capture ptp4l: [1115194.413] master offset -1065
s2 freq -7154 path delay 17992
Dec 18 11:25:36 it-evarig-capture ptp4l: [1115195.313] master offset -30
s2 freq -6438 path delay 17939
Dec 18 11:25:36 it-evarig-capture ptp4l: [1115195.720] selected best master
clock ba5d1b.fffe.90c737
Dec 18 11:25:36 it-evarig-capture ptp4l: [1115195.765] selected best master
clock ba5d1b.fffe.90c737
Dec 18 11:25:36 it-evarig-capture ptp4l: [1115195.890] selected best master
clock ba5d1b.fffe.90c737
Dec 18 11:25:36 it-evarig-capture ptp4l: [1115195.952] selected best master
clock ba5d1b.fffe.90c737
Dec 18 11:25:36 it-evarig-capture ptp4l: [1115195.978] selected best master
clock ba5d1b.fffe.90c737
Dec 18 11:25:36 it-evarig-capture ptp4l: [1115196.063] selected best master
clock ba5d1b.fffe.90c737
Dec 18 11:25:37 it-evarig-capture ptp4l: [1115196.213] master offset -297
s2 freq -6714 path delay 17976
Dec 18 11:25:37 it-evarig-capture ptp4l: [1115196.288] selected best master
clock ba5d1b.fffe.90c737
Dec 18 11:25:37 it-evarig-capture ptp4l: [1115196.328] selected best master
clock ba5d1b.fffe.90c737
Dec 18 11:25:37 it-evarig-capture ptp4l: [1115196.499] selected best master
clock ba5d1b.fffe.90c737
Dec 18 11:25:37 it-evarig-capture ptp4l: [1115196.947] selected best master
clock ba5d1b.fffe.90c737
Dec 18 11:25:37 it-evarig-capture ptp4l: [1115196.951] selected best master
clock ba5d1b.fffe.90c737
Dec 18 11:25:37 it-evarig-capture ptp4l: [1115197.113] master offset 689
s2 freq -5817 path delay 17976
Omar Pighi
Sr. Engineer, VisLab
Email opi...@ambarella.com<mailto:opi...@ambarella.com> - Phone: +39
0521 90 6181 (GMT+1)
VisLab, an Ambarella company - Parco Area delle Scienze,
Tecnopolo, Pad. 33, Univ di Parma, 43124 PARMA, Italy
Administration: off...@vislab.it<mailto:off...@vislab.it> phone: +39 0521
905725
Il 17/12/2017 19:46, Omar Pighi via Linuxptp-users ha scritto:
The arm is an ambarella h2.
Tomorrow i will.send to you.the phc2sys logs of arm, and also the working case
of the Pc's
Im.sure there is not ntp or chronyd on.the pc.
We have the chronyd running on.the arm to.sync it with gpsd... but i tried also
disabling it.
Thanks
Omar
Inviato dal mio dispositivo Huawei
-------- Messaggio originale --------
Oggetto: Re: Ris: Ris: [Linuxptp-users] phc2sys doesn't update system clock
anymore
Da: Richard Cochran
A: Omar Pighi
CC:
linuxptp-users@lists.sourceforge.net<mailto:linuxptp-users@lists.sourceforge.net>
On Sat, Dec 16, 2017 at 09:43:13PM +0000, Omar Pighi wrote:
But i i look at the ptp log, tbe offset is low, so the ethernet card
seems to.be synced...
That proves nothing.
the phc2sys isnt a "local" problem to.the slaves?
Without seeing the logs and not knowing the details of your arm board
(which SoC is it? which MAC HW and driver?), it is impossible for me
to guess.
Have you considered that maybe ntp (or chrony) is running on your PCs?
Good luck,
Richard
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
To access SPAM Manager Portal, please visit
https://spammanager-4.messagelabs.com
______________________________________________________________________
NOTE: This email (including attachments) contain Ambarella Proprietary and/or
Confidential Information and is intended solely for the use of the
individual(s) to whom it is addressed. Any unauthorized review, use,
disclosure, distribute, copy, or print is prohibited. If you are not an
intended recipient, please contact the sender by reply email and destroy all
copies of the original message. Thank you.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
To access SPAM Manager Portal, please visit
https://spammanager-4.messagelabs.com
______________________________________________________________________
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net<mailto:Linuxptp-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
NOTE: This email (including attachments) contain Ambarella Proprietary and/or
Confidential Information and is intended solely for the use of the
individual(s) to whom it is addressed. Any unauthorized review, use,
disclosure, distribute, copy, or print is prohibited. If you are not an
intended recipient, please contact the sender by reply email and destroy all
copies of the original message. Thank you.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
