Re: [Linuxptp-devel] linuxptp on ubuntu 14.04

[Andrei P. <and...@kl...>]

I tried using two nodes, both using the same configuration file.
rand the same command on both machines   *sudo ptp4l -i eth1 -f
/etc/ptp4l.conf* and got the same behaviour as before; they both seem to be
hanging...
Am I missing something?

Thanks,
Andrei


On Tue, Jun 17, 2014 at 12:32 PM, Richard Cochran <ric...@gm...>
wrote:

> On Tue, Jun 17, 2014 at 12:26:27PM +0100, Andrei Perietanu wrote:
>
> > ethtool -T eth1
> > Time stamping parameters for eth1:
> > Capabilities:
> >     hardware-transmit     (SOF_TIMESTAMPING_TX_HARDWARE)
> >     software-transmit     (SOF_TIMESTAMPING_TX_SOFTWARE)
> >     hardware-receive      (SOF_TIMESTAMPING_RX_HARDWARE)
> >     software-receive      (SOF_TIMESTAMPING_RX_SOFTWARE)
> >     software-system-clock (SOF_TIMESTAMPING_SOFTWARE)
> >     hardware-raw-clock    (SOF_TIMESTAMPING_RAW_HARDWARE)
> > PTP Hardware Clock: 1
> > Hardware Transmit Timestamp Modes:
> >     off                   (HWTSTAMP_TX_OFF)
> >     on                    (HWTSTAMP_TX_ON)
> > Hardware Receive Filter Modes:
> >     none                  (HWTSTAMP_FILTER_NONE)
> >     all                   (HWTSTAMP_FILTER_ALL)
> >     ptpv1-l4-sync         (HWTSTAMP_FILTER_PTP_V1_L4_SYNC)
> >     ptpv1-l4-delay-req    (HWTSTAMP_FILTER_PTP_V1_L4_DELAY_REQ)
> >     ptpv2-l4-sync         (HWTSTAMP_FILTER_PTP_V2_L4_SYNC)
> >     ptpv2-l4-delay-req    (HWTSTAMP_FILTER_PTP_V2_L4_DELAY_REQ)
> >     ptpv2-l2-sync         (HWTSTAMP_FILTER_PTP_V2_L2_SYNC)
> >     ptpv2-l2-delay-req    (HWTSTAMP_FILTER_PTP_V2_L2_DELAY_REQ)
> >     ptpv2-event           (HWTSTAMP_FILTER_PTP_V2_EVENT)
> >     ptpv2-sync            (HWTSTAMP_FILTER_PTP_V2_SYNC)
> >     ptpv2-delay-req       (HWTSTAMP_FILTER_PTP_V2_DELAY_REQ)
>
> You have hardware time stamping...
>
> > I use this config file:
> > [global]
> > verbose               1
> > time_stamping         software
>                         ^^^^^^^^
>
> and so you should use it by saying "hardware" here. (Or just omit this
> line, since HW time stamping is the default.)
>
> > tx_timestamp_timeout  1000
> >
> > and when I run  *sudo ptp4l -i eth1 -f /etc/ptp4l.conf*   I get:
> > ptp4l[519792.941]: port 1: INITIALIZING to LISTENING on INITIALIZE
> > ptp4l[519792.941]: port 0: INITIALIZING to LISTENING on INITIALIZE
> > ptp4l[519799.549]: port 1: LISTENING to MASTER on
> > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
> > ptp4l[519799.549]: selected best master clock 002590.fffe.f2c1e4
> > ptp4l[519799.549]: assuming the grand master role
> >
> >
> > After this it seams to just...hang; there no other activity.  Any ideas?
>
> This is the expected behavior when there is only on PTP node on the
> network. Do you have another node to test with?
>
> If not, you can patch your igb/eth0 to the e1000e/eth1 and run two
> instances of ptp4l. Then you should see some more activity.
>
> HTH,
> 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.