Bug#1070847:

2025-01-02 Thread Michael Byczkowski
The issue seems to be a misconfiguration in the standard /lib/systemd/system/ptp4l@.service: apparently, it starts already when the network (hardware) is not fully up and running – at least on my Raspberry Pi5 is not sufficiently up (running current Debian bookworm from Raspberry with Network M

Bug#1070847: ptp4l systemd-service starts before hardware is fully up

2024-05-10 Thread Michael Byczkowski
Package: linuxptp Version: 4.2-1 When (re-)booting the system the dependencies of ptp4l@.service (and phc2sys@.service) do not seem to be sufficient as the hardware (in this case eth0) is not up and running when those services are started, leading to a fail in SIOCSHWTSTAMP when using phc2sys -