Re: [Linuxptp-users] Synchronisation

[Keller, J. E <jac...@in...>]

> -----Original Message-----
> From: Jord Pool [mailto:jor...@ou...]
> Sent: Friday, June 15, 2018 2:59 AM
> To: Richard Cochran <ric...@gm...>
> Cc: Cliff Spradlin via Linuxptp-users <lin...@li...>
> Subject: Re: [Linuxptp-users] Synchronisation
> 
> Hi, an update here,
> 
> So I found that when launching ptp4l it automatically assigns itself a /dev/ptp*
> device. One time it assigns /dev/ptp2, another time it assigns /dev/ptp4 etc very
> random. I have a total of 5 devices: /dev/ptp0, /dev/ptp1, /dev/ptp2, /dev/ptp3
> and /dev/ptp4. Phc2sys is launched at the same time by using # phc2sys -c
> /dev/ptp0 -s CLOCK_REALTIME -m -q -w.
> 

Are you passing only one ethernet device to ptp4l? Or changing? It seems very suspicious if it keeps changing /dev/ptpX devices for a given interface. This smells of a potential driver issue.


> When letting ptp4l choose a device by just running # ptp4l -i enp0s25 -m -q -4 -H
> and letting phc2sys synchronise the /dev/ptp0 device to the system clock by
> using # phc2sys -c /dev/ptp0 -s CLOCK_REALTIME -m -q -w, ptp4l does return the
> message that it assumed the grandmaster role and phc2sys starts synchronising
> /dev/ptp0 to the system clock (I also checked this with phc_ctl and this seems
> perfectly fine).
> 
> When specifying any other device in the phc2sys command (such as /dev/ptp4 or
> /dev/ptp2 etc.) it does never reach servo 2 and always keeps returning the
> message “Clock check: clock jumped forward or running faster than expected!”
> 

Well, enp0s25 *seems* to indicate that it's using /dev/ptp4, according to your ethtool -T output.

> This seems to me that /dev/ptp0 is the only device that is correctly able to
> synchronize to the system clock, however I can never get ptp4l to distribute the
> time of /dev/ptp0 over the network..
> 

Well, /dev/ptp0 isn't connected to the network interface you are using ptp4l for.

It is quite possible you have a driver issue going on here.

Try Richard's suggestion of automated mode, and see what happens?

Thanks,
Jake