Re: [Linuxptp-users] ptp4l stop with ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES message.

[Takahiro S. <tsh...@gm...>]

Hello,

> ptp4l[4305]: port 1: bad message
>
> Here you have a problem. Your hardware (or driver) is dropping time
> stamps. You need to fix this.
>
>
I understand. EG20T GbE hardware drop the packet automatically if the
RxFIFO is overflowed.
So this is happened in high load condition.


> > ptp4l[4305]: port 1: SLAVE to LISTENING on
> ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
>
> This means that no announce message from the master clock arrived
> within the expected time.
>
>
I see.


> > port_set_announce_tmo is called infintely.
>
> This is normal. This should only happen once every
>
>   announceReceiptTimeout * 2^logAnnounceInterval
>
> seconds.
>
> For some reason, the ptp4l program is not receiving any more announce
> messages.
>
>
OK. I think the same.


> > This continues after stopping data copy.
> >
> > However, if I start Wireshark to see the packet exchange, ptp4l re-start
> > the sync.
>
> Wireshark places the MAC into promiscuous mode. Maybe your MAC is
> dropping UDP multicasts?
>
>
Yes, EG20T MAC drops UDP multicast in the situation. I think linuxptp seems
starting with promiscuous mode and leaves the promiscuous mode in the
situation.
However I can not see the any code about promiscuous mode in the linuxptp
source code.

I want that linuxptp re-start automatically getting new announce message
after ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES.

Thanks,
Takahiro Shimizu