Re: [Linuxptp-users] ptp4l and Broadcom 5720 problem

[Jay S. <li...@sh...>]

On 07/06/2022 10:28, Miroslav Lichvar wrote:
> On Tue, Jun 07, 2022 at 10:13:31AM +0100, Jay Shardlow wrote:
>> At this point I'm slightly out of my depth and out of ideas. The Broadcom
>> obviously does work (or they wouldn't advertise it as such), so must be
>> something with my environemnt, but I have no idea what.
> 
> I doubt it's HW related. You can try software timestamping (-S) to
> rule that out. In the ptp4l log there should be a message about the
> remote clock. If there is only the local clock, ptp4l is not getting
> the annoucement messages. That doesn't require any timestamping.
> 
> You can verify ptp4l is receiving messages from network with strace
> like this:
> 
> strace -erecvmsg ptp4l -m -q -i eth0 -s
> 

Thank you.

No joy on the software timestamping:

# ptp4l  -i lan2 -s -S -m
ptp4l[961566.609]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[961566.609]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[961572.642]: selected local clock e43d1a.fffe.acab65 as best master
ptp4l[961579.274]: selected local clock e43d1a.fffe.acab65 as best master
ptp4l[961587.069]: selected local clock e43d1a.fffe.acab65 as best master

And for the strace, on the working Intel I can see lots of this with the 
IP of our master:

recvmsg(14, {msg_name={sa_family=AF_INET, sin_port=htons(320), 
sin_addr=inet_addr("IP_REDACTED")}, msg_namelen=128->16, 
msg_iov=[{iov_base="\t\2\0006\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\354Fp\377\376\0\277\4\0\1\34\246"..., 
iov_len=1500}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 54

But on the Broadcom I don't see any such message from the same IP. So 
looks like ptp4l is not getting such annoucements as you suspected.

I've asked the networks team to check the switchport for Broadcom box is 
set up the same as Intel box, which they have confirmed it is. Meanwhile 
I've asked Meinberg for a bit of help/advice on the appliance config in 
case it's something at that end.

J