Hello Richard, ptp4l[1544131.729]: selected /dev/ptp0 as PTP clock ptp4l[1544131.764]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[1544131.764]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[1544132.338]: port 1: new foreign master 001b21.fffe.df71ab-8193 ptp4l[1544132.847]: port 1: new foreign master 6cb311.fffe.1b7464-12289 ptp4l[1544136.338]: selected best master clock 001b21.fffe.df71ab ptp4l[1544136.338]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE ptp4l[1544136.847]: selected best master clock 001b21.fffe.df71ab
I can't really get a grasp of what's happening there e.g why it does happen. >From the last message i did send you i clearly could see the ptp4l interacting with the hardware e.g it sends path delay requests and responds to them too. (responds to other devices request) Could it be that it's because two masters are connected via 1 port? (I mean shouldn't be a real problem as of the BMC) Best regards, Hamar Von: Richard Cochran <richardcoch...@gmail.com> An: Armin HAMAR <armin.ha...@sprecher-automation.com> Kopie: linuxptp-users@lists.sourceforge.net Datum: 05.12.2019 16:44 Betreff: Re: [Linuxptp-users] No offsets at all? On Thu, Dec 05, 2019 at 02:25:10PM +0100, Armin HAMAR wrote: > Anyone a idea why that would happen and i don't get any offsets? > > ptp4l[1208613.181]: port 1: new foreign master 001b21.fffe.df71ab-8193 > ptp4l[1208617.145]: selected best master clock 6cb311.fffe.1b7464 > ptp4l[1208617.145]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE > ptp4l[1208617.181]: selected best master clock 001b21.fffe.df71ab > ptp4l[1208621.145]: selected best master clock 001b21.fffe.df71ab > ptp4l[1208625.145]: selected best master clock 001b21.fffe.df71ab > ptp4l[1208629.144]: selected best master clock 001b21.fffe.df71ab > > I do have the ptp4l on a device which is behind a PRP device and for some > reason it doesn't show > the offsets anymore but this is actually the interesting part of it. (e.g > the jitter an such stuff) In order to transition from UNCALIBRATED to SLAVE, the client must complete a path delay measurement, that is a delay request and a delay response. Maybe the PRP device/network is dropping these? HTH, Richard
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
