Hello Miroslav Lichvar,
Tried as suggested, observed below error.
ptp4l: [806352.926] clockcheck: clock jumped backward or running slower than
expected!
So set sanity_freq_limit to 0, but still observing errors:
ptp4l: [806913.536] timed out while polling for tx timestamp
ptp4l: [806913.536] in
Hello Miroslav Lichvar,
Please find the value of ptp config as per 8275.1 standards.
logAnnounceInterval -3
announceReceiptTimeout 3
We can't increase beyond the above values.
regards,
Ramesh
On Thursday, March 17, 2022, 04:10:38 PM GMT+5:30, Miroslav Lichvar
wrote:
On Wed, Mar 16
On Wed, Mar 16, 2022 at 06:23:23PM +, ramesh t via Linuxptp-users wrote:
> ptp4l: [704774.649] port 1: announce timeout
> ptp4l: [704774.649] port 1: SLAVE to MASTER on
> ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
>
> On debugging further, when port 2 is configured for down state, we call
> raw_close
Hello,
Have ptp4l running in BC mode providing clock to connected TestUnits (via port
2) and syncing clock from BC/GM (via port 1)
Did few more iterations of testing (ptp4l in BC mode) by doing ifconfig down.
Observing PTP4l reporting below error in port 1 connected to BC/GM
ptp4l: [704774.649
