I tried the easy option *run ptp4l with the '-2' (L2 transport) flag* but
that changed nothing... so I tried something different: I changed
tx_timestamp_timeout from 1000 to 100 and now I get some output on the
slave node.
The output of the master node:
ptp4l[622024.340]: selected /dev/ptp1 as PTP clock
ptp4l[622024.340]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[622024.340]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[622026.448]: port 1: new foreign master 00e04b.fffe.3b5762-1
ptp4l[622030.527]: selected best master clock 00e04b.fffe.3b5762
ptp4l[622030.527]: assuming the grand master role
ptp4l[622030.527]: port 1: LISTENING to GRAND_MASTER on RS_GRAND_MASTER
and that's it..stops at that
The output of the slave node:
ptp4l[459942.424]: selected /dev/ptp0 as PTP clock
ptp4l[459942.425]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[459942.425]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[459949.497]: port 1: LISTENING to MASTER on
ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
ptp4l[459949.497]: selected best master clock 00e04b.fffe.3b5762
ptp4l[459949.497]: assuming the grand master role
ptp4l[459953.600]: port 1: new foreign master 002590.fffe.f2c1e4-1
ptp4l[459957.700]: selected best master clock 002590.fffe.f2c1e4
ptp4l[459957.700]: port 1: MASTER to UNCALIBRATED on RS_SLAVE
ptp4l[459959.700]: master offset 70392990950326 s0 freq +42196 path
delay 11935
ptp4l[459960.700]: master offset 70392990967298 s1 freq +59166 path
delay 11388
ptp4l[459961.700]: master offset -38681 s2 freq +20485 path delay
11388
ptp4l[459961.700]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED
ptp4l[459962.700]: master offset -46656 s2 freq +905 path delay
11388
ptp4l[459963.700]: master offset -33290 s2 freq +275 path delay
11627
ptp4l[459964.700]: master offset -16728 s2 freq +6850 path delay
11234
ptp4l[459965.700]: master offset -6979 s2 freq +11580 path delay
11781
ptp4l[459966.700]: master offset -2157 s2 freq +14308 path delay
12304
ptp4l[459967.775]: master offset -297 s2 freq +15521 path delay
12947
ptp4l[459968.700]: master offset -27 s2 freq +15702 path delay
13803
ptp4l[459969.700]: master offset -16 s2 freq +15705 path delay
14554
ptp4l[459970.701]: master offset -359 s2 freq +15357 path delay
15659
ptp4l[459971.701]: master offset 706 s2 freq +16315 path delay
15659
ptp4l[459972.701]: master offset 622 s2 freq +16442 path delay
16007
ptp4l[459973.701]: master offset 614 s2 freq +16621 path delay
16076
ptp4l[459974.701]: master offset 390 s2 freq +16581 path delay
16186
ptp4l[459975.787]: master offset 281 s2 freq +16589 path delay
16186
ptp4l[459976.701]: master offset 145 s2 freq +16538 path delay
16238
now, when this happened, I noticed my system clock went rogue - for some
reason it thinks it's July 11th 12:00 am (it's configured toget time
automatically from the internet)
So, two questions come to mind:
1. is ptp working correcly now? O sould I see some messages on the master's
console as well
2. why did my system clock decide to change tu such an awkward value?
Also I tried running *sudo phc2sys -s eth1 -w -q* but this does not seem to
work; it's like phc2sys is waiting for ptp4l, even though ptp4l is already
running. any ideas on this one?
Thanks,
Andrei
On Wed, Jun 18, 2014 at 3:33 PM, Richard Cochran <richardcoch...@gmail.com>
wrote:
> On Wed, Jun 18, 2014 at 01:13:27PM +0100, Andrei Perietanu wrote:
> > I tried running wireshark on both nodes and I see the exact same
> wireshark
> > output on both of them, so sync messages are being received by the slave.
>
> Okay, then something very strange is happening, and I can't imagine
> what is going on. The one difference between wireshark and ptp4l is
> that wireshark uses promiscuous mode, while ptp4l joins the multicast
> group.
>
> Here are two things to try.
>
> 1. Easy: run ptp4l with the '-2' (L2 transport) flag
> 2. Harder: try a vanilla kernel
>
> Sorry,
> Richard
>
--
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of or
taking of any action in reliance upon this information by persons or
entities other than the intended recipient is prohibited. If you receive
this in error please contact the sender and delete the material from any
computer immediately. It is the policy of Klas Limited to disavow the
sending of offensive material and should you consider that the material
contained in the message is offensive you should contact the sender
immediately and also your I.T. Manager.
Klas Telecom Inc., a Virginia Corporation with offices at 1101 30th St. NW,
Washington, DC 20007.
Klas Limited (Company Number 163303) trading as Klas Telecom, an Irish
Limited Liability Company, with its registered office at Fourth Floor, One
Kilmainham Square, Inchicore Road, Kilmainham, Dublin 8, Ireland.
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
