The delay timer wasn't reset when ptp4l was configured to select the delay mechanism automatically and P2P delay mechanism was selected.
ptp4l didn't make any peer delay measurements.
The P2P timer is reset when P2P mechanism is selected.
Peer delay is measured correctly when ptp4l is configured to select the delay mechanism automatically.
Description of problem:
When ptp4l is configured to use the Auto delay mechanism and it receives a P2P request when the E2E delay timer is not running, it will switch to P2P, but not make any P2P requests itself.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run ptp4l master with P2P
2. run ptp4l slave with Auto
3. monitor slave log
ptp4l not making any clock updates
ptp4l reporting master offsets and making clock updates
This is fixed by upstream commit b366b79306f0d5d8c7da0ae10acdca2b01cb54fe.
Test 18-autodm from https://github.com/mlichvar/linuxptp-testsuite tests this bug.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.