Il 28/03/23 12:14, Vladimir Oltean ha scritto:
On Tue, Mar 28, 2023 at 11:29:02AM +0200, Riccardo Laiolo wrote:
Hi there,
I'm working on a custom NXP iMX8 SoM connected to a Marvell MV88E6390 switch on
port0 (eth0 as management port).
Five switch ports are exposed to the outside and bridged together in a dsa
device (br0 soft bridge).
I'm running iMX linux-5.15.71 from NXP downstream repository.
I need my device to be a ptp device (master or slave depending on the specific
application).
Since I can ping other PCs on the network I think Marvell DSA drivers are
working, but ptp is not working.
I found and backported this patch
(https://github.com/torvalds/linux/commit/9627c981ac82209c66c1b6c0e15c6cceb8656f01)
into my codebase, but when I launch ptp4l it's not working properly. Launching
ptp4l on eth0 it says eth0 is
rejecting HWTSTAMP filtering configuration. Launching ptp4l on an outside
facing port (lan1:5), instead, using IPv4
or IPv6 transport, it's like my SoM can't talk to other ptp devices: if my SoM
is a ptp master i see announce, sync,
and follow-up messages get sent, and I see dly_req from other slaves coming
back, but there are no dly_resp at all.
When my som is slave there are no packets from it. It's like all ptp related
packets get ignored.
Is it possible to run ptp on eth0 (or on br0)? I want to syncronize devices on
all the front facing ports.
I've attached `ip a` output, `ethtool -T eth0` output, and `ethtool -T lan1`
output.
"ethtool -T lan1" reports that the switch ports only support L2 PTP, so
no IPv4 and no IPv6.
Thanks for your reply,
why are you saying there's no IP support? I thought ethtool was saying there is
both L2 and L4 filtering capabilities.
Hardware Receive Filter Modes:
none
ptpv2-l4-event
ptpv2-l4-sync
ptpv2-l4-delay-req
ptpv2-l2-event
ptpv2-l2-sync
ptpv2-l2-delay-req
ptpv2-event
ptpv2-sync
ptpv2-delay-req
PTP hardware timestamping on eth0 (the DSA master) is rejected if the
switch supports hardware timestamping too, because the kernel does not
support reporting more than 1 TX timestamp per packet (or rather, it
does report multiple timestamps, but it doesn't tell user space where
they came from). Since a choice needs to be made even with the
limitations in place, that current choice is to only allow PTP hardware
timestamping on the DSA switch ports, if those support this operation,
or on the DSA master if the switch doesn't support hardware timestamping.
Ok, that seems reasonable. Thanks for the insight.
PTP hardware timestamping does not work on a bridge interface, for the
same basic reason that a bridge forwards packets to potentially multiple
ports, and it is not immediately clear, when an application sees a
timestamp coming from a bridge interface, which bridge port took that
timestamp (they may have different PHCs).
This only leaves you a single option:
ptp4l -i lan1 -i lan2 -i lan3 [ ... ] -2 -P -m --tx_timestamp_timeout 40
Finally, I tried to launch ptp4l on my board as master (on all of the
front-facing port)
with -2 and it's working as expected, since all the (slave-only) devices are
synchronising to it.
On the other hand if I configure my board as a slave-only device (-s flag) it's
not working.
I've attached two logs, in the first one i launched ptp4l with -i on all ports,
but it's noisy and unreadable!
Anyway, the master was on port3 and on port5 was a second slave.
In the second one i passed -i lan3 (the port connected directly to the ptp
master device)
Thanks for the help,
RL
--
Riccardo Laiolo
Leaff Engineering - Digital Solutions & Algorithms
ptp4l -H -2 -mq --tx_timestamp_timeout=40 -i lan1 -i lan2 -i lan3 -i lan4 -i lan8 -P -s
ptp4l[1857.322]: selected /dev/ptp0 as PTP clock
ptp4l[1857.353]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1857.377]: port 2: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1857.409]: port 3: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1857.433]: port 4: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1857.457]: port 5: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1857.457]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1857.458]: port 1: received SYNC without timestamp
ptp4l[1857.458]: port 2: link down
ptp4l[1857.458]: port 2: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1857.481]: port 4: link down
ptp4l[1857.481]: port 4: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1857.532]: port 5: received SYNC without timestamp
ptp4l[1857.532]: selected local clock 4e1d45.fffe.aeb507 as best master
ptp4l[1857.532]: port 2: assuming the grand master role
ptp4l[1857.532]: port 2: master state recommended in slave only mode
ptp4l[1857.532]: port 2: defaultDS.priority1 probably misconfigured
ptp4l[1857.532]: port 4: assuming the grand master role
ptp4l[1857.532]: port 4: master state recommended in slave only mode
ptp4l[1857.532]: port 4: defaultDS.priority1 probably misconfigured
ptp4l[1857.988]: timed out while polling for tx timestamp
ptp4l[1857.988]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1857.988]: port 3: send peer delay response failed
ptp4l[1857.988]: port 3: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1858.346]: timed out while polling for tx timestamp
ptp4l[1858.346]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1858.346]: port 5: send peer delay response failed
ptp4l[1858.346]: port 5: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1858.413]: timed out while polling for tx timestamp
ptp4l[1858.413]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1858.413]: port 1: send peer delay request failed
ptp4l[1858.413]: port 1: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1874.041]: port 3: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1874.397]: port 5: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1874.473]: port 1: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1874.473]: port 5: received SYNC without timestamp
ptp4l[1874.473]: port 3: new foreign master f8dc7a.fffe.739f22-1
ptp4l[1874.473]: port 5: new foreign master f8dc7a.fffe.739f22-1
ptp4l[1875.364]: timed out while polling for tx timestamp
ptp4l[1875.364]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1875.364]: port 5: send peer delay response failed
ptp4l[1875.364]: port 5: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1875.447]: port 1: received SYNC without timestamp
ptp4l[1875.514]: timed out while polling for tx timestamp
ptp4l[1875.514]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1875.514]: port 1: send peer delay request failed
ptp4l[1875.514]: port 1: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1878.445]: selected best master clock f8dc7a.fffe.739f22
ptp4l[1878.446]: port 1: master state recommended in slave only mode
ptp4l[1878.446]: port 1: defaultDS.priority1 probably misconfigured
ptp4l[1878.446]: port 2: master state recommended in slave only mode
ptp4l[1878.446]: port 2: defaultDS.priority1 probably misconfigured
ptp4l[1878.446]: port 3: LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[1878.446]: port 4: master state recommended in slave only mode
ptp4l[1878.446]: port 4: defaultDS.priority1 probably misconfigured
ptp4l[1878.446]: port 5: master state recommended in slave only mode
ptp4l[1878.446]: port 5: defaultDS.priority1 probably misconfigured
ptp4l[1879.447]: master offset 104447 s0 freq +1000000 path delay 367
ptp4l[1880.448]: master offset 104509 s1 freq +1000000 path delay 367
ptp4l[1881.447]: master offset 62 s2 freq +1000000 path delay 367
ptp4l[1881.448]: port 3: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[1882.448]: master offset 131 s2 freq +1000000 path delay 366
ptp4l[1883.448]: master offset 190 s2 freq +1000000 path delay 366
ptp4l[1884.448]: master offset 269 s2 freq +1000000 path delay 365
ptp4l[1885.448]: master offset 323 s2 freq +1000000 path delay 365
ptp4l[1886.447]: master offset 390 s2 freq +1000000 path delay 366
ptp4l[1887.448]: master offset 486 s2 freq +1000000 path delay 367
ptp4l[1888.448]: master offset 594 s2 freq +1000000 path delay 367
ptp4l[1889.448]: master offset 689 s2 freq +1000000 path delay 366
ptp4l[1890.448]: master offset 780 s2 freq +1000000 path delay 366
ptp4l[1891.425]: port 5: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1891.448]: master offset 859 s2 freq +1000000 path delay 367
ptp4l[1891.448]: port 5: received SYNC without timestamp
ptp4l[1891.569]: port 1: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1892.381]: timed out while polling for tx timestamp
ptp4l[1892.381]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1892.381]: port 5: send peer delay response failed
ptp4l[1892.381]: port 5: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1892.446]: port 1: new foreign master f8dc7a.fffe.739f22-1
ptp4l[1892.448]: master offset 941 s2 freq +1000000 path delay 367
ptp4l[1892.448]: port 1: received SYNC without timestamp
ptp4l[1892.609]: timed out while polling for tx timestamp
ptp4l[1892.609]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1892.609]: port 1: send peer delay request failed
ptp4l[1892.609]: port 1: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1893.448]: master offset 1006 s2 freq +1000000 path delay 367
ptp4l[1894.448]: master offset 1081 s2 freq +1000000 path delay 367
ptp4l[1895.448]: master offset 1133 s2 freq +1000000 path delay 367
ptp4l[1896.448]: master offset 1214 s2 freq +1000000 path delay 367
ptp4l[1897.448]: master offset 1277 s2 freq +1000000 path delay 367
ptp4l[1898.448]: master offset 1335 s2 freq +1000000 path delay 367
ptp4l[1899.448]: master offset 1401 s2 freq +1000000 path delay 367
ptp4l[1900.448]: master offset 1471 s2 freq +1000000 path delay 367
ptp4l[1901.448]: master offset 1532 s2 freq +1000000 path delay 368
ptp4l[1902.448]: master offset 1614 s2 freq +1000000 path delay 368
ptp4l[1903.448]: master offset 1679 s2 freq +1000000 path delay 368
ptp4l[1904.448]: master offset 1732 s2 freq +1000000 path delay 369
ptp4l[1905.449]: master offset 1803 s2 freq +1000000 path delay 369
ptp4l[1906.448]: master offset 1865 s2 freq +1000000 path delay 368
ptp4l[1907.449]: master offset 1926 s2 freq +1000000 path delay 367
ptp4l[1908.437]: port 5: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1908.446]: port 5: new foreign master f8dc7a.fffe.739f22-1
ptp4l[1908.448]: master offset 2005 s2 freq +1000000 path delay 367
ptp4l[1908.448]: port 5: received SYNC without timestamp
ptp4l[1908.665]: port 1: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1909.399]: timed out while polling for tx timestamp
ptp4l[1909.399]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1909.399]: port 5: send peer delay response failed
ptp4l[1909.399]: port 5: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1909.448]: port 1: received SYNC without timestamp
ptp4l[1909.449]: master offset 2090 s2 freq +1000000 path delay 368
ptp4l[1909.706]: timed out while polling for tx timestamp
ptp4l[1909.706]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1909.706]: port 1: send peer delay request failed
ptp4l[1909.706]: port 1: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1910.448]: master offset 2175 s2 freq +1000000 path delay 368
ptp4l[1911.448]: master offset 2259 s2 freq +1000000 path delay 368
ptp4l[1912.451]: master offset 2323 s2 freq +1000000 path delay 368
ptp4l[1913.449]: master offset 2406 s2 freq +1000000 path delay 368
ptp4l[1914.448]: master offset 2488 s2 freq +1000000 path delay 368
ptp4l[1915.449]: master offset 2563 s2 freq +1000000 path delay 368
ptp4l[1916.449]: master offset 2646 s2 freq +1000000 path delay 368
ptp4l[1917.449]: master offset 2744 s2 freq +1000000 path delay 368
ptp4l[1918.449]: master offset 2861 s2 freq +1000000 path delay 368
ptp4l[1919.449]: master offset 2973 s2 freq +1000000 path delay 368
ptp4l[1920.449]: master offset 3087 s2 freq +1000000 path delay 368
ptp4l[1921.449]: master offset 3174 s2 freq +1000000 path delay 368
ptp4l[1922.449]: master offset 3260 s2 freq +1000000 path delay 368
ptp4l[1923.449]: master offset 3361 s2 freq +1000000 path delay 369
ptp4l[1924.449]: master offset 3485 s2 freq +1000000 path delay 371
ptp4l[1925.453]: port 5: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1925.454]: master offset 3609 s2 freq +1000000 path delay 371
ptp4l[1925.454]: port 5: received SYNC without timestamp
ptp4l[1925.758]: port 1: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1926.417]: timed out while polling for tx timestamp
ptp4l[1926.417]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1926.417]: port 5: send peer delay response failed
ptp4l[1926.417]: port 5: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1926.446]: port 1: new foreign master f8dc7a.fffe.739f22-1
ptp4l[1926.449]: port 1: received SYNC without timestamp
ptp4l[1926.449]: master offset 3743 s2 freq +1000000 path delay 371
ptp4l[1926.798]: timed out while polling for tx timestamp
ptp4l[1926.798]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1926.798]: port 1: send peer delay request failed
ptp4l[1926.798]: port 1: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1927.449]: master offset 3855 s2 freq +1000000 path delay 371
ptp4l[1928.449]: master offset 3998 s2 freq +1000000 path delay 371
ptp4l[1929.449]: master offset 4121 s2 freq +1000000 path delay 370
ptp4l[1930.449]: master offset 4226 s2 freq +1000000 path delay 370
ptp4l[1931.449]: master offset 4350 s2 freq +1000000 path delay 370
ptp4l[1932.449]: master offset 4438 s2 freq +1000000 path delay 370
ptp4l[1933.449]: master offset 4541 s2 freq +1000000 path delay 370
ptp4l[1934.449]: master offset 4653 s2 freq +1000000 path delay 369
ptp4l[1935.449]: master offset 4746 s2 freq +1000000 path delay 369
ptp4l[1936.449]: master offset 4829 s2 freq +1000000 path delay 368
ptp4l[1937.450]: master offset 4915 s2 freq +1000000 path delay 367
ptp4l[1938.449]: master offset 4994 s2 freq +1000000 path delay 367
ptp4l[1939.450]: master offset 5045 s2 freq +1000000 path delay 367
ptp4l[1940.449]: master offset 5114 s2 freq +1000000 path delay 367
ptp4l[1941.450]: master offset 5177 s2 freq +1000000 path delay 367
ptp4l[1942.473]: port 5: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1942.474]: master offset 5240 s2 freq +1000000 path delay 367
ptp4l[1942.853]: port 1: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1943.435]: timed out while polling for tx timestamp
ptp4l[1943.435]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1943.435]: port 5: send peer delay response failed
ptp4l[1943.435]: port 5: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1943.464]: port 1: received SYNC without timestamp
ptp4l[1943.465]: master offset 5272 s2 freq +1000000 path delay 367
ptp4l[1943.894]: timed out while polling for tx timestamp
ptp4l[1943.894]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1943.894]: port 1: send peer delay request failed
ptp4l[1943.894]: port 1: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1944.449]: master offset 5312 s2 freq +1000000 path delay 367
ptp4l[1945.450]: master offset 5331 s2 freq +1000000 path delay 367
ptp4l[1946.450]: master offset 5384 s2 freq +1000000 path delay 367
ptp4l[1947.450]: master offset 5433 s2 freq +1000000 path delay 367
ptp4l[1948.450]: master offset 5513 s2 freq +1000000 path delay 367
ptp4l[1949.450]: master offset 5582 s2 freq +1000000 path delay 367
ptp4l[1950.449]: master offset 5660 s2 freq +1000000 path delay 367
ptp4l[1951.450]: master offset 5733 s2 freq +1000000 path delay 367
ptp4l[1952.450]: master offset 5788 s2 freq +1000000 path delay 367
ptp4l[1953.450]: master offset 5851 s2 freq +1000000 path delay 369
ptp4l[1954.449]: master offset 5928 s2 freq +1000000 path delay 369
ptp4l[1955.450]: master offset 6008 s2 freq +1000000 path delay 370
ptp4l[1956.450]: master offset 6075 s2 freq +1000000 path delay 369
ptp4l[1957.450]: master offset 6157 s2 freq +1000000 path delay 370
ptp4l[1958.450]: master offset 6208 s2 freq +1000000 path delay 371
ptp4l[1959.451]: master offset 6282 s2 freq +1000000 path delay 371
ptp4l[1959.489]: port 5: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1959.941]: port 1: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1960.452]: timed out while polling for tx timestamp
ptp4l[1960.452]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1960.452]: port 5: send peer delay response failed
ptp4l[1960.452]: port 5: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1960.480]: port 1: received SYNC without timestamp
ptp4l[1960.480]: port 1: new foreign master f8dc7a.fffe.739f22-1
ptp4l[1960.481]: master offset 6338 s2 freq +1000000 path delay 371
ptp4l[1960.982]: timed out while polling for tx timestamp
ptp4l[1960.982]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1960.982]: port 1: send peer delay request failed
ptp4l[1960.982]: port 1: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1961.450]: master offset 6376 s2 freq +1000000 path delay 371
ptp4l[1962.450]: master offset 6420 s2 freq +1000000 path delay 369
ptp4l[1963.450]: master offset 6471 s2 freq +1000000 path delay 369
ptp4l[1964.450]: master offset 6513 s2 freq +1000000 path delay 370
ptp4l[1965.450]: master offset 6571 s2 freq +1000000 path delay 368
ptp4l[1966.450]: master offset 6618 s2 freq +1000000 path delay 370
ptp4l[1967.450]: master offset 6692 s2 freq +1000000 path delay 368
ptp4l[1968.450]: master offset 6751 s2 freq +1000000 path delay 367
ptp4l[1969.451]: master offset 6837 s2 freq +1000000 path delay 367
ptp4l[1970.450]: master offset 6898 s2 freq +1000000 path delay 367
ptp4l[1971.450]: master offset 6950 s2 freq +1000000 path delay 367
ptp4l[1972.450]: master offset 7008 s2 freq +1000000 path delay 367
ptp4l[1973.450]: master offset 7083 s2 freq +1000000 path delay 369
ptp4l[1974.450]: master offset 7183 s2 freq +1000000 path delay 369
ptp4l[1975.450]: master offset 7263 s2 freq +1000000 path delay 369
ptp4l[1976.450]: master offset 7351 s2 freq +1000000 path delay 366
ptp4l[1976.517]: port 5: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1977.041]: port 1: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1977.470]: timed out while polling for tx timestamp
ptp4l[1977.470]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1977.470]: port 5: send peer delay response failed
ptp4l[1977.470]: port 5: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1977.500]: port 1: received SYNC without timestamp
ptp4l[1977.501]: master offset 7424 s2 freq +1000000 path delay 369
ptp4l[1978.082]: timed out while polling for tx timestamp
ptp4l[1978.082]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[1978.082]: port 1: send peer delay request failed
ptp4l[1978.082]: port 1: LISTENING to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[1978.450]: master offset 7516 s2 freq +1000000 path delay 370
ptp4l[1979.450]: master offset 7604 s2 freq +1000000 path delay 369
ptp4l[1980.450]: master offset 7724 s2 freq +1000000 path delay 369
ptp4l[1981.450]: master offset 7842 s2 freq +1000000 path delay 369
ptp4l[1982.450]: master offset 7957 s2 freq +1000000 path delay 368
ptp4l[1983.451]: master offset 8066 s2 freq +1000000 path delay 368
root@imx8mp-leaff-evk:~# ptp4l -H -2 -mq --tx_timestamp_timeout=40 -i lan3 -P -s
ptp4l[2088.019]: selected /dev/ptp0 as PTP clock
ptp4l[2088.061]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[2088.062]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[2088.450]: port 1: new foreign master f8dc7a.fffe.739f22-1
ptp4l[2092.450]: selected best master clock f8dc7a.fffe.739f22
ptp4l[2092.450]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[2093.454]: master offset 17828 s0 freq +1000000 path delay 371
ptp4l[2094.455]: master offset 17903 s2 freq +1000000 path delay 370
ptp4l[2094.455]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[2095.455]: master offset 17973 s2 freq +1000000 path delay 369
ptp4l[2096.455]: master offset 18048 s2 freq +1000000 path delay 370
ptp4l[2097.455]: master offset 18121 s2 freq +1000000 path delay 369
ptp4l[2098.455]: master offset 18184 s2 freq +1000000 path delay 369
ptp4l[2099.455]: master offset 18277 s2 freq +1000000 path delay 369
ptp4l[2100.455]: master offset 18371 s2 freq +1000000 path delay 371
ptp4l[2101.455]: master offset 18480 s2 freq +1000000 path delay 370
ptp4l[2102.455]: master offset 18597 s2 freq +1000000 path delay 370
ptp4l[2103.455]: master offset 18723 s2 freq +1000000 path delay 369
ptp4l[2104.455]: master offset 18851 s2 freq +1000000 path delay 368
ptp4l[2105.455]: master offset 18999 s2 freq +1000000 path delay 368
ptp4l[2106.455]: master offset 19143 s2 freq +1000000 path delay 368
ptp4l[2107.455]: master offset 19277 s2 freq +1000000 path delay 367
ptp4l[2108.455]: master offset 19404 s2 freq +1000000 path delay 369
ptp4l[2109.455]: master offset 19534 s2 freq +1000000 path delay 367
ptp4l[2110.455]: master offset 19638 s2 freq +1000000 path delay 367
ptp4l[2111.455]: master offset 19783 s2 freq +1000000 path delay 367
ptp4l[2112.456]: master offset 19921 s2 freq +1000000 path delay 367
ptp4l[2113.456]: master offset 20085 s2 freq +1000000 path delay 367
ptp4l[2114.456]: master offset 20225 s2 freq +1000000 path delay 368
ptp4l[2115.456]: master offset 20379 s2 freq +1000000 path delay 368
ptp4l[2116.456]: master offset 20545 s2 freq +1000000 path delay 367
ptp4l[2117.456]: master offset 20696 s2 freq +1000000 path delay 367
ptp4l[2118.455]: master offset 20856 s2 freq +1000000 path delay 366
ptp4l[2119.456]: master offset 21015 s2 freq +1000000 path delay 366
ptp4l[2120.455]: master offset 21182 s2 freq +1000000 path delay 366
ptp4l[2121.456]: master offset 21339 s2 freq +1000000 path delay 366
ptp4l[2122.456]: master offset 21512 s2 freq +1000000 path delay 367
ptp4l[2123.456]: master offset 21680 s2 freq +1000000 path delay 366
ptp4l[2124.456]: master offset 21811 s2 freq +1000000 path delay 366
ptp4l[2125.455]: master offset 21948 s2 freq +1000000 path delay 365
ptp4l[2126.456]: master offset 22072 s2 freq +1000000 path delay 367
ptp4l[2127.458]: master offset 22182 s2 freq +1000000 path delay 367
ptp4l[2128.456]: master offset 22271 s2 freq +1000000 path delay 368
ptp4l[2129.456]: master offset 22382 s2 freq +1000000 path delay 370
ptp4l[2130.456]: master offset 22459 s2 freq +1000000 path delay 368
ptp4l[2131.456]: master offset 22556 s2 freq +1000000 path delay 368
ptp4l[2132.456]: master offset 22647 s2 freq +1000000 path delay 366
ptp4l[2133.457]: master offset 22731 s2 freq +1000000 path delay 367
ptp4l[2134.456]: master offset 22827 s2 freq +1000000 path delay 367
ptp4l[2135.456]: master offset 22936 s2 freq +1000000 path delay 367
ptp4l[2136.456]: master offset 23047 s2 freq +1000000 path delay 366
ptp4l[2137.456]: master offset 23158 s2 freq +1000000 path delay 367
ptp4l[2138.456]: master offset 23259 s2 freq +1000000 path delay 367
ptp4l[2139.456]: master offset 23358 s2 freq +1000000 path delay 366
ptp4l[2140.456]: master offset 23466 s2 freq +1000000 path delay 367
ptp4l[2141.457]: master offset 23591 s2 freq +1000000 path delay 366
ptp4l[2142.456]: master offset 23708 s2 freq +1000000 path delay 366
ptp4l[2143.456]: master offset 23867 s2 freq +1000000 path delay 366
ptp4l[2144.456]: master offset 23997 s2 freq +1000000 path delay 366
ptp4l[2145.456]: master offset 24153 s2 freq +1000000 path delay 366
ptp4l[2146.457]: master offset 24299 s2 freq +1000000 path delay 367
ptp4l[2147.457]: master offset 24469 s2 freq +1000000 path delay 366
ptp4l[2148.457]: master offset 24603 s2 freq +1000000 path delay 366
ptp4l[2149.457]: master offset 24767 s2 freq +1000000 path delay 368
ptp4l[2150.457]: master offset 24938 s2 freq +1000000 path delay 368
ptp4l[2151.457]: master offset 25105 s2 freq +1000000 path delay 368
ptp4l[2152.457]: master offset 25258 s2 freq +1000000 path delay 368
ptp4l[2153.457]: master offset 25404 s2 freq +1000000 path delay 369
ptp4l[2154.457]: master offset 25506 s2 freq +1000000 path delay 369
ptp4l[2155.457]: master offset 25601 s2 freq +1000000 path delay 369
ptp4l[2156.457]: master offset 25667 s2 freq +1000000 path delay 369
ptp4l[2157.457]: master offset 25739 s2 freq +1000000 path delay 369
ptp4l[2158.457]: master offset 25811 s2 freq +1000000 path delay 367
ptp4l[2159.458]: master offset 25861 s2 freq +1000000 path delay 366
ptp4l[2160.457]: master offset 25913 s2 freq +1000000 path delay 366
ptp4l[2161.457]: master offset 25942 s2 freq +1000000 path delay 369
ptp4l[2162.457]: master offset 25945 s2 freq +1000000 path delay 369
ptp4l[2163.457]: master offset 25949 s2 freq +1000000 path delay 370
ptp4l[2164.457]: master offset 25947 s2 freq +1000000 path delay 368
ptp4l[2165.457]: master offset 25954 s2 freq +1000000 path delay 368
ptp4l[2166.457]: master offset 25927 s2 freq +1000000 path delay 369
ptp4l[2167.457]: master offset 25911 s2 freq +1000000 path delay 369
ptp4l[2168.457]: master offset 25881 s2 freq +1000000 path delay 369
ptp4l[2169.457]: master offset 25839 s2 freq +1000000 path delay 370
ptp4l[2170.457]: master offset 25813 s2 freq +1000000 path delay 369
ptp4l[2171.458]: master offset 25776 s2 freq +1000000 path delay 369
ptp4l[2172.458]: master offset 25756 s2 freq +1000000 path delay 369
ptp4l[2173.458]: master offset 25778 s2 freq +1000000 path delay 368
ptp4l[2174.458]: master offset 25765 s2 freq +1000000 path delay 367
ptp4l[2175.458]: master offset 25776 s2 freq +1000000 path delay 367
ptp4l[2176.458]: master offset 25808 s2 freq +1000000 path delay 367
ptp4l[2177.458]: master offset 25827 s2 freq +1000000 path delay 367
ptp4l[2178.458]: master offset 25845 s2 freq +1000000 path delay 368
ptp4l[2179.458]: master offset 25893 s2 freq +1000000 path delay 367
ptp4l[2180.458]: master offset 25911 s2 freq +1000000 path delay 368
ptp4l[2181.458]: master offset 25955 s2 freq +1000000 path delay 366
ptp4l[2182.458]: master offset 25957 s2 freq +1000000 path delay 366
ptp4l[2183.458]: master offset 25970 s2 freq +1000000 path delay 368
ptp4l[2184.458]: master offset 25991 s2 freq +1000000 path delay 368
ptp4l[2185.459]: master offset 25982 s2 freq +1000000 path delay 368
ptp4l[2186.458]: master offset 25968 s2 freq +1000000 path delay 368
ptp4l[2187.458]: master offset 25934 s2 freq +1000000 path delay 369
ptp4l[2188.458]: master offset 25915 s2 freq +1000000 path delay 371
ptp4l[2189.458]: master offset 25895 s2 freq +1000000 path delay 371
ptp4l[2190.458]: master offset 25868 s2 freq +1000000 path delay 371
ptp4l[2191.458]: master offset 25862 s2 freq +1000000 path delay 371
ptp4l[2192.458]: master offset 25859 s2 freq +1000000 path delay 371
ptp4l[2193.458]: master offset 25896 s2 freq +1000000 path delay 371
ptp4l[2194.458]: master offset 25935 s2 freq +1000000 path delay 371
ptp4l[2195.458]: master offset 26003 s2 freq +1000000 path delay 370
ptp4l[2196.458]: master offset 26083 s2 freq +1000000 path delay 369
ptp4l[2197.458]: master offset 26129 s2 freq +1000000 path delay 369
ptp4l[2198.458]: master offset 26160 s2 freq +1000000 path delay 369
ptp4l[2199.458]: master offset 26171 s2 freq +1000000 path delay 370
ptp4l[2200.458]: master offset 26176 s2 freq +1000000 path delay 370
ptp4l[2201.459]: master offset 26173 s2 freq +1000000 path delay 371
ptp4l[2202.458]: master offset 26169 s2 freq +1000000 path delay 369
ptp4l[2203.459]: master offset 26177 s2 freq +1000000 path delay 371
ptp4l[2204.458]: master offset 26191 s2 freq +1000000 path delay 373
ptp4l[2205.459]: master offset 26225 s2 freq +1000000 path delay 373
ptp4l[2206.459]: master offset 26243 s2 freq +1000000 path delay 373
ptp4l[2207.459]: master offset 26272 s2 freq +1000000 path delay 372
ptp4l[2208.459]: master offset 26323 s2 freq +1000000 path delay 371
ptp4l[2209.459]: master offset 26359 s2 freq +1000000 path delay 370
ptp4l[2210.459]: master offset 26398 s2 freq +1000000 path delay 371
ptp4l[2211.460]: master offset 26451 s2 freq +1000000 path delay 371
ptp4l[2212.459]: master offset 26516 s2 freq +1000000 path delay 372
ptp4l[2213.459]: master offset 26602 s2 freq +1000000 path delay 371
ptp4l[2214.459]: master offset 26660 s2 freq +1000000 path delay 370
ptp4l[2215.459]: master offset 26724 s2 freq +1000000 path delay 370
ptp4l[2216.459]: master offset 26766 s2 freq +1000000 path delay 370
ptp4l[2217.459]: master offset 26786 s2 freq +1000000 path delay 371
ptp4l[2218.459]: master offset 26780 s2 freq +1000000 path delay 369
ptp4l[2219.459]: master offset 26792 s2 freq +1000000 path delay 369
ptp4l[2220.459]: master offset 26774 s2 freq +1000000 path delay 369
ptp4l[2221.459]: master offset 26796 s2 freq +1000000 path delay 369
ptp4l[2222.459]: master offset 26782 s2 freq +1000000 path delay 369
ptp4l[2223.459]: master offset 26782 s2 freq +1000000 path delay 369
ptp4l[2224.459]: master offset 26786 s2 freq +1000000 path delay 369
ptp4l[2225.459]: master offset 26796 s2 freq +1000000 path delay 369
ptp4l[2226.459]: master offset 26792 s2 freq +1000000 path delay 368
ptp4l[2227.459]: master offset 26799 s2 freq +1000000 path delay 367
ptp4l[2228.459]: master offset 26827 s2 freq +1000000 path delay 367
ptp4l[2229.459]: master offset 26832 s2 freq +1000000 path delay 368
ptp4l[2230.459]: master offset 26842 s2 freq +1000000 path delay 367
ptp4l[2231.460]: master offset 26846 s2 freq +1000000 path delay 367
ptp4l[2232.460]: master offset 26865 s2 freq +1000000 path delay 369
ptp4l[2233.459]: master offset 26874 s2 freq +1000000 path delay 368
ptp4l[2234.459]: master offset 26881 s2 freq +1000000 path delay 368
ptp4l[2235.460]: master offset 26936 s2 freq +1000000 path delay 367
ptp4l[2236.460]: master offset 26969 s2 freq +1000000 path delay 367
ptp4l[2237.460]: master offset 27014 s2 freq +1000000 path delay 371
ptp4l[2238.460]: master offset 27085 s2 freq +1000000 path delay 367
ptp4l[2239.460]: master offset 27148 s2 freq +1000000 path delay 367
ptp4l[2240.460]: master offset 27210 s2 freq +1000000 path delay 367
ptp4l[2241.460]: master offset 27265 s2 freq +1000000 path delay 367
ptp4l[2242.459]: master offset 27356 s2 freq +1000000 path delay 366
ptp4l[2243.460]: master offset 27434 s2 freq +1000000 path delay 366
ptp4l[2244.459]: master offset 27506 s2 freq +1000000 path delay 369
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
