linuxptp-users — Open discussion on using the linuxptp software.

Re: [Linuxptp-users] time stamping

[Milutin A. <mil...@ho...>]

Hello,
Maybe I didn't understand but I was thinking that I can get traffic
of network packets (packets that go out of network card like wireshark does) with exact times when they were sent not the time on the host but the times on
the network card. And I was thinking I could do it with your ptp4l program.
So I need the exact time (timestamping on the card with accuracy of 1 microsecond) and length of packets on the link. If I can't do it with your program's packet can you tell me with which program I can do it.
Thank you in advance,
Milutin Aksic.

> From: jac...@in...
> To: ric...@gm...; mil...@ho...
> CC: lin...@li...
> Subject: RE: [Linuxptp-users] time stamping
> Date: Fri, 19 Jul 2013 20:50:58 +0000
> 
> 
> > -----Original Message-----
> > From: Richard Cochran [mailto:ric...@gm...]
> > Sent: Friday, July 19, 2013 10:24 AM
> > To: Milutin Aksic
> > Cc: lin...@li...
> > Subject: Re: [Linuxptp-users] time stamping
> > 
> > On Fri, Jul 19, 2013 at 04:29:07PM +0100, Milutin Aksic wrote:
> > > Ok, when I do the command: ptp4l -i eth1 -p /dev/ptp0 -m
> > > I get the following:
> > >
> > > ptp4l[468.371]: selected /dev/ptp0 as PTP clock
> > > ptp4l[468.372]: failed to read out the clock frequency adjustment:
> > Operation not supported
> > > ptp4l[468.372]: port 1: get_ts_info not supported
> > > ptp4l[468.372]: driver changed our HWTSTAMP options
> > > ptp4l[468.372]: tx_type   1 not 1
> > > ptp4l[468.372]: rx_filter 1 not 12
> > > ptp4l[468.372]: port 1: INITIALIZING to LISTENING on INITIALIZE
> > > ptp4l[468.373]: port 0: INITIALIZING to LISTENING on INITIALIZE
> > > ptp4l[474.372]: port 1: LISTENING to MASTER on
> > ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
> > 
> > This looks okay.
> > 
> > > and 2nd line I supose is not the problem (failed to read out the
> > > clock frequency adjustment). But what I should do next to get the
> > > time stamp times of packets?
> > 
> > What do you mean? The program appears to be working correctly,
> > including getting time stamps (otherwise you would see an error
> > message).
> > 
> > Thanks,
> > Richard
> > 
> 
> What you are seeing is your device going into master mode because there are no other nodes detected. Are you running at least one other node connected to the same network?
> 
> This is the expected behavior for a master node.
> 
> - Jake
> 
 		 	   		  

Re: [Linuxptp-users] time stamping

[Keller, J. E <jac...@in...>]

> -----Original Message-----
> From: Richard Cochran [mailto:ric...@gm...]
> Sent: Friday, July 19, 2013 10:24 AM
> To: Milutin Aksic
> Cc: lin...@li...
> Subject: Re: [Linuxptp-users] time stamping
> 
> On Fri, Jul 19, 2013 at 04:29:07PM +0100, Milutin Aksic wrote:
> > Ok, when I do the command: ptp4l -i eth1 -p /dev/ptp0 -m
> > I get the following:
> >
> > ptp4l[468.371]: selected /dev/ptp0 as PTP clock
> > ptp4l[468.372]: failed to read out the clock frequency adjustment:
> Operation not supported
> > ptp4l[468.372]: port 1: get_ts_info not supported
> > ptp4l[468.372]: driver changed our HWTSTAMP options
> > ptp4l[468.372]: tx_type   1 not 1
> > ptp4l[468.372]: rx_filter 1 not 12
> > ptp4l[468.372]: port 1: INITIALIZING to LISTENING on INITIALIZE
> > ptp4l[468.373]: port 0: INITIALIZING to LISTENING on INITIALIZE
> > ptp4l[474.372]: port 1: LISTENING to MASTER on
> ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
> 
> This looks okay.
> 
> > and 2nd line I supose is not the problem (failed to read out the
> > clock frequency adjustment). But what I should do next to get the
> > time stamp times of packets?
> 
> What do you mean? The program appears to be working correctly,
> including getting time stamps (otherwise you would see an error
> message).
> 
> Thanks,
> Richard
> 

What you are seeing is your device going into master mode because there are no other nodes detected. Are you running at least one other node connected to the same network?

This is the expected behavior for a master node.

- Jake

Re: [Linuxptp-users] time stamping

[Richard C. <ric...@gm...>]

On Fri, Jul 19, 2013 at 04:29:07PM +0100, Milutin Aksic wrote:
> Ok, when I do the command: ptp4l -i eth1 -p /dev/ptp0 -m 
> I get the following:
> 
> ptp4l[468.371]: selected /dev/ptp0 as PTP clock
> ptp4l[468.372]: failed to read out the clock frequency adjustment: Operation not supported
> ptp4l[468.372]: port 1: get_ts_info not supported
> ptp4l[468.372]: driver changed our HWTSTAMP options
> ptp4l[468.372]: tx_type   1 not 1
> ptp4l[468.372]: rx_filter 1 not 12
> ptp4l[468.372]: port 1: INITIALIZING to LISTENING on INITIALIZE
> ptp4l[468.373]: port 0: INITIALIZING to LISTENING on INITIALIZE
> ptp4l[474.372]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES

This looks okay.

> and 2nd line I supose is not the problem (failed to read out the
> clock frequency adjustment). But what I should do next to get the
> time stamp times of packets?

What do you mean? The program appears to be working correctly,
including getting time stamps (otherwise you would see an error
message).

Thanks,
Richard

Re: [Linuxptp-users] time stamping

[Milutin A. <mil...@ho...>]

Ok, when I do the command: ptp4l -i eth1 -p /dev/ptp0 -m 
I get the following:

ptp4l[468.371]: selected /dev/ptp0 as PTP clock
ptp4l[468.372]: failed to read out the clock frequency adjustment: Operation not supported
ptp4l[468.372]: port 1: get_ts_info not supported
ptp4l[468.372]: driver changed our HWTSTAMP options
ptp4l[468.372]: tx_type   1 not 1
ptp4l[468.372]: rx_filter 1 not 12
ptp4l[468.372]: port 1: INITIALIZING to LISTENING on INITIALIZE
ptp4l[468.373]: port 0: INITIALIZING to LISTENING on INITIALIZE
ptp4l[474.372]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
and 2nd line I supose is not the problem (failed to read out the clock frequency adjustment). But what I should do next to get the time stamp times of packets?
 		 	   		  

Re: [Linuxptp-users] time stamping

[Richard C. <ric...@gm...>]

On Fri, Jul 19, 2013 at 03:58:08PM +0100, Milutin Aksic wrote:
> Hello,
> I've just read that ethtool -T option is available in later kernels (from 3.5) but ptp4l still doesn't work properly.

Please keep the list on CC.

Thanks,
Richard

Re: [Linuxptp-users] time stamping

[Richard C. <ric...@gm...>]

On Fri, Jul 19, 2013 at 03:41:07PM +0100, Milutin Aksic wrote:
> Hello,
> I'm using kernel 3.3.4-5.fc17.i686.PAE (Fedora 17) and the driver is igb-4.3.0 compiled on my machine.

[Adding the list back onto CC]

Okay, then there is no problem.

The ethtool command was added in kernel 3.5. Your kernel is too old
for that.  But, the ptp4l program should work just fine, as long as
you give /dev/ptpX on the command line.

HTH,
Richard

Re: [Linuxptp-users] time stamping

[Richard C. <ric...@gm...>]

On Fri, Jul 19, 2013 at 03:27:37PM +0100, Milutin Aksic wrote:
> 
> There is /dev/ptp0 on my machine and it is valid but the problem is
> with network card as it says get_ts_info not supported like that
> time stamping is not supported but I read it in manual that it is
> supported.  I don't know what I'm doing wrong.

Can you tell us what kernel version you are using?

And are you using the igb driver from your kernel, or the Intel out of
tree drivers?

Thanks,
Richard

[Linuxptp-users] time stamping

[Milutin A. <mil...@ho...>]

Hello,
I have Intel i210-t1 network card and when I enter command ethtool -T eth1 to see time stamping capabilities it says that time stamping is not supported by the card however I read in manual of my card that time stamping is supported.
When I enter a command: ptp4l -i eth1 -p /dev/ptp0 -m
it says following

ptp4l[1880.852]: selected /dev/ptp0 as PTP clock
ptp4l[1880.852]: failed to read out the clock frequency adjustment: Operation not supported
ptp4l[1880.852]: port 1: get_ts_info not supported
ptp4l[1880.853]: driver changed our HWTSTAMP options

There is /dev/ptp0 on my machine and it is valid but the problem is with network card as it says get_ts_info not supported like that time stamping is not supported but I read it in manual that it is supported.
I don't know what I'm doing wrong.
Thank you in advance,
MIlutin Aksic.

 		 	   		  

Re: [Linuxptp-users] Issue in Hardware timestamping with I210 NIC

[Richard C. <ric...@gm...>]

On Thu, Jul 18, 2013 at 12:48:41PM +0530, Aman Sharma wrote:
> *
> As my kernel version is more then 3.0, Please help me to
> enable CONFIG_PTP_1588_CLOCK support in kernel.

You will have to compile your own kernel.

There are lots and lots of tutorials out there on how to do
it. However, this list is *not* the place to teach you how to compile
a kernel.

Sorry,
Richard

[Linuxptp-users] Issue in Hardware timestamping with I210 NIC

[Aman S. <ama...@gm...>]

Hi All,

We have intel I210Nic card inserted in x86 machine Ubuntu 12.10 with kernel
3.5.0-17-generic version.

When we are trying to run Linux ptp with hardware timestamp mode, it gives
below error message:
*interface does not support requested timestamping mode*

we are trying to compile I210 igb driver with PTP option gives following
error:

*make CFLAGS_EXTRA="-DIGB_PTP" install*
*
*
*/home/user/Downloads/igb-4.3.0/src/kcompat.h:3454:2: error: #error Cannot
enable PTP Hardware Clock support due to a pre-3.0 kernel version or **
CONFIG_PTP_1588_CLOCK** not enabled in the kernel.*
*
*
As my kernel version is more then 3.0, Please help me to
enable CONFIG_PTP_1588_CLOCK support in kernel.

Thanks in advance for your precious help and time.


--
Regards

AMAN SHARMA
*
*

Re: [Linuxptp-users] Issue in 802.1AS

[Richard C. <ric...@gm...>]

On Tue, Jul 16, 2013 at 11:17:02AM +0530, Aman Sharma wrote:
> Hi All,
> 
> We are running gPTP between two linux machines having Broadcom switch as a
> intermidate device.In this Broadcom switch also support gPTP i.e 802.1AS
> .So in this case Broadcom switch act as a P2P transparent clock with Port 1
> and Port 2.Port 1 is connected to Laptop_1 and Port 2 is connected to
> Laptop_2.
> 
> When running* Laptop_1 :- Master mode* and  *Laptop_2 :- Slave mode*
> and *Broadcom
> switch :- P2P transparent clock*.
> 
> And Correction field is updated to the residence delay at the Laptop_2.

Um, you have Laptop_2 as an end station, and so it does not have any
residence delay at all.

> In this,My question is this : In The transparent clock, Port 1 act as
> Master mode and Port 2 act as slave mode.
> But I read that It will just send the Peer 2 peer delays packets and update
> the correction field according to the residence time.Means No master or
> slave mode are there in the Transparent clock.
> 
> *I want to know, whether gPTP supports boundary clock mode or not?*

There are no boundary clocks in gPTP, just bridges and end stations.

But ptp4l does work as an end station together with bridges. I have
tested it with the Titanium 411 AVB Ethernet Bridge. I don't have a
Broadcom bridge to test, but ptp4l should work with it.

HTH,
Richard

[Linuxptp-users] Issue in 802.1AS

[Aman S. <ama...@gm...>]

Hi All,

We are running gPTP between two linux machines having Broadcom switch as a
intermidate device.In this Broadcom switch also support gPTP i.e 802.1AS
.So in this case Broadcom switch act as a P2P transparent clock with Port 1
and Port 2.Port 1 is connected to Laptop_1 and Port 2 is connected to
Laptop_2.

When running* Laptop_1 :- Master mode* and  *Laptop_2 :- Slave mode*
and *Broadcom
switch :- P2P transparent clock*.

And Correction field is updated to the residence delay at the Laptop_2.

In this,My question is this : In The transparent clock, Port 1 act as
Master mode and Port 2 act as slave mode.
But I read that It will just send the Peer 2 peer delays packets and update
the correction field according to the residence time.Means No master or
slave mode are there in the Transparent clock.

*I want to know, whether gPTP supports boundary clock mode or not?*

Can you Please help me in this.

--
Regards
Aman

Re: [Linuxptp-users] Bug in LinuxPTP

[Richard C. <ric...@gm...>]

On Fri, Jul 12, 2013 at 07:34:10PM +0530, Aman Sharma wrote:
> 
> After increasing it to 3600, slave time is updated according to the master
> time.But the master machine is not sending Sync message and no follow_up is
> there.Both machines directly sending Peer delay message to each other using
> gPTP.
> 
> Is there any reason for not sending Sync meassage to slave machine.

Read this once again ...

> >    neighborPropDelayThresh
> >           Upper limit for peer delay in nanoseconds. If the estimated peer
> >           delay is greater than this value  the  port  is  marked  as  not
> >           802.1AS capable.

and notice the part about "not capable."

Why don't you try a more reasonable value?

Richard

Re: [Linuxptp-users] Bug in LinuxPTP

[Aman S. <ama...@gm...>]

Hi Richard,

Thanks for the response.

After increasing it to 3600, slave time is updated according to the master
time.But the master machine is not sending Sync message and no follow_up is
there.Both machines directly sending Peer delay message to each other using
gPTP.

Is there any reason for not sending Sync meassage to slave machine.

--
Regards
Aman




On Fri, Jul 12, 2013 at 6:48 PM, Richard Cochran
<ric...@gm...>wrote:

> On Fri, Jul 12, 2013 at 05:06:35PM +0530, Aman Sharma wrote:
> >
> > when running linuxPTP with gPTP configuration between two linux machines,
> > then they are just sending peer delay request to each other and other one
> > also gives response for the same request.Means Master is not sending Sync
> > message and no follow_up is there.And in log messages ,it shows :
>
> Probably you are using software time stamping. If so, you need to
> increase neighborPropDelayThresh. Read the ptp4l.8 man page, and you
> will find:
>
>    neighborPropDelayThresh
>           Upper limit for peer delay in nanoseconds. If the estimated peer
>           delay is greater than this value  the  port  is  marked  as  not
>           802.1AS capable.
>
> HTH,
> Richard
>

Re: [Linuxptp-users] Bug in LinuxPTP

[Richard C. <ric...@gm...>]

On Fri, Jul 12, 2013 at 05:06:35PM +0530, Aman Sharma wrote:
> 
> when running linuxPTP with gPTP configuration between two linux machines,
> then they are just sending peer delay request to each other and other one
> also gives response for the same request.Means Master is not sending Sync
> message and no follow_up is there.And in log messages ,it shows :

Probably you are using software time stamping. If so, you need to
increase neighborPropDelayThresh. Read the ptp4l.8 man page, and you
will find:

   neighborPropDelayThresh
          Upper limit for peer delay in nanoseconds. If the estimated peer
          delay is greater than this value  the  port  is  marked  as  not
          802.1AS capable.

HTH,
Richard

Re: [Linuxptp-users] Bug in LinuxPTP

[Aman S. <ama...@gm...>]

Hi Richard,

Thanks for your response.

when running linuxPTP with gPTP configuration between two linux machines,
then they are just sending peer delay request to each other and other one
also gives response for the same request.Means Master is not sending Sync
message and no follow_up is there.And in log messages ,it shows :

ptp4l[2437.862]: port 1: master sync timeout
ptp4l[2437.937]: port 1: master tx announce timeout
ptp4l[2437.948]: port 1: delay timeout
ptp4l[2437.987]: port 1: master sync timeout
ptp4l[2438.113]: port 1: master sync timeout
ptp4l[2438.238]: port 1: master sync timeout
ptp4l[2438.363]: port 1: master sync timeout
ptp4l[2438.489]: port 1: master sync timeout

Can you Please help me in this.

--
Regards
Aman




On Fri, Jul 12, 2013 at 4:40 PM, Richard Cochran
<ric...@gm...>wrote:

> On Fri, Jul 12, 2013 at 04:33:03PM +0530, Aman Sharma wrote:
> > Hi Richard,
> >
> > Can you please tell me how to enable 802.1as in the linuxPTP source code.
> > By default,802.1as is in off state and what are the dependencies for the
> > same.
>
> ptp4l -f gPTP.cfg
>
> HTH,
> Richard
>

Re: [Linuxptp-users] Bug in LinuxPTP

[Richard C. <ric...@gm...>]

On Fri, Jul 12, 2013 at 04:33:03PM +0530, Aman Sharma wrote:
> Hi Richard,
> 
> Can you please tell me how to enable 802.1as in the linuxPTP source code.
> By default,802.1as is in off state and what are the dependencies for the
> same.

ptp4l -f gPTP.cfg

HTH,
Richard

Re: [Linuxptp-users] Bug in LinuxPTP

[Aman S. <ama...@gm...>]

Hi Richard,

Can you please tell me how to enable 802.1as in the linuxPTP source code.
By default,802.1as is in off state and what are the dependencies for the
same.


--
regards
Aman



On Fri, Jul 5, 2013 at 1:40 PM, Aman Sharma <ama...@gm...>wrote:

> Hi Richard,
>
> Thanks for the Support.
> We are able to run this now.
>
> --
> Regards
> Aman Sharma
>
>
> On Thu, Jul 4, 2013 at 4:02 PM, Richard Cochran <ric...@gm...>wrote:
>
>> On Thu, Jul 04, 2013 at 02:59:57PM +0530, Aman Sharma wrote:
>>
>> > Machine details:
>> > OS: 12.04 ubuntu
>> > Kermel version: 3.2.0-40-generic
>> > Ethernet controller: INTEL 82579LM with e1000e kernel driver
>>
>> ...
>>
>> > We are not able to figure out why "send sync failed" is happening
>> > interface is UP and connected to other linux machine with linuxptp
>> > runnning.
>>
>> It is because the e1000e needs kernel version 3.5 or newer to support
>> software transmit time stamps.
>>
>> See the Driver Support Matrix at:
>>
>>    http://linuxptp.sourceforge.net/
>>
>> Thanks,
>> Richard
>>
>
>

Re: [Linuxptp-users] About gptp and ptp 1588

[Richard C. <ric...@gm...>]

On Fri, Jul 12, 2013 at 01:43:26PM +0530, Aman Sharma wrote:
> Hi Jacob,
> 
> One more question: Is there any packet difference between gPTP packet and
> IEEE 1588 packets.Can you send me the sniffers of both with working in P2P
> TRANSPARENT CLOCK mode.

This list is for discussing the linuxptp programs.

This is *not* for teaching you about PTP.

If you want a recommendation about which settings to use for linuxptp,
then you need to describe your application to us first.
 
> Actually I am little bit confused with this gPTP. So please  make it clear
> ASAP.

Please do your own homework. You can start by reading the two
standards. Both of them are available from the IEEE.

Good luck,
Richard

Re: [Linuxptp-users] About gptp and ptp 1588

[Aman S. <ama...@gm...>]

Hi Jacob,

One more question: Is there any packet difference between gPTP packet and
IEEE 1588 packets.Can you send me the sniffers of both with working in P2P
TRANSPARENT CLOCK mode.

Actually I am little bit confused with this gPTP. So please  make it clear
ASAP.

Thanks for your Attention towards me.

--
regards
Aman

On Fri, Jul 12, 2013 at 9:37 AM, Aman Sharma <ama...@gm...>wrote:

> Hi Jacob,
>
> Thanks for your Reply.
>
> Can you suggest some more documents/Pdfs to understand gPTP and IEEE 1588
> more clearly.This will be helpful to my Team.
>
> And if I am running Gptp in the Switch as a P2P Transparent clock mode,
> then what it does actually.Means Switch will add some correction field i.e
> correct the residence delay.
>
>
> --
> Regards
> Aman Sharma
>
>
>
>

Re: [Linuxptp-users] About gptp and ptp 1588

[Aman S. <ama...@gm...>]

Hi Jacob,

Thanks for your Reply.

Can you suggest some more documents/Pdfs to understand gPTP and IEEE 1588
more clearly.This will be helpful to my Team.

And if I am running Gptp in the Switch as a P2P Transparent clock mode,
then what it does actually.Means Switch will add some correction field i.e
correct the residence delay.


--
Regards
Aman Sharma

Re: [Linuxptp-users] About gptp and ptp 1588

[Keller, J. E <jac...@in...>]

Hello -

gPTP is supposed to be a subset of 1588 PTP, however it has modifications to the standard. It is part of 802.1AS, and the gPTP standard is freely available online. In general, gPTP just has more restrictions on what it defines as acceptable, ie: you can't use E2E mode in gPTP. Both support Transparent clocks, assuming you have hardware capable of it. I don't know if linuxPTP supports transparent clocks at this time.

The gPTP.config file uses the settings that make LinuxPTP compatible with the gPTP standard. Some of those changes may result in better performance of PTP, (depending on your system and the requirements).

Fundamentally they are very similar, and perform using the same type of mechanisms.

gPTP is supposed to be a profile for PTP but it has some non-compatible changes which are not supposed to be allowed for a profile. The following is a list of the profile requirements.

PTP Profile Included in
IEEE 802.1AS - 1
Profile Item Specification
Best master clock
algorithm (BMCA) option
Alternate BMCA (similar, but not identical, to
algorithm (BMCA) option 1588 clause 9) 1588 clause 9)
Management mechanism SNMP MIB
Path delay mechanism Peer delay mechanism
802 1AS ifi d f l 802.1AS specifies default S i l 1/8
values; 802.1BA may
specify additional ranges
for each AVB profile
Sync interval: 1/8 s
Announce interval: 1 s
Pdelay interval: 1 s
for each AVB profile
Announce receipt timeout: 2 announce
intervals
Sync receipt timeout: 3 sync intervals
Node types Boundary clock (synchronization specified in
manner similar to peer-to-peer transparent
clock; BC and peer-to-peer TC synchronization
can be shown to be mathematically can be shown to be mathematically
equivalent, see [6])
Ordinary clock

This is taken from http://www.itu.int/dms_pub/itu-t/oth/06/38/T06380000040002PDFE.pdf



From: Aman Sharma [mailto:ama...@gm...]
Sent: Thursday, July 11, 2013 12:06 AM
To: lin...@li...
Subject: [Linuxptp-users] About gptp and ptp 1588

Hi all,


Can anyone please explain the difference between gPTP and 1588 PTP .And How do I know which is better one for my system architecture.Detail explanation is required for understanding the architecture of both gPTP and 1588 PTP.

Can we use E2E and P2P Transparent clock in gPTP ?

Please help me in this ASAP.
Plz Revert me in case you have any query.

--
regards
Aman Sharma

[Linuxptp-users] About gptp and ptp 1588

[Aman S. <ama...@gm...>]

Hi all,


Can anyone please explain the difference between gPTP and 1588 PTP .And How
do I know which is better one for my system architecture.Detail explanation
is required for understanding the architecture of both gPTP and 1588 PTP.

Can we use E2E and P2P Transparent clock in gPTP ?

Please help me in this ASAP.
Plz Revert me in case you have any query.

--
regards
Aman Sharma

Re: [Linuxptp-users] Bug in LinuxPTP

[Aman S. <ama...@gm...>]

Hi Richard,

Thanks for the Support.
We are able to run this now.

--
Regards
Aman Sharma


On Thu, Jul 4, 2013 at 4:02 PM, Richard Cochran <ric...@gm...>wrote:

> On Thu, Jul 04, 2013 at 02:59:57PM +0530, Aman Sharma wrote:
>
> > Machine details:
> > OS: 12.04 ubuntu
> > Kermel version: 3.2.0-40-generic
> > Ethernet controller: INTEL 82579LM with e1000e kernel driver
>
> ...
>
> > We are not able to figure out why "send sync failed" is happening
> > interface is UP and connected to other linux machine with linuxptp
> > runnning.
>
> It is because the e1000e needs kernel version 3.5 or newer to support
> software transmit time stamps.
>
> See the Driver Support Matrix at:
>
>    http://linuxptp.sourceforge.net/
>
> Thanks,
> Richard
>

Re: [Linuxptp-users] Bug in LinuxPTP

[Richard C. <ric...@gm...>]

On Thu, Jul 04, 2013 at 02:59:57PM +0530, Aman Sharma wrote:

> Machine details:
> OS: 12.04 ubuntu
> Kermel version: 3.2.0-40-generic
> Ethernet controller: INTEL 82579LM with e1000e kernel driver

...

> We are not able to figure out why "send sync failed" is happening
> interface is UP and connected to other linux machine with linuxptp
> runnning.

It is because the e1000e needs kernel version 3.5 or newer to support
software transmit time stamps.

See the Driver Support Matrix at:

   http://linuxptp.sourceforge.net/

Thanks,
Richard