I'd suggest posting the exact arguments and config files of phc2sys and ptp4l, for both master and slave.
Is ptp4l supposed to run as the grandmaster, or do you have some special hardware to be grandmaster? The reason I ask: If you're using ptp4l as the grandmaster, it has a hardcoded UTC/TAI offset (which can be overridden via a config option). This offset doesn't automatically change after leap seconds are applied to the Linux system clock, and ptp4l on the grandmaster does not query the kernel for the offset between UTC and TAI. If ptp4l is the grandmaster, the offset will never change unless you change it via pmc or restarting ptp4l with new options. So, how are you setting the time on the grandmaster, and how are you expecting ptp4l's utc_offset to change after a leap second? Also, I just want to point out that in many server applications, you may want to smear a leap second instead of immediately jump a full second. If so, the Linux concept of TAI vs UTC doesn't work since it only supports an integer conversion between the two timescales. Also, I don't know if the offset of CLOCK_TAI persists between reboots; you might have to wait for ptp4l to sync to a master before starting time-dependent software. _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
