Re: [Linuxptp-users] Should Linux PTP syn the clock used by date between PCs?

[Gil G. <Gil...@ha...>]

I run phc2sys like this on the master and the slave.
I guess I don't really know how to run and what to run on each PC.
My goal is to sync the system clock between both PCs, what do Ineed to do on each of them to do that?

here is the log you asked for:

[root@localhost ~]# phc2sys -m -q -r -a
phc2sys[263300.449]: reconfiguring after port state change
phc2sys[263300.449]: selecting CLOCK_REALTIME for synchronization
phc2sys[263300.449]: selecting eth0 as the master clock
phc2sys[263300.449]: phc offset  97993134 s0 freq  -18158 delay   2235
phc2sys[263301.450]: phc offset  97996456 s1 freq  -14837 delay   2305
phc2sys[263302.450]: phc offset     19470 s2 freq   +4633 delay   2374
phc2sys[263303.450]: phc offset     15047 s2 freq   +6051 delay   2374
phc2sys[263304.450]: phc offset      6788 s2 freq   +2307 delay   2305
phc2sys[263305.450]: phc offset     -1351 s2 freq   -3796 delay   2304
phc2sys[263306.451]: phc offset     -5743 s2 freq   -8593 delay   2305
phc2sys[263307.451]: phc offset    -11472 s2 freq  -16045 delay   2305
phc2sys[263308.451]: phc offset      8490 s2 freq    +475 delay   2374
phc2sys[263309.451]: phc offset      7564 s2 freq   +2096 delay   2305
phc2sys[263310.451]: phc offset     -1164 s2 freq   -4363 delay   2374
phc2sys[263311.451]: phc offset     -9589 s2 freq  -13137 delay   2235
phc2sys[263312.452]: phc offset      9205 s2 freq   +2780 delay   2305
phc2sys[263313.452]: phc offset      4075 s2 freq    +412 delay   2304
phc2sys[263314.452]: phc offset        -8 s2 freq   -2449 delay   2305
phc2sys[263315.452]: phc offset     -4963 s2 freq   -7406 delay   2305
phc2sys[263316.452]: phc offset    -12206 s2 freq  -16138 delay   2305
phc2sys[263317.453]: phc offset      8407 s2 freq    +813 delay   2305
phc2sys[263318.453]: phc offset      3129 s2 freq   -1943 delay   2305
phc2sys[263319.453]: phc offset    -11670 s2 freq  -15803 delay   2304
phc2sys[263320.453]: phc offset      -717 s2 freq   -8351 delay   2305
phc2sys[263321.453]: phc offset     16022 s2 freq   +8173 delay   2305
phc2sys[263322.453]: phc offset      7991 s2 freq   +4949 delay   2304
phc2sys[263323.454]: phc offset      -901 s2 freq   -1546 delay   2305
phc2sys[263324.454]: phc offset     -5239 s2 freq   -6154 delay   2305
phc2sys[263325.454]: phc offset     -3604 s2 freq   -6091 delay   2374
phc2sys[263326.454]: phc offset     -2364 s2 freq   -5932 delay   2304
phc2sys[263327.454]: phc offset      -900 s2 freq   -5177 delay   2305
phc2sys[263328.454]: phc offset        74 s2 freq   -4473 delay   2235
phc2sys[263329.455]: phc offset -70368744178346 s2 freq -100000000 delay   2375
phc2sys[263330.473]: port fcaa14.fffe.705813-1 changed state
phc2sys[263330.473]: reconfiguring after port state change
phc2sys[263330.473]: master clock not ready, waiting...
phc2sys[263331.484]: port fcaa14.fffe.705813-1 changed state
phc2sys[263331.484]: reconfiguring after port state change
phc2sys[263331.484]: selecting CLOCK_REALTIME for synchronization
phc2sys[263331.484]: selecting eth0 as the master clock
phc2sys[263331.484]: phc offset -70368560279091 s2 freq -100000000 delay   2535
phc2sys[263332.485]: phc offset -70368469338890 s2 freq -100000000 delay   2536
phc2sys[263333.495]: phc offset -70367843327064 s2 freq -100000000 delay   2535
phc2sys[263334.505]: phc offset -70367200755567 s2 freq -100000000 delay   2459
phc2sys[263335.595]: phc offset -70366506841458 s2 freq -100000000 delay   2612
phc2sys[263336.611]: phc offset -70365860214766 s2 freq -100000000 delay   2535
phc2sys[263337.628]: phc offset -70365213078895 s2 freq -100000000 delay   2458
phc2sys[263338.642]: phc offset -70364567712097 s2 freq -100000000 delay   2612
phc2sys[263339.656]: phc offset -70363922799511 s2 freq -100000000 delay   2535
phc2sys[263340.668]: phc offset -70363278531449 s2 freq -100000000 delay   2535
phc2sys[263341.679]: phc offset -70362635113063 s2 freq -100000000 delay   2535
phc2sys[263342.689]: phc offset -70361992822666 s2 freq -100000000 delay   2535
phc2sys[263343.696]: phc offset -70361351911962 s2 freq -100000000 delay   2535
phc2sys[263344.702]: phc offset -70360711215837 s2 freq -100000000 delay   2535
phc2sys[263345.704]: phc offset -70360074141392 s2 freq -100000000 delay   2535
phc2sys[263346.704]: phc offset -70359437587138 s2 freq -100000000 delay   2535
phc2sys[263347.791]: phc offset -70358745478137 s2 freq -100000000 delay   2535
phc2sys[263348.856]: phc offset -70358068325985 s2 freq -100000000 delay   2459
phc2sys[263349.858]: phc offset -70357430511310 s2 freq -100000000 delay   2536
phc2sys[263350.940]: phc offset -70356741846988 s2 freq -100000000 delay   2536
phc2sys[263351.940]: phc offset -70356105187998 s2 freq -100000000 delay   2536
phc2sys[263352.965]: phc offset -70355453047006 s2 freq -100000000 delay   2535
phc2sys[263353.967]: phc offset -70354815788362 s2 freq -100000000 delay   2535
phc2sys[263355.023]: phc offset -70354143449305 s2 freq -100000000 delay   2535
phc2sys[263356.030]: phc offset -70353502918268 s2 freq -100000000 delay   2535
phc2sys[263357.036]: phc offset -70352862758153 s2 freq -100000000 delay   2535
phc2sys[263358.062]: phc offset -70352209533328 s2 freq -100000000 delay   2535
phc2sys[263359.063]: phc offset -70351572755646 s2 freq -100000000 delay   2535
phc2sys[263360.079]: phc offset -70350926122291 s2 freq -100000000 delay   2535
^Cphc2sys[263360.774]: phc offset -70350483892841 s2 freq -100000000 delay   2459

Thanks,
Gil.
________________________________________
From: Richard Cochran <ric...@gm...>
Sent: Wednesday, November 11, 2015 4:05 PM
To: Gil Graiber
Cc: lin...@li...
Subject: Re: [Linuxptp-users] Should Linux PTP syn the clock used by date between PCs?

On Wed, Nov 11, 2015 at 12:38:38PM +0000, Gil Graiber wrote:
> Hi,
>
> I run:
> ptp4l -i eth0 -m
> The prints looks OK (even after hours).
> Once I run
> phc2sys -r -a
> Or
> phc2sys -s eth0 -c CLOCK_REALTIME -w

Are you perhaps running phc2sys like that on the master?

Please show us the phc2sys output, with -m.

For example, on my PC, I run ptp4l, and it locks to my GPS/PTP master
with output like what you posted.  Then, I start phc2sys, also on my
PC, and I see:

# ./phc2sys -m -q -r -a
phc2sys[19289.292]: reconfiguring after port state change
phc2sys[19289.293]: selecting CLOCK_REALTIME for synchronization
phc2sys[19289.293]: selecting eth6 as the master clock
phc2sys[19289.293]: phc offset     61893 s0 freq  +11746 delay   5743
phc2sys[19290.293]: phc offset     61937 s1 freq  +11790 delay   5698
phc2sys[19291.293]: phc offset       674 s2 freq  +12464 delay   5574
phc2sys[19292.293]: phc offset       715 s2 freq  +12707 delay   5694
phc2sys[19293.293]: phc offset      -209 s2 freq  +11998 delay   5748
phc2sys[19294.294]: phc offset      -546 s2 freq  +11598 delay   5575
phc2sys[19295.294]: phc offset       293 s2 freq  +12273 delay   5758
phc2sys[19296.294]: phc offset       174 s2 freq  +12242 delay   5719

and so on.

Thanks,
Richard