Re: [Linuxptp-users] Clock jumped forward or running faster than expected

[Jord P. <jor...@ou...>]

Hi,


I am actually running a ptp4l instance on that same machine, before even running the phc2sys instance. However, that ptp4l instance is the only one in the network at that moment; electing the node as the PTP grandmaster.


I have tried if the -F and -S options could resolve the problem. Sadly this didn't work.


I have tried another phc2sys command that did looked like resolving the problem as it is still running at acceptable values, I used the following:


# phc2sys -c /dev/ptp0 -s CLOCK_REALTIME -O 35 -m


Instead of the command I tried using in the first case:


# phc2sys -c /dev/ptp0 -s CLOCK_REALTIME -w -m


I'm glad it's running now, but I do not know what was the problem in the first case, why the offset of 35 seconds resolves the problem. Anyone?


Jord Pool
IT Service Management


________________________________
From: Keller, Jacob E <jac...@in...>
Sent: Tuesday, May 8, 2018 6:58:13 PM
To: Jord Pool; lin...@li...
Subject: RE: Clock jumped forward or running faster than expected

> -----Original Message-----
> From: Jord Pool [mailto:jor...@ou...]
> Sent: Monday, May 07, 2018 11:32 PM
> To: Keller, Jacob E <jac...@in...>; linuxptp-
> us...@li...
> Subject: Re: Clock jumped forward or running faster than expected
>
> Hi Jake!
>
>
>
>
> The network device is the Intel Ethernet Connection (2) I218-LM in combination
> with the e1000e driver version 3.4.0.2 (latest).
>
>

Ok. I'm not super familiar with that device. From the output that clockcheck is seeing a jump, this indicates usually either a driver bug or that something else is setting the clock.

You aren't (yet) running ptp4l in this scenario right? If you are, is it possible you've configured the client on this device to enter slave mode on accident?

You might also try the -F and -S options of the phc2sys to enable step threshold offsets. (-F should be on by default but not be a good value in this case).

>
>
> The output of ethtool -T eno1 is as follows:
>
> Time stamping parameters for eno1:
> Capabilities:
>     hardware-transmit     (SOF_TIMESTAMPING_TX_HARDWARE)
>     software-transmit     (SOF_TIMESTAMPING_TX_SOFTWARE)
>     hardware-receive      (SOF_TIMESTAMPING_RX_HARDWARE)
>     software-receive      (SOF_TIMESTAMPING_RX_SOFTWARE)
>     software-system-clock (SOF_TIMESTAMPING_SOFTWARE)
>     hardware-raw-clock    (SOF_TIMESTAMPING_RAW_HARDWARE)
> PTP Hardware Clock: 0
> Hardware Transmit Timestamp Modes:
>     off                   (HWTSTAMP_TX_OFF)
>     on                    (HWTSTAMP_TX_ON)
> Hardware Receive Filter Modes:
>     none                  (HWTSTAMP_FILTER_NONE)
>     all                   (HWTSTAMP_FILTER_ALL)
>     ptpv1-l4-sync         (HWTSTAMP_FILTER_PTP_V1_L4_SYNC)
>     ptpv1-l4-delay-req    (HWTSTAMP_FILTER_PTP_V1_L4_DELAY_REQ)
>     ptpv2-l4-sync         (HWTSTAMP_FILTER_PTP_V2_L4_SYNC)
>     ptpv2-l4-delay-req    (HWTSTAMP_FILTER_PTP_V2_L4_DELAY_REQ)
>     ptpv2-l2-sync         (HWTSTAMP_FILTER_PTP_V2_L2_SYNC)
>     ptpv2-l2-delay-req    (HWTSTAMP_FILTER_PTP_V2_L2_DELAY_REQ)
>     ptpv2-event           (HWTSTAMP_FILTER_PTP_V2_EVENT)
>     ptpv2-sync            (HWTSTAMP_FILTER_PTP_V2_SYNC)
>     ptpv2-delay-req       (HWTSTAMP_FILTER_PTP_V2_DELAY_REQ)
>
>

Regards,
Jake