On Thu, 2014-06-19 at 09:23 +0100, Andrei Perietanu wrote:
> > 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)
> 
> >That is strange. You must be sure to turn off NTP first, if you want
> >to use phc2sys (or ptp4l with SW time stamping). Otherwise, the two
> >programs will fight each other.
> 
> I don't think I have ntp running:
> 
> sudo /etc/init.d/ntp stop
> sudo: /etc/init.d/ntp: command not found
> 

sudo /etc/init.d/ntpd stop
sudo /etc/init.d/ntpdate stop

> sudo service ntp stop
> ntp: unrecognized service
> 
> 
> that's what I found online about stopping ntp at least; is there some
> other command I'm supposed to run?
> 
> > 2. why did my system clock decide to change tu such an awkward
>  value?
> 
> >Are you perhaps still using SW time stamping? That would explain it.
> 

It certainly appears like you are using software timestamps.

> 
> I'm actually using HW timestamping and can't find anything on the
> internet about this problem...
> 
> 
> Thanks,
> Andrei
> 
>  
> 

Thanks,
Jake

> 
> 
> On Wed, Jun 18, 2014 at 5:10 PM, Richard Cochran
> <richardcoch...@gmail.com> wrote:
>         On Wed, Jun 18, 2014 at 04:49:38PM +0100, Andrei Perietanu
>         wrote:
>         > 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.
>         
>         
>         That is really very suspicious. I think this must be a red
>         herring,
>         and something *else* changed.
>         
>         > 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
>         
>         
>         Normal for a master node.
>         
>         > 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[459976.701]: master offset        145 s2 freq  +16538
>         path delay 16238
>         
>         
>         This is also working.
>         
>         > 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)
>         
>         
>         That is strange. You must be sure to turn off NTP first, if
>         you want
>         to use phc2sys (or ptp4l with SW time stamping). Otherwise,
>         the two
>         programs will fight each other.
>         
>         > 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
>         
>         
>         Yes, looks like it.
>         
>         > 2. why did my system clock decide to change tu such an
>         awkward  value?
>         
>         
>         Are you perhaps still using SW time stamping? That would
>         explain it.
>         
>         Thanks,
>         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

Reply via email to