On Thu, Jan 03, 2019 at 04:58:35PM +0000, Dan Geist wrote: > summary_interval 4
Leave this at zero for debugging, so you can see the synchronization messages. Looking at the ptp4l logs: Jan 3 11:56:50 psp6esxd04 ptp4l: [6011.077] port 1: LISTENING to UNCALIBRATED on RS_SLAVE Jan 3 11:56:52 psp6esxd04 ptp4l: [6012.144] selected best master clock 0080ea.fffe.8c2100 Jan 3 11:56:52 psp6esxd04 ptp4l: [6012.144] updating UTC offset to 37 Jan 3 11:56:54 psp6esxd04 ptp4l: [6014.399] port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED Jan 3 11:56:54 psp6esxd04 ptp4l: [6015.076] selected best master clock 0080ea.fffe.8c2100 Jan 3 11:56:54 psp6esxd04 ptp4l: [6015.077] updating UTC offset to 37 Jan 3 11:56:58 psp6esxd04 ptp4l: [6019.076] selected best master clock 0080ea.fffe.8c2100 Jan 3 11:56:58 psp6esxd04 ptp4l: [6019.077] updating UTC offset to 37 Jan 3 11:57:02 psp6esxd04 ptp4l: [6023.076] selected best master clock 0080ea.fffe.8c2100 Jan 3 11:57:02 psp6esxd04 ptp4l: [6023.077] updating UTC offset to 37 Something is causing the BMC to trigger every four seconds. That seems wrong. Maybe you have a logAnnounceInterval mismatch? Also, what is the phc2sys command line? Thanks, Richard _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users