[Linuxptp-users] ptp4l/phc2sys: Linux 'date' incorrect
PTP IEEE 1588 stack for Linux
Brought to you by:
rcochran
Menu
▾
▴
[Linuxptp-users] ptp4l/phc2sys: Linux 'date' incorrect
|
From: Harold L. <hla...@pi...> - 2015-09-15 16:32:24
|
To Whom It May Concern,
Have ptp4l/phc2sys running on 3 separate systems, start system 1 and then system 2 and the output looks good ( using -m attribute) but when system 3 is started a 'GRAND_MASTER' to Faulty occurs. System 3 is immediately removed but system 2 is showing a huge master offset and it starts to slowly come down but takes 20 - 30 minutes. Have stopped and restarted system 2 but it continues with a huge master offset that continues to move downward. How does one get a system to recover quickly from this type of issue (i.e., 20 - 30 minutes is unreasonable and powering the unit ON/OFF isn't an option)?
Thanks,
Harold
system 1:
ptp4l:
root@zx3-pm3-zynq7:~# ptp4l -i eth0 -m
ptp4l[134.005]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[134.006]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[134.878]: port 1: new foreign master 00214a.fffe.000007-1
ptp4l[138.752]: selected best master clock 00214a.fffe.000007
ptp4l[138.753]: assuming the grand master role
ptp4l[138.753]: port 1: LISTENING to GRAND_MASTER on RS_GRAND_MASTER
phc2sys:
root@zx3-pm3-zynq7:~# phc2sys -a -r -r -m
hc2sys[216.598]: sys offset 46 s2 freq -1 delay 9936
phc2sys[217.599]: sys offset 69 s2 freq +36 delay 9891
phc2sys[218.599]: sys offset 9 s2 freq -3 delay 9908
phc2sys[219.600]: sys offset -72 s2 freq -82 delay 9918
phc2sys[220.600]: sys offset -41 s2 freq -72 delay 9837
system2:
ptp4l:
root@zx3-pm3-zynq7:~# ptp4l -i eth0 -m
ptp4l[10299.159]: master offset 13496 s2 freq -92511 path delay 30399
ptp4l[10300.259]: master offset 6068 s2 freq -95890 path delay 30399
ptp4l[10301.359]: master offset 2295 s2 freq -97843 path delay 30399
ptp4l[10302.459]: master offset -787 s2 freq -100236 path delay 30399
ptp4l[10303.559]: master offset 576 s2 freq -99110 path delay 29807
ptp4l[10304.659]: master offset 3480 s2 freq -96033 path delay 27695
ptp4l[10305.759]: master offset 1531 s2 freq -96938 path delay 27059
ptp4l[10306.859]: master offset 46 s2 freq -97963 path delay 27059
system 3: brought up:
ptp4l[10826.010]: selected best master clock 000a35.fffe.00da5e
ptp4l[10826.010]: port 1: SLAVE to UNCALIBRATED on RS_SLAVE
ptp4l[10828.010]: master offset 318377681381 s2 freq +32767999 path delay 9823
ptp4l[10828.010]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[10829.002]: master offset 318344852456 s2 freq +32767999 path delay 9823
ptp4l[10829.975]: master offset 318309408666 s2 freq +32767999 path delay 2590734
ptp4l[10830.935]: master offset 318276417859 s2 freq +32767999 path delay 2706681
system 3 removed:
.
.
.
ptp4l[10826.010]: selected best master clock 000a35.fffe.00da5e
ptp4l[10826.010]: port 1: SLAVE to UNCALIBRATED on RS_SLAVE
ptp4l[10828.010]: master offset 318377681381 s2 freq +32767999 path delay 9823
ptp4l[10828.010]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[10829.002]: master offset 318344852456 s2 freq +32767999 path delay 9823
ptp4l[10829.975]: master offset 318309408666 s2 freq +32767999 path delay 2590734
ptp4l[10830.935]: master offset 318276417859 s2 freq +32767999 path delay 2706681
.
. (20 - 30 minutes)
.
ptp4l[11563.398]: master offset 26 s2 freq -108134 path delay 2554197
ptp4l[11564.300]: master offset 1272234 s2 freq +1164082 path delay 1290161
ptp4l[11565.197]: master offset 844850 s2 freq +1118368 path delay 458005
ptp4l[11566.098]: master offset -373946 s2 freq +153027 path delay 458005
ptp4l[11566.998]: master offset -426947 s2 freq -12157 path delay 257305
ptp4l[11567.898]: master offset -513853 s2 freq -227148 path delay 257305
ptp4l[11568.798]: master offset -170513 s2 freq -37963 path delay 41365
ptp4l[11569.698]: master offset -231087 s2 freq -149691 path delay 41365
ptp4l[11570.598]: master offset -161630 s2 freq -149560 path delay 23074
ptp4l[11571.498]: master offset -111912 s2 freq -148331 path delay 23074
ptp4l[11572.398]: master offset -62601 s2 freq -132594 path delay 23074
ptp4l[11573.298]: master offset -31339 s2 freq -120112 path delay 25772
ptp4l[11574.198]: master offset -10658 s2 freq -108833 path delay 25949
ptp4l[11575.098]: master offset -312 s2 freq -101684 path delay 25949
ptp4l[11575.998]: master offset 2400 s2 freq -99066 path delay 25949
ptp4l[11576.898]: master offset 3233 s2 freq -97513 path delay 25949
ptp4l[11577.798]: master offset 2215 s2 freq -97561 path delay 26035
ptp4l[11578.698]: master offset 1507 s2 freq -97605 path delay 26035
ptp4l[11579.598]: master offset 1025 s2 freq -97635 path delay 26546
ptp4l[11580.498]: master offset -221 s2 freq -98573 path delay 26813
ptp4l[11581.398]: master offset 730 s2 freq -97688 path delay 26813
ptp4l[11582.298]: master offset 119 s2 freq -98080 path delay 26813
phc2sys:
root@zx3-pm3-zynq7:~# phc2sys -a -r -r -m
phc2sys[10432.994]: phc offset 474 s2 freq -99007 delay 2727
phc2sys[10433.994]: phc offset 638 s2 freq -98701 delay 2677
phc2sys[10434.995]: phc offset -302 s2 freq -99450 delay 2682
phc2sys[10435.995]: phc offset 108 s2 freq -99130 delay 2682
phc2sys[10436.996]: phc offset 325 s2 freq -98881 delay 2679
phc2sys[10437.996]: phc offset -264 s2 freq -99372 delay 2682
phc2sys[10438.997]: phc offset -483 s2 freq -99670 delay 2682
phc2sys[10439.997]: phc offset 506 s2 freq -98826 delay 2706
phc2sys[10440.998]: phc offset -796 s2 freq -99977 delay 2686
system 3 brought up:
phc2sys[11555.873]: phc offset -4 s2 freq +32768017 delay 2591
phc2sys[11556.873]: phc offset 7 s2 freq +32768027 delay 2614
phc2sys[11557.874]: phc offset -6 s2 freq +32768016 delay 2589
phc2sys[11558.874]: phc offset -8 s2 freq +32768012 delay 2605
phc2sys[11559.875]: port 00214a.fffe.000007-1 changed state
phc2sys[11559.876]: reconfiguring after port state change
phc2sys[11559.876]: master clock not ready, waiting...
phc2sys[11562.877]: port 00214a.fffe.000007-1 changed state
phc2sys[11562.878]: reconfiguring after port state change
phc2sys[11562.878]: selecting CLOCK_REALTIME for synchronization
phc2sys[11562.878]: selecting eth0 as the master clock
phc2sys[11562.878]: phc offset 293403920992 s2 freq +100000000 delay 2641
phc2sys[11563.879]: phc offset 293292168858 s2 freq +100000000 delay 2410
phc2sys[11564.879]: phc offset 293181588380 s2 freq +100000000 delay 2416
.
. (20 - 30 minutes)
.
phc2sys[10848.490]: phc offset 262 s2 freq +32767701 delay 2640
phc2sys[10849.494]: phc offset 596 s2 freq +32768114 delay 2594
phc2sys[10850.495]: phc offset 507 s2 freq +32768204 delay 2591
phc2sys[10851.496]: phc offset 300 s2 freq +32768149 delay 2704
phc2sys[10852.496]: phc offset 186 s2 freq +32768125 delay 2597
phc2sys[10853.497]: phc offset 79 s2 freq +32768074 delay 2594
phc2sys[10854.497]: phc offset 14 s2 freq +32768032 delay 2638
phc2sys[10855.498]: phc offset 18 s2 freq +32768040 delay 2591
phc2sys[10856.499]: phc offset -1 s2 freq +32768027 delay 2594
system 3:
ptpl4:
root@zx3-pm3-zynq7:~# ptp4l -i eth0 -m
ptp4l[9570.777]: selected /dev/ptp0 as PTP clock
ptp4l[9570.781]: driver changed our HWTSTAMP options
ptp4l[9570.782]: tx_type 1 not 1
ptp4l[9570.782]: rx_filter 1 not 12
ptp4l[9570.783]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[9570.784]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[9572.743]: port 1: new foreign master 000a35.fffe.01225c-1
ptp4l[9576.743]: selected best master clock 000a35.fffe.01225c
ptp4l[9576.744]: assuming the grand master role
ptp4l[9576.744]: port 1: LISTENING to GRAND_MASTER on RS_GRAND_MASTER
ptp4l[9593.749]: timed out while polling for tx timestamp
ptp4l[9593.749]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[9593.749]: port 1: send sync failed
ptp4l[9593.749]: port 1: GRAND_MASTER to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[9609.753]: driver changed our HWTSTAMP options
ptp4l[9609.754]: tx_type 1 not 1
ptp4l[9609.755]: rx_filter 1 not 12
ptp4l[9609.755]: port 1: FAULTY to LISTENING on FAULT_CLEARED
ptp4l[9611.049]: port 1: new foreign master 000a35.fffe.01225c-1
|
