James Clark

It can also happen if the compoled-in leap second table is out of date. They have an expiry date 6 months in the future. There’s a optoon to specify a...

Questions here: - What is causing the bad pulse? - Is it the M8T? If so, is it the antenna placement or something else? - Is it the kernel confusing...

Here's another one: ``` Nov 16 12:39:14 wensleydale ts2phc: [349041.521] eth0 extts index 0 at 1668577190.999999988 corr 0 src 1668577191.18746814 diff -12 Nov 16 12:39:14 wensleydale ts2phc: [349041.521] eth0 master...

I'm not seeing this at all on another system. System that shows the problem: - GPS module is LEA-M8T on a Huawei [board](https://www.ebay.com/itm/134243322249) - Waveshare IO [board](https://www.waveshare.com/compute-module-4-poe-board.htm) with PoE -...

More details of problem here https://github.com/raspberrypi/linux/issues/5231 Summary is it's a hardware limitation, which the driver hasn't been able to fully workaround.

The kernel gets into a state where it delivers 4 extts events in a second: ``` Nov 7 20:09:45 ricotta ts2phc: [1911220.240] eth0 extts index 0 at 1667826586.175084690 corr 0...

This is exacerbated by the fact that the default value for `step_threshold` is 0, which means that ts2phc won't step the clock to correct the bad time. We can alleviate...

Using `-c /dev/ptp0` rather `-c eth0` also seems to avoid the problem.

linuxptp tests this by looking at phc_index in the ethtool_ts_info struct returned by SIOCETHTOOL with a ETHTOOL_GET_TS_INFO command. When I do `ethtool -T eth0` from systemd, it shows no hardware...

We can workaround this by adding a unit ` /etc/systemd/system/[email protected]` ``` [Unit] Description=Ensure PTP hardware clock (PHC) of %I is ready Documentation=man:phc_ctl After=sys-subsystem-net-devices-%i.device Before=ptp4l@%i.service [Service] Type=oneshot ExecStart=/usr/sbin/phc_ctl -Q %I RemainAfterExit=yes...