[Linuxptp-users] strange behavior with free_running regarding offset display

[Tino K. <tin...@al...>]

Hi Richard,

I get a strange behavior when using "free_running 1". The summary looks
like this:

$ ptp4l -f /etc/ptp4l.conf -i eth1 -m
ptp4l[3620445.368]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[3620445.368]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[3620445.600]: port 1: new foreign master 008063.fffe.b6706b-13
ptp4l[3620447.600]: selected best master clock 00606e.fffe.7c230f
ptp4l[3620447.600]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[3620448.515]: port 1: minimum delay request interval 2^3
ptp4l[3620452.600]: rms 34999153762 max 34999173342 freq -19583 +/-   2
delay  7694 +/- 246
ptp4l[3620456.599]: rms 34999231855 max 34999251436 freq -19587 +/-   3
delay  5256 +/-   0
ptp4l[3620460.599]: rms 34999309648 max 34999328697 freq -19591 +/-   8
delay  5141 +/-   0
ptp4l[3620464.599]: rms 34999387468 max 34999407058 freq -19592 +/-   0
ptp4l[3620468.598]: rms 34999465846 max 34999485433 freq -19595 +/-   7

Querying ptp4l using pmc gives this output (note the first
offsetFromMaster value):

$ pmc -u "get CURRENT_DATA_SET"
sending: GET CURRENT_DATA_SET
	001b21.fffe.929906-0 seq 0 RESPONSE MANAGMENT CURRENT_DATA_SET 
		stepsRemoved     2
		offsetFromMaster -35000968295.0
		meanPathDelay    5354.0
	008063.fffe.b6706b-13 seq 0 RESPONSE MANAGMENT CURRENT_DATA_SET 
		stepsRemoved     1
		offsetFromMaster -33.0
		meanPathDelay    87.4
	000b72.fffe.0585b6-1 seq 0 RESPONSE MANAGMENT CURRENT_DATA_SET 
		stepsRemoved     2
		offsetFromMaster -2.0
		meanPathDelay    3818.0

Everything is fine as soon as I use "free_running 0".

Regards,
Tino