Hardik Gohil
2017-03-24 02:44:20 UTC
Hello,
I am working on Linux 3.12 running on TI AM335x.
The Test system is GPS connected to CPU over Ethernet and GPS is configured
to PEER to PEER mode.
I can successfully test using E2E mode there were no issues.
***@phycore-am335x-1:~# ptp4l -i eth0 -m -P -s
ptp4l[2103.623]: selected /dev/ptp0 as PTP clock
ptp4l[2103.653]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[2103.657]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[2103.724]: port 1: new foreign master 001d7f.fffe.8002f7-1
ptp4l[2103.849]: port 1: received PDELAY_REQ without timestamp
ptp4l[2104.658]: timed out while polling for tx timestamp
ptp4l[2104.659]: increasing tx_timestamp_timeout may correct this issue,
but it is likely caused by a driver bug
ptp4l[2104.659]: port 1: send peer delay request failed
ptp4l[2104.659]: port 1: LISTENING to FAULTY on FAULT_DETECTED
(FT_UNSPECIFIED)
ptp4l[2120.707]: port 1: FAULTY to LISTENING on FAULT_CLEARED
ptp4l[2120.865]: port 1: received PDELAY_REQ without timestamp
ptp4l[2121.714]: timed out while polling for tx timestamp
ptp4l[2121.715]: increasing tx_timestamp_timeout may correct this issue,
but it is likely caused by a driver bug
ptp4l[2121.715]: port 1: send peer delay request failed
ptp4l[2121.715]: port 1: LISTENING to FAULTY on FAULT_DETECTED
(FT_UNSPECIFIED)
Regards,
Hardik A Gohil
I am working on Linux 3.12 running on TI AM335x.
The Test system is GPS connected to CPU over Ethernet and GPS is configured
to PEER to PEER mode.
I can successfully test using E2E mode there were no issues.
***@phycore-am335x-1:~# ptp4l -i eth0 -m -P -s
ptp4l[2103.623]: selected /dev/ptp0 as PTP clock
ptp4l[2103.653]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[2103.657]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[2103.724]: port 1: new foreign master 001d7f.fffe.8002f7-1
ptp4l[2103.849]: port 1: received PDELAY_REQ without timestamp
ptp4l[2104.658]: timed out while polling for tx timestamp
ptp4l[2104.659]: increasing tx_timestamp_timeout may correct this issue,
but it is likely caused by a driver bug
ptp4l[2104.659]: port 1: send peer delay request failed
ptp4l[2104.659]: port 1: LISTENING to FAULTY on FAULT_DETECTED
(FT_UNSPECIFIED)
ptp4l[2120.707]: port 1: FAULTY to LISTENING on FAULT_CLEARED
ptp4l[2120.865]: port 1: received PDELAY_REQ without timestamp
ptp4l[2121.714]: timed out while polling for tx timestamp
ptp4l[2121.715]: increasing tx_timestamp_timeout may correct this issue,
but it is likely caused by a driver bug
ptp4l[2121.715]: port 1: send peer delay request failed
ptp4l[2121.715]: port 1: LISTENING to FAULTY on FAULT_DETECTED
(FT_UNSPECIFIED)
Regards,
Hardik A Gohil