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

[Richard C. <ric...@gm...>]

On Mon, Mar 12, 2012 at 07:37:51PM +0900, Takahiro Shimizu wrote:
> Hello,
> 
> I am using ptp4l with hardware clock.
> The ieee1588 hardware is Intel EG20T.
> The sync is fine.
> However ptp4l stop sometimes when we copy many data like following.
> 
> I connect 2 CrownBay(Intel E6xx CPU + Intel PCH EG20T) boards and 1 PC in
> the same network.
> I installed Linux kernel 3.3-rc6 on 2 CrownBays.
> I installed Windows 7 on PC.
> CrownBay-1 is a PTP master.
> CrownBay-2 is a PTP slave.
> Samba server is running on the CrownBay-2.
> The ptp4l is running on the both CrownBay.
> I mount the directory of CrownBay-2 on PC.
> I copied many files between PC and CrwonBay-2 when I am running ptp4l.

So you generate a lot of non-PTP traffic. In theory, this should not
affect the operation of the PHC hardware, PHC driver, or PTP stack.

> 
> The ptp4l log is as follows:
> 
> :
> ptp4l[4305]: master offset       -502 s2 adj  -10566 path delay       3062
> ptp4l[4305]: received SYNC without timestamp
> ptp4l[4305]: port 1: bad message
> ptp4l[4305]: received SYNC without timestamp
> ptp4l[4305]: port 1: bad message

Here you have a problem. Your hardware (or driver) is dropping time
stamps. You need to fix this.

> 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 put debug message to see what is happened after
> ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES.
> 
> :
> ptp4l[4305]: port 1: SLAVE to LISTENING on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
> ptp4l[4305]: port_set_announce_tmo
> ptp4l[4305]: port_set_announce_tmo
> 
> 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.

> 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?

HTH,
Richard