Re: [Linuxptp-users] asCapable and FD_MANNO_TIMER questions

[Drasko D. <dra...@gm...>]

On Fri, May 31, 2013 at 4:09 PM, Richard Cochran
<ric...@gm...> wrote:
> On Fri, May 31, 2013 at 02:31:27PM +0200, Drasko DRASKOVIC wrote:
>
>> 1) What is does exactly  exectly asCapable flasg represent?
>
> This is explained in 802.1AS.

Yes, found it. Based on what I can read here, this log is a good sign.

>> 2) I can see that tx announce timeouts because of FD_MANNO_TIMER event
>> in FSM. Any ideas why this is happening and where to look?
>
> This is the master's announce timer. It means that it is time to
> transmit an announce message.

Great, then this is also a good sign. From what I can see in the code,
port_tx_announce() is called.

>From log presented in previous mail I can now conclude that master
keeps broadcasting "announce" and "sync" messages.

Can somebody please confirm that this is normal behavior, and that
these log actually does not represent any error (abnormal state) on
master side?


On the slave side, I have an evident error :

root@slave:~/linuxptp# ./ptp4l -S -i wlan0 -m -l9 -s
ptp4l[7264.414]: port 1: get_ts_info not supported
ptp4l[7264.424]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[7264.425]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[7264.772]: port 1: setting asCapable
ptp4l[7264.773]: port 1: new foreign master deadbe.fffe.ef0000-1
ptp4l[7270.424]: port 1: announce timeout
ptp4l[7270.711]: selected best master clock deadbe.fffe.ef0000
ptp4l[7270.711]: foreign master not using PTP timescale
ptp4l[7270.711]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[7271.892]: port 1: delay timeout
ptp4l[7271.894]: poll tx timestamp failed: Success
ptp4l[7271.894]: port 1: send delay request failed
ptp4l[7271.894]: port 1: UNCALIBRATED to FAULTY on FAULT_DETECTED
(FT_UNSPECIFIED)
ptp4l[7271.896]: waiting 2^{4} seconds to clear fault on port 0

Is there any hints how this delay failure should be examined ? Looking
at this code in port_delay_request() :
cnt = transport_send(p->trp, &p->fda, 1, msg, pdulen, &msg->hwts);
	if (cnt <= 0) {
		pr_err("port %hu: send delay request failed", portnum(p));
		goto out;
	}
it does not give too much information why sending this message fails.

Secondly, I am seeing again "poll tx timestamp failed: Success",
although I have added skb_tx_timestamp(skb); to the wireless driver.
This seemd to work well on master side, so master stopped complain. I
am not sure why on the slave side I am facing the same error, while
using the same driver with tx_timestamp added.

Best regards,
Drasko