Hello Miroslav,

This is Centos 7.9 with linuxptp-2.0-2.el7_9.1.x86_64 installed, running kernel 
version 3.10.0-1160.41.1.el7.x86_64.

It is running on a Lenovo thinkpad t440, with a built-in intel I218-LM ethernet 
controller, that uses the e1000e kernel driver.

The output of ethtool -T enp0s25 is:

ethtool -T enp0s25
Time stamping parameters for enp0s25:
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)


So I followed your suggestion for a dummy entry.  I made it in the form:
        [ptp_domain 0]
        interfaces enp0s25

and my main domain entry is
        [ptp_domain 44]
        interfaces enp0s25
        delay 10e-6
        ptp4l_option logging_level 7

observations:

        ptp4l on domain 0 always chooses the local clock as its best master
        ptp4l on domain 44 seems to cycle between
                "UNCALIBRATED to LISTENING on "ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
                        and
                "LISTENING TO UNCALIBRATED on RS_SLAVE"

        phc2sys is only listening to the ptp clock for domain 0
                which will not get synced since there is no domain 0 ptp clock.

And chronyc sources now shows two ptp clocks that are not usable.

chronyc sources
210 Number of sources = 5
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
#? PTP0                          0   2     0     -     +0ns[   +0ns] +/-    0ns
#? PTP1                          0   2     0     -     +0ns[   +0ns] +/-    0ns
^+ india.colorado.edu            1   4   203     4  +7589us[+7589us] +/-   29ms
^+ uslax1-ntp-002.aaplimg.c>     1   4   377     5  -1059us[-1059us] +/-   14ms
^* clock.fmt.he.net              1   4   377     6  -2296us[-2251us] +/-   13ms

So it would seem that while that dummy entry stops the " port 1: received SYNC 
without timestamp" messages, it doesn't do much good afterwards.








-----Original Message-----
From: Miroslav Lichvar <mlich...@redhat.com>
Sent: Monday, November 8, 2021 01:09
To: Brooks, Jason <jason.bro...@allstream.com>
Cc: linuxptp-users@lists.sourceforge.net
Subject: [External]Re: [Linuxptp-users] Timemaster question with ptp4l and 
chrony

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.


On Thu, Nov 04, 2021 at 10:55:49PM +0000, Brooks, Jason wrote:
>   1.  Chronyc sources shows
>      *   210 Number of sources = 5
>      *   MS Name/IP address         Stratum Poll Reach LastRx Last sample
>      *   
> ===============================================================================
>      *   #? PTP0                          0   2     0     -     +0ns[   +0ns] 
> +/-    0nsq
>      *   ^+ time-c-b.nist.gov             1   4   377     5  +7083us[+7083us] 
> +/-   28ms
>      *   ^+ time2.google.com              1   4   377     7   +333us[ +333us] 
> +/-   28ms
>      *   ^* usscz2-ntp-001.aaplimg.c>     1   4   377     5   -780us[ -780us] 
> +/-   11ms
>      *   ^+ clock.fmt.he.net              1   4   377     6  -2245us[-2245us] 
> +/-   14ms
>
> Why is chrony showing PTP0 as a problem?

The refclock (i.e. ptp4l+phc2sys) didn't provide any samples.

FYI, Google NTP servers uses a nonstandard timescale (leap smear) and must not 
be combined with standard NTP servers.

>   1.  And when using this system as an ntp source on another system it shows 
> as a stratum 2 system.  Shouldn't this be a stratum 1, given the ptp0 clock?
>   2.  A lot of messages in /var/log/messages:
>      *   [44:enp0s25] port 1: received SYNC without timestamp

What OS and version is it?

Does it work with SW timestamping? If you add a dummy PTP domain to 
timemaster.conf before the 44, it should force 44 to use SW timestamping.

--
Miroslav Lichvar

NOTICE - CONFIDENTIAL INFORMATION This communication is the property of 
Allstream and may contain confidential or privileged information. If you have 
received this communication in error, please promptly notify the sender by 
reply e-mail, do not disseminate, distribute, copy or use the information 
contained in this communication, and destroy all copies of the communication 
and any attachments.
AVIS – RENSEIGNEMENTS CONFIDENTIELS Cette communication est la propriété 
d’Allstream et peut contenir des renseignements confidentiels ou privilégiés. 
Si vous avez reçu cette communication par erreur, veuillez informer rapidement 
l’expéditeur en répondant par courriel, ne pas diffuser, distribuer, copier ou 
utiliser les renseignements contenus dans la présente communication, et 
détruire toutes les copies de la communication et ses pièces jointes.

_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to