Re: [Linuxptp-users] Support for latest igb driver?
PTP IEEE 1588 stack for Linux
Brought to you by:
rcochran
Menu
▾
▴
Re: [Linuxptp-users] Support for latest igb driver?
|
From: Rich S. <sch...@gm...> - 2016-12-22 16:33:56
|
ptp4l[4906520.702]: linreg: points 16 slope 0.999999311 intercept 7 err 28
ptp4l[4906520.702]: master offset 5 s2 freq +682 path delay 1640
ptp4l[4906521.702]: linreg: points 16 slope 0.999999311 intercept -0 err 28
ptp4l[4906521.702]: master offset 2 s2 freq +689 path delay 1640
ptp4l[4906522.702]: linreg: points 16 slope 0.999999313 intercept 12 err 28
ptp4l[4906522.702]: master offset -48 s2 freq +675 path delay 1640
ptp4l[4906523.702]: linreg: points 16 slope 0.999999312 intercept 0 err 28
ptp4l[4906523.702]: master offset -4 s2 freq +687 path delay 1640
ptp4l[4906524.016]: port 1: delay timeout
ptp4l[4906524.032]: delay filtered 1644 raw 1649
ptp4l[4906524.702]: linreg: points 16 slope 0.999999313 intercept -1 err 28
ptp4l[4906524.702]: master offset 24 s2 freq +688 path delay 1644
ptp4l[4906525.582]: port 1: delay timeout
ptp4l[4906525.592]: delay filtered 1644 raw 1676
ptp4l[4906525.702]: linreg: points 16 slope 0.999999313 intercept 2 err 28
ptp4l[4906525.702]: master offset -25 s2 freq +685 path delay 1644
ptp4l[4906526.702]: linreg: points 16 slope 0.999999315 intercept 18 err 29
ptp4l[4906526.702]: master offset -71 s2 freq +668 path delay 1644
ptp4l[4906527.702]: linreg: points 16 slope 0.999999315 intercept -0 err 28
ptp4l[4906527.702]: master offset 21 s2 freq +685 path delay 1644
ptp4l[4906528.702]: linreg: points 16 slope 0.999999316 intercept 3 err 28
ptp4l[4906528.702]: master offset 15 s2 freq +682 path delay 1644
ptp4l[4906529.702]: linreg: points 16 slope 0.999999316 intercept 3 err 28
ptp4l[4906529.703]: master offset -27 s2 freq +681 path delay 1644
ptp4l[4906530.703]: linreg: points 16 slope 0.999999316 intercept 0 err 28
ptp4l[4906530.703]: master offset 12 s2 freq +683 path delay 1644
ptp4l[4906531.703]: linreg: points 16 slope 0.999999316 intercept 1 err 28
ptp4l[4906531.703]: master offset -32 s2 freq +683 path delay 1644
ptp4l[4906531.867]: port 1: delay timeout
ptp4l[4906531.898]: delay filtered 1647 raw 1657
ptp4l[4906532.703]: linreg: points 16 slope 0.999999317 intercept 17 err 29
ptp4l[4906532.703]: master offset -78 s2 freq +666 path delay 1647
ptp4l[4906533.703]: linreg: points 16 slope 0.999999319 intercept 11 err 29
ptp4l[4906533.703]: master offset -24 s2 freq +670 path delay 1647
ptp4l[4906534.703]: linreg: points 16 slope 0.999999320 intercept 6 err 29
ptp4l[4906534.703]: master offset -14 s2 freq +674 path delay 1647
ptp4l[4906535.703]: linreg: points 16 slope 0.999999322 intercept 15 err 29
ptp4l[4906535.703]: master offset -48 s2 freq +663 path delay 1647
ptp4l[4906536.703]: linreg: points 16 slope 0.999999323 intercept 17 err 30
ptp4l[4906536.703]: master offset -72 s2 freq +660 path delay 1647
ptp4l[4906537.703]: linreg: points 16 slope 0.999999323 intercept -5 err 30
ptp4l[4906537.703]: master offset 28 s2 freq +682 path delay 1647
ptp4l[4906538.703]: linreg: points 16 slope 0.999999325 intercept 10 err 29
ptp4l[4906538.703]: master offset -14 s2 freq +666 path delay 1647
ptp4l[4906539.478]: port 1: delay timeout
ptp4l[4906539.503]: delay filtered 1650 raw 1667
ptp4l[4906539.703]: linreg: points 16 slope 0.999999325 intercept 3 err 29
ptp4l[4906539.703]: master offset -3 s2 freq +671 path delay 1650
ptp4l[4906540.701]: port 1: delay timeout
ptp4l[4906540.704]: linreg: points 16 slope 0.999999327 intercept 15 err 30
ptp4l[4906540.704]: master offset -75 s2 freq +658 path delay 1650
ptp4l[4906540.738]: delay filtered 1653 raw 15548
ptp4l[4906541.703]: linreg: points 16 slope 0.999999328 intercept 7 err 30
ptp4l[4906541.703]: master offset -17 s2 freq +666 path delay 1653
ptp4l[4906542.703]: linreg: points 16 slope 0.999999330 intercept 19 err 30
ptp4l[4906542.703]: master offset -43 s2 freq +651 path delay 1653
ptp4l[4906543.703]: linreg: points 16 slope 0.999999331 intercept 4 err 30
ptp4l[4906543.703]: master offset -14 s2 freq +666 path delay 1653
ptp4l[4906544.301]: port 1: delay timeout
ptp4l[4906545.303]: timed out while polling for tx timestamp
ptp4l[4906545.303]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[4906545.303]: port 1: send delay request failed
ptp4l[4906545.303]: port 1: SLAVE to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[4906545.303]: waiting 2^{4} seconds to clear fault on port 1
ptp4l[4906561.303]: clearing fault on port 1
ptp4l[4906561.303]: config item enp1s0f0.logMinDelayReqInterval is 2
ptp4l[4906561.303]: config item enp1s0f0.logAnnounceInterval is 0
ptp4l[4906561.303]: config item enp1s0f0.announceReceiptTimeout is 4
ptp4l[4906561.303]: config item enp1s0f0.syncReceiptTimeout is 0
ptp4l[4906561.303]: config item enp1s0f0.transportSpecific is 0
ptp4l[4906561.303]: config item enp1s0f0.logSyncInterval is 0
ptp4l[4906561.303]: config item enp1s0f0.logMinPdelayReqInterval is 2
ptp4l[4906561.303]: config item enp1s0f0.neighborPropDelayThresh is 20000000
ptp4l[4906561.303]: config item enp1s0f0.min_neighbor_prop_delay is -20000000
ptp4l[4906561.303]: config item enp1s0f0.udp_ttl is 1
ptp4l[4906561.305]: driver changed our HWTSTAMP options
ptp4l[4906561.305]: tx_type 1 not 1
ptp4l[4906561.305]: rx_filter 1 not 12
ptp4l[4906561.305]: config item (null).dscp_event is 0
ptp4l[4906561.305]: config item (null).dscp_general is 0
ptp4l[4906561.305]: port 1: FAULTY to LISTENING on FAULT_CLEARED
ptp4l[4906561.703]: port 1: setting asCapable
ptp4l[4906561.713]: port 1: new foreign master 0019dd.fffe.00085c-1
ptp4l[4906563.713]: selected best master clock 0019dd.fffe.00085c
ptp4l[4906563.713]: foreign master not using PTP timescale
ptp4l[4906563.713]: running in a temporal vortex
ptp4l[4906563.713]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[4906564.704]: linreg: points 8 slope 0.999999339 intercept 123 err 31
ptp4l[4906564.704]: master offset -120 s2 freq +538 path delay 1653
ptp4l[4906564.704]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[4906565.704]: linreg: points 8 slope 0.999999340 intercept 29 err 31
ptp4l[4906565.704]: master offset -59 s2 freq +631 path delay 1653
ptp4l[4906566.704]: linreg: points 8 slope 0.999999340 intercept 3 err 31
ptp4l[4906566.704]: master offset -10 s2 freq +656 path delay 1653
ptp4l[4906567.704]: linreg: points 8 slope 0.999999339 intercept -16 err 31
ptp4l[4906567.704]: master offset 53 s2 freq +676 path delay 1653
ptp4l[4906567.720]: port 1: delay timeout
ptp4l[4906568.721]: timed out while polling for tx timestamp
ptp4l[4906568.721]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[4906568.721]: port 1: send delay request failed
ptp4l[4906568.721]: port 1: SLAVE to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[4906568.721]: waiting 2^{4} seconds to clear fault on port 1
ptp4l[4906584.722]: clearing fault on port 1
ptp4l[4906584.722]: config item enp1s0f0.logMinDelayReqInterval is 2
ptp4l[4906584.722]: config item enp1s0f0.logAnnounceInterval is 0
ptp4l[4906584.722]: config item enp1s0f0.announceReceiptTimeout is 4
ptp4l[4906584.722]: config item enp1s0f0.syncReceiptTimeout is 0
ptp4l[4906584.722]: config item enp1s0f0.transportSpecific is 0
ptp4l[4906584.722]: config item enp1s0f0.logSyncInterval is 0
ptp4l[4906584.722]: config item enp1s0f0.logMinPdelayReqInterval is 2
ptp4l[4906584.722]: config item enp1s0f0.neighborPropDelayThresh is 20000000
ptp4l[4906584.722]: config item enp1s0f0.min_neighbor_prop_delay is -20000000
ptp4l[4906584.722]: config item enp1s0f0.udp_ttl is 1
ptp4l[4906584.722]: driver changed our HWTSTAMP options
ptp4l[4906584.722]: tx_type 1 not 1
ptp4l[4906584.722]: rx_filter 1 not 12
ptp4l[4906584.722]: config item (null).dscp_event is 0
ptp4l[4906584.722]: config item (null).dscp_general is 0
ptp4l[4906584.722]: port 1: FAULTY to LISTENING on FAULT_CLEARED
ptp4l[4906585.704]: port 1: setting asCapable
ptp4l[4906585.714]: port 1: new foreign master 0019dd.fffe.00085c-1
ptp4l[4906587.714]: selected best master clock 0019dd.fffe.00085c
ptp4l[4906587.714]: foreign master not using PTP timescale
ptp4l[4906587.714]: running in a temporal vortex
ptp4l[4906587.714]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[4906588.705]: linreg: points 8 slope 0.999999345 intercept 506 err 37
ptp4l[4906588.705]: master offset -645 s2 freq +149 path delay 1653
ptp4l[4906588.705]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[4906589.705]: linreg: points 8 slope 0.999999347 intercept 81 err 40
ptp4l[4906589.705]: master offset -194 s2 freq +572 path delay 1653
ptp4l[4906590.705]: linreg: points 8 slope 0.999999351 intercept 67 err 43
ptp4l[4906590.705]: master offset -166 s2 freq +582 path delay 1653
ptp4l[4906591.705]: linreg: points 8 slope 0.999999356 intercept 62 err 43
ptp4l[4906591.705]: master offset -68 s2 freq +582 path delay 1653
ptp4l[4906592.417]: port 1: delay timeout
ptp4l[4906593.418]: timed out while polling for tx timestamp
ptp4l[4906593.418]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[4906593.418]: port 1: send delay request failed
ptp4l[4906593.418]: port 1: SLAVE to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[4906593.418]: waiting 2^{4} seconds to clear fault on port 1
ptp4l[4906609.419]: clearing fault on port 1
ptp4l[4906609.419]: config item enp1s0f0.logMinDelayReqInterval is 2
ptp4l[4906609.419]: config item enp1s0f0.logAnnounceInterval is 0
ptp4l[4906609.419]: config item enp1s0f0.announceReceiptTimeout is 4
ptp4l[4906609.419]: config item enp1s0f0.syncReceiptTimeout is 0
ptp4l[4906609.419]: config item enp1s0f0.transportSpecific is 0
ptp4l[4906609.419]: config item enp1s0f0.logSyncInterval is 0
ptp4l[4906609.419]: config item enp1s0f0.logMinPdelayReqInterval is 2
ptp4l[4906609.419]: config item enp1s0f0.neighborPropDelayThresh is 20000000
ptp4l[4906609.419]: config item enp1s0f0.min_neighbor_prop_delay is -20000000
ptp4l[4906609.419]: config item enp1s0f0.udp_ttl is 1
ptp4l[4906609.419]: driver changed our HWTSTAMP options
ptp4l[4906609.419]: tx_type 1 not 1
ptp4l[4906609.419]: rx_filter 1 not 12
ptp4l[4906609.419]: config item (null).dscp_event is 0
ptp4l[4906609.419]: config item (null).dscp_general is 0
ptp4l[4906609.419]: port 1: FAULTY to LISTENING on FAULT_CLEARED
ptp4l[4906609.705]: port 1: setting asCapable
ptp4l[4906609.715]: port 1: new foreign master 0019dd.fffe.00085c-1
ptp4l[4906611.715]: selected best master clock 0019dd.fffe.00085c
ptp4l[4906611.715]: foreign master not using PTP timescale
ptp4l[4906611.715]: running in a temporal vortex
ptp4l[4906611.715]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[4906612.706]: linreg: points 8 slope 0.999999361 intercept -1042 err 49
ptp4l[4906612.706]: master offset 889 s2 freq +1680 path delay 1653
ptp4l[4906612.706]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[4906613.594]: port 1: delay timeout
ptp4l[4906614.596]: timed out while polling for tx timestamp
ptp4l[4906614.596]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug
ptp4l[4906614.596]: port 1: send delay request failed
ptp4l[4906614.596]: port 1: SLAVE to FAULTY on FAULT_DETECTED (FT_UNSPECIFIED)
ptp4l[4906614.596]: waiting 2^{4} seconds to clear fault on port 1
ptp4l[4906630.596]: clearing fault on port 1
ptp4l[4906630.596]: config item enp1s0f0.logMinDelayReqInterval is 2
ptp4l[4906630.596]: config item enp1s0f0.logAnnounceInterval is 0
ptp4l[4906630.596]: config item enp1s0f0.announceReceiptTimeout is 4
ptp4l[4906630.596]: config item enp1s0f0.syncReceiptTimeout is 0
ptp4l[4906630.596]: config item enp1s0f0.transportSpecific is 0
ptp4l[4906630.596]: config item enp1s0f0.logSyncInterval is 0
ptp4l[4906630.596]: config item enp1s0f0.logMinPdelayReqInterval is 2
ptp4l[4906630.596]: config item enp1s0f0.neighborPropDelayThresh is 20000000
ptp4l[4906630.596]: config item enp1s0f0.min_neighbor_prop_delay is -20000000
ptp4l[4906630.596]: config item enp1s0f0.udp_ttl is 1
ptp4l[4906630.597]: driver changed our HWTSTAMP options
ptp4l[4906630.597]: tx_type 1 not 1
ptp4l[4906630.597]: rx_filter 1 not 12
ptp4l[4906630.597]: config item (null).dscp_event is 0
ptp4l[4906630.597]: config item (null).dscp_general is 0
ptp4l[4906630.597]: port 1: FAULTY to LISTENING on FAULT_CLEARED
ptp4l[4906630.705]: port 1: setting asCapable
ptp4l[4906630.716]: port 1: new foreign master 0019dd.fffe.00085c-1
ptp4l[4906632.716]: selected best master clock 0019dd.fffe.00085c
ptp4l[4906632.716]: foreign master not using PTP timescale
ptp4l[4906632.716]: running in a temporal vortex
ptp4l[4906632.716]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE
ptp4l[4906633.707]: linreg: points 4 slope 0.999999378 intercept 21467 err 58
ptp4l[4906633.707]: master offset -21531 s2 freq -20845 path delay 1653
ptp4l[4906633.707]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[4906634.205]: port 1: delay timeout
ptp4l[4906635.206]: timed out while polling for tx timestamp
ptp4l[4906635.206]: increasing tx_timestamp_timeout may correct this issue, but it is likely caused by a driver bug |
