On Tue, Nov 02, 2021 at 09:02:19AM +0000, ramesh t via Linuxptp-devel wrote: > hi, > > We are using ptp3.0 version in C3 mode. Both ptp4l and phc2sys (to sync > system clock) are running fine. > > Ptp4l rms value is in single digits and we see a sudden jump in phc offset as > captured below resulting in date change. > > Oct 26 19:15:48 phc2sys_slave: [1177711.923] CLOCK_REALTIME phc offset -97 s2 > freq +3454 delay 2479 > Oct 26 19:15:49 ptp4l_slave: [1177712.827] rms 3 max 7 freq -2363 +/- 5 delay > 86 +/- 1 > Oct 26 19:15:49 phc2sys_slave: [1177712.924] CLOCK_REALTIME phc offset -61 s2 > freq +3461 delay 2433 > Oct 12 05:18:20 ptp4l_slave: [1177713.819] rms 3 max 8 freq -2364 +/- 5 delay > 86 +/- 1 > Oct 19 08:03:31 phc2sys_slave: [1177713.924] clockcheck: clock jumped > backward or running slower than expected! > Oct 19 08:03:31 phc2sys_slave: [1177713.924] CLOCK_REALTIME phc offset > -645138994849912 s0 freq +3461 delay 2478 > Oct 25 18:44:33 ptp4l_slave: [1177714.811] rms 3 max 6 freq -2361 +/- 4 delay > 86 +/- 1 > Sep 30 01:35:47 phc2sys_slave: [1177714.924] clockcheck: clock jumped > backward or running slower than expected! > Sep 30 01:35:47 phc2sys_slave: [1177714.924] CLOCK_REALTIME phc offset > -2310003858831797 s0 freq +3461 delay 2472 > Oct 12 07:16:54 ptp4l_slave: [1177715.803] rms 3 max 5 freq -2362 +/- 5 delay > 87 +/- 1 > > Is there any known issues with ptp3.0 version? Please suggest.
What hardware do you use? It's most likely a driver bug or something else (e.g. an NTP client) is trying to control the clock. -- Miroslav Lichvar _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
