PTP timestamps, published by HSB, aren't synchonized with the host time.

[p-ogrady]

The user guide hardware setup instructions show how to configure the phc2sys tool, which ensures that the NIC time-of-day clock (which is published in PTP network messages) is synchronized with the host real-time clock. The setup instructions rely on the default ntpdate configuration to initialize the system clock with the current real-world time. As written in the user guide, the phc2sys startup doesn't properly wait for ntpdate to complete, so that when ntpdate does finish, phc2sys sees a large jump in the system time. Because phc2sys slowly adjusts the NIC clock, the time published by ptp4l will then not be synchronized with the system clock, and could take a very long time to do so. This has the effect of publishing a time with ingress data that is out-of-sync with the system time.

To verify you're in this condition, observe the output in the "sys offset" column from the command systemctl status phc2sys-*.service; large absolute values are an indication of this condition.

To work around this, run sudo systemctl restart phc2sys-*.service after ntpdate is synchronized. There is some anecdotal evidence that adding "-w" to the phc2sys command line may fix this problem but the documentation for this option doesn't address the configuration in use here.