On 1/8/2020 5:35 AM, RAVEENDRA M via Linuxptp-users wrote: > /boot/config* has following > > # PTP clock support > CONFIG_PTP_1588_CLOCK=m > CONFIG_PTP_1588_CLOCK_PCH=m > CONFIG_PTP_1588_CLOCK_KVM=m > > Do I need to make above defines to 'y' & rebuild kernel or build igbe > driver is good enough ? >
Modules are fine. On Wednesday, January 8, 2020, 6:35:38 PM GMT+5:30, RAVEENDRA M via > Linuxptp-users <linuxptp-users@lists.sourceforge.net> wrote: > > > Hi, > > We have tested ptp4l L2 mode which is working fine. But when we are > trying to test with UDP mode the ptp4l slave is not responding to ptp > sync, anounce or followup messages. > > [root@centos7 <mailto:root@centos7> ~]# ethtool -T eth1 > > Time stamping parameters for eth1: > 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: 3 > Hardware Transmit Timestamp Modes: > off (HWTSTAMP_TX_OFF) > on (HWTSTAMP_TX_ON) > Hardware Receive Filter Modes: > none (HWTSTAMP_FILTER_NONE) > all (HWTSTAMP_FILTER_ALL) > ethtool -i? What hardware/driver are you using? It clearly indicates support for timestamping all packets... > [root@centos7 <mailto:root@centos7> etc]# ptp4l -i eth1 -s -4 -A -l 7 -m <snip> > ptp4l[713555.689]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE > ptp4l[713555.689]: port 1: received link status notification > ptp4l[713555.689]: interface index 3 is up > ptp4l[713556.782]: port 1: announce timeout > ptp4l[713556.783]: config item eth1.udp_ttl is 3 > ptp4l[713556.784]: config item (null).dscp_event is 0 > ptp4l[713556.784]: config item (null).dscp_general is 0 > ptp4l[713556.784]: selected local clock 00a0a5.fffe.d9dbb9 as best master > ptp4l[713557.815]: port 1: announce timeout > ptp4l[713557.815]: config item eth1.udp_ttl is 3 > ptp4l[713557.816]: config item (null).dscp_event is 0 > ptp4l[713557.816]: config item (null).dscp_general is 0 > ptp4l[713557.816]: selected local clock 00a0a5.fffe.d9dbb9 as best master > > > Any suggestion will be helpful. > You cut off the log output before it showed any messages about the timestamps or packets being sent. You can see this output indicates that the local clock is being selected as best master. I would investigate whether or not the L3 packets are actually making it to the server and application. It's quite possible firewall settings or other system settings are preventing the PTP traffic from reaching ptp4l. You could try using something like tcpdump (optionally with disabling promiscuous mode) to verify the packets are reaching your system. You might also try checking ethtool statistics for the device. > Thanks, > Raveendra. M > Good luck! Thanks, Jake _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
