On Wed, Oct 31, 2018 at 04:14:30PM +0530, Dolly Gyanchandani wrote: > Both currentUtcOffsetValid and timeTraceable are coming as "*0*"?
That's why the kernel UTC-TAI offset is not set. Maybe it would make sense to remove this restriction? Is a possibly incorrect offset worse than no offset? > There is 1 more thing we notice, the system time on slave clock is off by > 35 seconds from the master clock's system time (The offset reported by PMC > is default i.e. 37) > > What could be the reason for this? Maybe one side is using an older linuxptp version? Is ptpTimescale 1? Are you using phc2sys -a? -- Miroslav Lichvar _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users