This smells a bit like the same symptoms as https://github.com/richardcochran/linuxptp/commit/6b61ba29c78e26109426429c6d6b354f6e4443cd : "Avoid fault when receiving zero length packets" You could confirm with a tcpdump on UDP ports 320 and 319, keeping an eye for otherwise well-formed UDP messages with zero payload on your network, being sent for some reason.
Cheers, Dave On Wed, 4 Sep 2019 at 07:00, Essling, Adam M <adam.essl...@udri.udayton.edu> wrote: > Hi, I'm trying to use ptp4l with [system1] and [system2] as slaves with a > Spectracom Versasync PTP clock as master. Both slave systems are running > Ubuntu 16.04 with ptp4l v1.8. I am using the default ptp4l.conf file. When > I run the following command (on system1): > > sudo ptp4l -i eth0 -f /etc/linuxptp/ptp4l.conf -m > > I get the following output: > ptp4l: [7769.535] selected /dev/ptp0 as PTP clock > ptp4l: [7769.537] port 1: INITIALIZING to LISTENING on INITIALIZE > ptp4l: [7769.537] port 0: INITIALIZING to LISTENING on INITIALIZE > ptp4l: [7769.537] port 1: link up > ptp4l: [7770.221] port 1: new foreign master 000cec.fffe.xxxxxx-1 > ptp4l: [7770.221] recvmsg failed: No such file or directory > ptp4l: [7770.221] port 1: recv message failed > ptp4l: [7770.221] port 1: LISTENING to FAULTY on FAULT_DETECTED > (FT_UNSPECIFIED) > ptp4l: [7786.223] port 1: FAULTY to LISTENING on FAULT_CLEARED > ... > > And then the output just repeats the last 4 lines shown, indefinitely. > Both slaves get the same error. The foreign master address is the correct > mac address for the Versasync, so I don't think it's a network issue. > > I know the recvmsg failed error has something to do with the ptp4l socket > but I'm not sure how to go about fixing it. Please let me know if more > information is needed. I'll also include the results of ethtool -T for the > NIC on the slave systems. > > [system1] ethtool -T results: > Time stamping parameters for eth0: > 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) > 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) > > [system2] ethtool -T results: > Time stamping parameters for eno2: > 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) > all (HWTSTAMP_FILTER_ALL) > > > Thanks, > Adam > _______________________________________________ > Linuxptp-users mailing list > Linuxptp-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxptp-users >
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
