Re: [Linuxptp-users] Should Linux PTP syn the clock used by date between PCs?
PTP IEEE 1588 stack for Linux
Brought to you by:
rcochran
From: Richard C. <ric...@gm...> - 2015-11-11 14:05:52
|
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 |