Dear All,

I'm working on a ptp4l solution on a custom board. We are performing
test creating faults (like missing messages, hw fault...), then you
should consider the faults in the following log as part of the test.

The issue that I'm facing is the following:
 - After a fault, the port lost the SLAVE role (correct) passing to
MASTER state (cortect)
 - After this transition, and after restoring the working condition I'm
unable to move from UNCALIBRATED state to SLAVE state.

My suspect is a wrong servo condition and my idea is to add a
servo_reset() into clock_update_slave() function.

Is it a good idea or a comlete non-sense?

Thanks a lot for your opinion and any suggestion,

Luigi




LOG:
ptp4l[1167.787]: selected /dev/ptp0 as PTP clock
ptp4l[1167.800]: port 5: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1167.802]: port 28: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1167.820]: port 109: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1167.821]: port 111: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1167.822]: port 209: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1167.844]: port 213: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1167.845]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[1167.846]: port 109: link down
ptp4l[1167.846]: port 109: LISTENING to FAULTY on FAULT_DETECTED
(FT_UNSPECIFIED)
ptp4l[1167.846]: port 111: link down
ptp4l[1167.846]: port 111: LISTENING to FAULTY on FAULT_DETECTED
(FT_UNSPECIFIED)
ptp4l[1167.847]: port 209: link down
ptp4l[1167.847]: port 209: LISTENING to FAULTY on FAULT_DETECTED
(FT_UNSPECIFIED)
ptp4l[1167.847]: selected local clock aabbcc.fffe.ddeeff as best master
ptp4l[1167.847]: port 109: assuming the grand master role
ptp4l[1167.847]: port 111: assuming the grand master role
ptp4l[1167.847]: port 209: assuming the grand master role
ptp4l[1167.858]: port 5: new foreign master 112233.fffe.445566-2
ptp4l[1167.927]: port 28: new foreign master 040506.fffe.070809-17
ptp4l[1168.108]: selected best master clock 112233.fffe.445566
ptp4l[1168.108]: running in a temporal vortex
ptp4l[1168.108]: updating UTC offset to 35
ptp4l[1168.108]: port 5: LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[1168.166]: pi_sample:79 sono qui
ptp4l[1168.177]: updating UTC offset to 35
ptp4l[1168.229]: pi_sample:102 sono qui
ptp4l[1168.232]: port 213: LISTENING to MASTER on
ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[1168.232]: updating UTC offset to 35
ptp4l[1168.239]: port 28: LISTENING to MASTER on
ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[1168.239]: updating UTC offset to 35
ptp4l[1168.291]: pi_sample:102 sono qui
ptp4l[1168.408]: port 5: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[1200.142]: rms   32 max   77 freq     +3 +/-  17 delay   181 +/-
14
ptp4l[1232.116]: rms   30 max   74 freq     +0 +/-   0 delay   182 +/-
14
ptp4l[1235.147]: port 111: link up
ptp4l[1235.147]: port 111: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1235.148]: port 109: link up
ptp4l[1235.148]: port 109: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1235.584]: port 111: LISTENING to MASTER on
ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[1235.584]: updating UTC offset to 35
ptp4l[1235.600]: port 109: LISTENING to MASTER on
ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[1235.601]: updating UTC offset to 35
ptp4l[1236.648]: timed out while polling for tx timestamp
ptp4l[1236.648]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1236.648]: port 111: Echo frame too short
ptp4l[1237.649]: timed out while polling for tx timestamp
ptp4l[1237.649]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1237.649]: port 111: Echo frame too short
ptp4l[1238.649]: timed out while polling for tx timestamp
ptp4l[1238.649]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1238.650]: port 111: Echo frame too short
ptp4l[1239.651]: timed out while polling for tx timestamp
ptp4l[1239.651]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1239.651]: port 111: Echo frame too short
ptp4l[1240.652]: timed out while polling for tx timestamp
ptp4l[1240.652]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1240.652]: port 111: Echo frame too short
ptp4l[1241.653]: timed out while polling for tx timestamp
ptp4l[1241.653]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1241.653]: port 111: Echo frame too short
ptp4l[1242.654]: timed out while polling for tx timestamp
ptp4l[1242.654]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1242.654]: port 111: Echo frame too short
ptp4l[1243.655]: timed out while polling for tx timestamp
ptp4l[1243.655]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1243.655]: port 111: Echo frame too short
ptp4l[1244.656]: timed out while polling for tx timestamp
ptp4l[1244.656]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1244.656]: port 111: Echo frame too short
ptp4l[1245.657]: timed out while polling for tx timestamp
ptp4l[1245.657]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1245.657]: port 111: Echo frame too short
ptp4l[1246.658]: timed out while polling for tx timestamp
ptp4l[1246.659]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1246.659]: port 111: Echo frame too short
ptp4l[1246.659]: port 111: send sync failed
ptp4l[1246.659]: port 111: MASTER to FAULTY on FAULT_DETECTED
(FT_UNSPECIFIED)
ptp4l[1246.660]: port 5: SLAVE to MASTER on
ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[1247.662]: timed out while polling for tx timestamp
ptp4l[1247.662]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1247.662]: port 109: Echo frame too short
ptp4l[1248.663]: timed out while polling for tx timestamp
ptp4l[1248.663]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1248.663]: port 109: Echo frame too short
ptp4l[1249.664]: timed out while polling for tx timestamp
ptp4l[1249.664]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1249.664]: port 109: Echo frame too short
ptp4l[1250.664]: timed out while polling for tx timestamp
ptp4l[1250.664]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1250.664]: port 109: Echo frame too short
ptp4l[1251.665]: timed out while polling for tx timestamp
ptp4l[1251.665]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1251.665]: port 109: Echo frame too short
ptp4l[1252.665]: timed out while polling for tx timestamp
ptp4l[1252.665]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1252.665]: port 109: Echo frame too short
ptp4l[1253.666]: timed out while polling for tx timestamp
ptp4l[1253.666]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1253.666]: port 109: Echo frame too short
ptp4l[1254.667]: timed out while polling for tx timestamp
ptp4l[1254.667]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1254.667]: port 109: Echo frame too short
ptp4l[1255.668]: timed out while polling for tx timestamp
ptp4l[1255.668]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1255.668]: port 109: Echo frame too short
ptp4l[1256.669]: timed out while polling for tx timestamp
ptp4l[1256.669]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1256.669]: port 109: Echo frame too short
ptp4l[1257.670]: timed out while polling for tx timestamp
ptp4l[1257.670]: increasing tx_timestamp_timeout may correct this
issue, but it is likely caused by a driver bug
ptp4l[1257.670]: port 109: Echo frame too short
ptp4l[1257.671]: port 109: send sync failed
ptp4l[1257.671]: port 109: MASTER to FAULTY on FAULT_DETECTED
(FT_UNSPECIFIED)
ptp4l[1257.672]: selected local clock aabbcc.fffe.ddeeff as best master
ptp4l[1257.672]: port 5: assuming the grand master role
ptp4l[1257.672]: port 28: assuming the grand master role
ptp4l[1257.672]: port 109: assuming the grand master role
ptp4l[1257.672]: port 111: assuming the grand master role
ptp4l[1257.672]: port 209: assuming the grand master role
ptp4l[1257.672]: port 213: assuming the grand master role
ptp4l[1257.675]: port 5: assuming the grand master role
ptp4l[1257.675]: port 28: assuming the grand master role
ptp4l[1257.675]: port 109: assuming the grand master role
ptp4l[1257.675]: port 111: assuming the grand master role
ptp4l[1257.675]: port 209: assuming the grand master role
ptp4l[1257.675]: port 213: assuming the grand master role
ptp4l[1257.677]: selected best master clock 112233.fffe.445566
ptp4l[1257.677]: updating UTC offset to 35
ptp4l[1257.677]: port 5: MASTER to UNCALIBRATED on RS_SLAVE
ptp4l[1286.211]: rms   45 max  250 freq     +0 +/-   0 delay   181 +/-
13
ptp4l[1300.147]: port 111: link down
ptp4l[1300.147]: updating UTC offset to 35
ptp4l[1300.148]: port 109: link down
ptp4l[1300.149]: updating UTC offset to 35
ptp4l[1318.172]: rms   23 max   67 freq     +0 +/-   0 delay   181 +/-
14
ptp4l[1350.214]: rms   21 max   62 freq     +0 +/-   0 delay   181 +/-
13
ptp4l[1370.149]: port 109: link up
ptp4l[1370.150]: port 109: FAULTY to LISTENING on INIT_COMPLETE
ptp4l[1370.273]: port 109: new foreign master 010302.fffe.040506-204
ptp4l[1370.523]: updating UTC offset to 35
ptp4l[1370.523]: port 109: LISTENING to PRE_MASTER on RS_MASTER
ptp4l[1370.773]: port 109: PRE_MASTER to MASTER on
QUALIFICATION_TIMEOUT_EXPIRES
ptp4l[1382.175]: rms   20 max   59 freq     +0 +/-   0 delay   182 +/-
14
ptp4l[1414.187]: rms   21 max   62 freq     +0 +/-   0 delay   174 +/-
14
ptp4l[1436.009]: port 5: new foreign master f8f9fa.fffe.f0f1f2-117
ptp4l[1446.222]: rms   20 max   61 freq     +0 +/-   0 delay   170 +/-
13
ptp4l[1478.173]: rms   19 max   60 freq     +0 +/-   0 delay   173 +/-
14
ptp4l[1510.173]: rms   19 max   56 freq     +0 +/-   0 delay   172 +/-
14
ptp4l[1542.173]: rms   18 max   54 freq     +0 +/-   0 delay   175 +/-
15
ptp4l[1574.177]: rms   16 max   56 freq     +0 +/-   0 delay   172 +/-
13
ptp4l[1606.236]: rms   15 max   52 freq     +0 +/-   0 delay   173 +/-
13
ptp4l[1638.174]: rms   15 max   54 freq     +0 +/-   0 delay   174 +/-
14

Attachment: signature.asc
Description: This is a digitally signed message part

_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel

Reply via email to