Re: [Linuxptp-users] Newly Configured Machine Has Very Large Sys Offset
On 6/27/2023 9:03 PM, Joshua Quesenberry wrote: > If I don't do one per NIC how do devices connected to each different > NIC do the PTP syncing? For instance, I have three LiDARs each with > dedicated NIC and needing to receive the PTP time from this system in > order to be properly sync'd to each other. > That setup sounds a lot like the "just a bunch of clocks" mode of ptp4l. > Some new information. Of the six NICs, enp0s31f6 that I was working > with above is an I219-LM and the other five are I225-IT. The five > I225-IT appear to be working as I had expected. I have no idea why the > I219-LM is not working properly. I have stumbled upon this post: > https://community.intel.com/t5/Ethernet-Products/Onboard-Intel-I219-LM-PTP-synchronization-problem-Driver-e1000e/td-p/1420598 > which shows that others are also running into similar issues with the > device and I've just posted there too. Please give it a read in case > something stands out. > It looks like that hardware uses the e1000e driver. I recall that driver having many issues and fixes or workarounds for hardware. Are you certain you're on an up to date version of the driver? I am not very familiar with that device, so I am not certain about the level of quality for its clock or timestamps. ___ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
Re: [Linuxptp-users] Newly Configured Machine Has Very Large Sys Offset
If I don't do one per NIC how do devices connected to each different NIC do the PTP syncing? For instance, I have three LiDARs each with dedicated NIC and needing to receive the PTP time from this system in order to be properly sync'd to each other. Some new information. Of the six NICs, enp0s31f6 that I was working with above is an I219-LM and the other five are I225-IT. The five I225-IT appear to be working as I had expected. I have no idea why the I219-LM is not working properly. I have stumbled upon this post: https://community.intel.com/t5/Ethernet-Products/Onboard-Intel-I219-LM-PTP-synchronization-problem-Driver-e1000e/td-p/1420598 which shows that others are also running into similar issues with the device and I've just posted there too. Please give it a read in case something stands out. Thanks, Josh Q On Tue, Jun 27, 2023 at 10:27 PM Richard Cochran wrote: > > On Mon, Jun 26, 2023 at 09:42:27AM -0400, engn...@gmail.com wrote: > > > Created /etc/systemd/system/phc2sys_.service for each of the > > above 6 ports > > I think you want just ONE instance of phc2sys running, not six. > > Thanks, > Richard ___ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
Re: [Linuxptp-users] Newly Configured Machine Has Very Large Sys Offset
On Mon, Jun 26, 2023 at 09:42:27AM -0400, engn...@gmail.com wrote: > Created /etc/systemd/system/phc2sys_.service for each of the > above 6 ports I think you want just ONE instance of phc2sys running, not six. Thanks, Richard ___ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
[Linuxptp-users] Newly Configured Machine Has Very Large Sys Offset
Good Morning, I have a new system that I'm trying to setup as a PTP Grandmaster on an in-vehicle network. It will use upstream NTP servers to keep the time largely in sync with the rest of the world. The setup procedures I'm doing largely follow Ouster's PTP Quickstart Guide here: https://static.ouster.dev/sensor-docs/image_route1/image_route2/appendix/ptp -quickstart.html. /etc/linuxptp/ptp4l.conf Changed clockClass from 248 to 128 Appended: boundary_clock_jbod 1 [enp0s31f6] [eth1] [eth2] [eth3] [eth4] [eth5] Created /etc/systemd/system/ptp4l.service.d/override.conf: [Service] ExecStart= ExecStart=/usr/sbin/ptp4l -f /etc/linuxptp/ptp4l.conf Created /etc/systemd/system/phc2sys_.service for each of the above 6 ports After enabling services and restarting the system I'm seeing this output: Jun 26 13:41:13 hel-Nuvo phc2sys[8240]: [2617.426] enp0s31f6 sys offset 1457079943513 s0 freq +2399 delay 4880 Jun 26 13:41:14 hel-Nuvo phc2sys[8240]: [2618.426] clockcheck: clock jumped forward or running faster than expected! Jun 26 13:41:14 hel-Nuvo phc2sys[8240]: [2618.426] enp0s31f6 sys offset 1457641512370 s0 freq +2399 delay 4758 Jun 26 13:41:15 hel-Nuvo phc2sys[8240]: [2619.426] clockcheck: clock jumped forward or running faster than expected! Jun 26 13:41:15 hel-Nuvo phc2sys[8240]: [2619.426] enp0s31f6 sys offset 1458203078781 s0 freq +2399 delay 4636 Jun 26 13:41:16 hel-Nuvo phc2sys[8240]: [2620.426] clockcheck: clock jumped forward or running faster than expected! Jun 26 13:41:16 hel-Nuvo phc2sys[8240]: [2620.426] enp0s31f6 sys offset 1458764650543 s0 freq +2399 delay 5490 Jun 26 13:41:17 hel-Nuvo phc2sys[8240]: [2621.426] clockcheck: clock jumped forward or running faster than expected! Jun 26 13:41:17 hel-Nuvo phc2sys[8240]: [2621.426] enp0s31f6 sys offset 1459326242869 s0 freq +2399 delay 5490 Jun 26 13:41:18 hel-Nuvo phc2sys[8240]: [2622.427] clockcheck: clock jumped forward or running faster than expected! Jun 26 13:41:18 hel-Nuvo phc2sys[8240]: [2622.427] enp0s31f6 sys offset 1459887820658 s0 freq +2399 delay 5368 Jun 26 13:41:19 hel-Nuvo phc2sys[8240]: [2623.427] clockcheck: clock jumped forward or running faster than expected! Jun 26 13:41:19 hel-Nuvo phc2sys[8240]: [2623.427] enp0s31f6 sys offset 1460449399871 s0 freq +2399 delay 5490 Jun 26 13:41:20 hel-Nuvo phc2sys[8240]: [2624.427] clockcheck: clock jumped forward or running faster than expected! Jun 26 13:41:20 hel-Nuvo phc2sys[8240]: [2624.427] enp0s31f6 sys offset 1461010971817 s0 freq +2399 delay 5368 Jun 26 13:41:21 hel-Nuvo phc2sys[8240]: [2625.427] clockcheck: clock jumped forward or running faster than expected! Jun 26 13:41:21 hel-Nuvo phc2sys[8240]: [2625.427] enp0s31f6 sys offset 1461572561063 s0 freq +2399 delay 5368 Jun 26 13:41:22 hel-Nuvo phc2sys[8240]: [2626.427] clockcheck: clock jumped forward or running faster than expected! Jun 26 13:41:22 hel-Nuvo phc2sys[8240]: [2626.427] enp0s31f6 sys offset 1462134138947 s0 freq +2399 delay 5368 Jun 26 13:41:23 hel-Nuvo phc2sys[8240]: [2627.427] clockcheck: clock jumped forward or running faster than expected! Jun 26 13:41:23 hel-Nuvo phc2sys[8240]: [2627.427] enp0s31f6 sys offset 1462695708258 s0 freq +2399 delay 5368 Jun 26 13:41:24 hel-Nuvo phc2sys[8240]: [2628.427] clockcheck: clock jumped forward or running faster than expected! Jun 26 13:41:24 hel-Nuvo phc2sys[8240]: [2628.427] enp0s31f6 sys offset 1463257288175 s0 freq +2399 delay 5490 Jun 26 13:41:25 hel-Nuvo phc2sys[8240]: [2629.427] clockcheck: clock jumped forward or running faster than expected! Jun 26 13:41:25 hel-Nuvo phc2sys[8240]: [2629.427] enp0s31f6 sys offset 1463818857383 s0 freq +2399 delay 4514 It's continuously growing larger and I have no idea what's causing this. On another computer I tried this on I don't believe this was happening, so I'm looking for some help troubleshooting why it's happening. Thanks! Josh Q ___ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
