----- On Jan 3, 2019, at 12:24 PM, Richard Cochran richardcoch...@gmail.com 
wrote:

> On Thu, Jan 03, 2019 at 04:58:35PM +0000, Dan Geist wrote:
>> summary_interval                4
> 
> Leave this at zero for debugging, so you can see the synchronization messages.

Done. Lots of verbose output now.
 
> Looking at the ptp4l logs:
> 
> Jan  3 11:56:50 psp6esxd04 ptp4l: [6011.077] port 1: LISTENING to UNCALIBRATED
> on RS_SLAVE
> Jan  3 11:56:52 psp6esxd04 ptp4l: [6012.144] selected best master clock
> 0080ea.fffe.8c2100
> Jan  3 11:56:52 psp6esxd04 ptp4l: [6012.144] updating UTC offset to 37
> Jan  3 11:56:54 psp6esxd04 ptp4l: [6014.399] port 1: UNCALIBRATED to SLAVE on
> MASTER_CLOCK_SELECTED
> Jan  3 11:56:54 psp6esxd04 ptp4l: [6015.076] selected best master clock
> 0080ea.fffe.8c2100
> Jan  3 11:56:54 psp6esxd04 ptp4l: [6015.077] updating UTC offset to 37
> Jan  3 11:56:58 psp6esxd04 ptp4l: [6019.076] selected best master clock
> 0080ea.fffe.8c2100
> Jan  3 11:56:58 psp6esxd04 ptp4l: [6019.077] updating UTC offset to 37
> Jan  3 11:57:02 psp6esxd04 ptp4l: [6023.076] selected best master clock
> 0080ea.fffe.8c2100
> Jan  3 11:57:02 psp6esxd04 ptp4l: [6023.077] updating UTC offset to 37
> 
> Something is causing the BMC to trigger every four seconds.  That
> seems wrong.  Maybe you have a logAnnounceInterval mismatch?

Perhaps... but I have it set to once a second, which matches my GM:

PTP Domain Number       :       44
Clock Class     :       6
Master Clock Type       :       One Step
Clock Class Profile     :       G.8275.2
Master Delay Mechanism  :       End To End
Max Slaves Supported    :       100
Max Static Slaves Supported     :       0
Max Announce Message Rate       :       1 Packet per 1 Second
Max Sync Message Rate   :       32 Packets per Second
Max Delay Response Message Rate :       32 Packets per Second
Max Lease Duration      :       300 sec
Announce Extension TLV  :       N/A

The BMC messages do settle down after a while. I commented out one of the GMs 
and it seems to only iterate on BMC 2 or 3 times, now.

> Also, what is the phc2sys command line?

It's being run via systemd, but:
# ps -Aef | grep phc2sys
root      5041     1  0 16:27 ?        00:00:00 /usr/local/sbin/phc2sys -w -s 
em2.98

and for reference:
# ethtool -T em2.98
Time stamping parameters for em2.98:
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: 1
Hardware Transmit Timestamp Modes:
        off                   (HWTSTAMP_TX_OFF)
        on                    (HWTSTAMP_TX_ON)
Hardware Receive Filter Modes:
        none                  (HWTSTAMP_FILTER_NONE)
        ptpv1-l4-event        (HWTSTAMP_FILTER_PTP_V1_L4_EVENT)
        ptpv2-l4-event        (HWTSTAMP_FILTER_PTP_V2_L4_EVENT)
        ptpv2-l2-event        (HWTSTAMP_FILTER_PTP_V2_L2_EVENT)

Thanks
Dan

-- 
Dan Geist 


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

Reply via email to