On Thu, Jun 19, 2014 at 02:53:12PM +0100, Andrei Perietanu wrote: > I was running *ptp4l* and *phc2sys* this is what caused the behavior. But > as far as ntp goes I did not start anything myself and did not find any ntp > service in the backgorund...though I get your point a conflict between two > programs is likely to be the cause. > > anyway once I stopped phc2sys after a while (about one hour) it went back > to normal...
Well, you did not tell us about running phc2sys before. Now the situation is clear. It is important to remember that the Linux system clock and your NIC's the PTP Hardware Clock (PHC) are totally separate. When your computer boots, the PHC has some random time value, unless you arrange to set the time on that clock. The role of the phc2sys program is to synchronize the PHC and the Linux system clock. You ptp4l master node uses its PHC, and your slave node synchronizes to the master. Now your slave PHC will have some random time from the master's NIC. If you then run phc2sys on the slave, you synchronize your Linux system clock to the random NIC time on the master. So you want to ensure that the master's PHC has the correct time. You need to synchronize it to something. You *can* use phc2sys program to synchronize it to the master's system clock (by reversing the normal phc2sys settings), but in a production setting you would synchronize the PHC to a GPS clock, for example. HTH, Richard ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
