Re: [Linuxptp-users] rogue peer delay response caused by port_synchronize()

[Miroslav L. <mli...@re...>]

On Tue, Mar 21, 2023 at 10:17:56AM +0800, merlinhe wrote:
> 1. after the first clock jumpping, PHC jumpped to master, SYS keep the
> original value
> 2. peer_delay_req set to NUL
> 3. when the next peer_delay_resp arrives, the port enters the faulty state,
> which cause the port reinited(PHC reset to SYS)

By phc2sys? System clock shouldn't be used at all with HW
timestamping.

> 4. then the next SYNC, FUP arrives, the clock.servo enter LOCK state,
> 
> Do you have any suggestions to fix this problem? Or do I need to change my
> ptp4l configuration?

It's not very clear to me what is the issue that you are trying to
avoid.

-- 
Miroslav Lichvar