That's excellent, thank you for this.  I was unable to find 3.2.4.2
anywhere in the https://sourceforge.net/projects/e1000/ project.
I searched for SYSTIM, yanir, and 3.2.4.2
Am I looking in the wrong place?

Thanks again.

On Sun, May 31, 2015 at 1:35 PM, Lubetkin, YanirX
<yanirx.lubet...@intel.com> wrote:
> Hi,
>
> I have submitted a version that fixes this issue to sourceforge (3.2.4.2)
> I have also submitted a set of patches upstream, they can be found in 
> intel-wired-...@lists.osuosl.org.
> If all goes well they will be applied to branch dev-queue in:
> https://git.kernel.org/cgit/linux/kernel/git/jkirsher/next-queue.git/
>
> Please review the patch that deals with SYSTIM. For a description of the 
> problem/fix
>
> BR,
> Yanir
>
>> -----Original Message-----
>> From: Robb [mailto:rbarr...@gmail.com]
>> Sent: Saturday, May 30, 2015 20:08
>> To: e1000-devel@lists.sourceforge.net
>> Subject: [E1000-devel] Problem with I217-LM blowing up PTP timestamps
>>
>> For whatever reason my I217-LM seems to blow up time stamps when I try
>> to use it to set system time using PTP.
>>
>> I tried the PTP mailing list and was referred here as it is believed to be a 
>> HW
>> issue with the I217-LM
>>
>> My set up is as follows:
>>
>> Two CentOS 6.5 machines
>> 2.6.32-504.16.2.el6.x86_64
>> linuxptp-1.3-1.el6.x86_64
>>
>> Machine1 eth1 [igb    5.0.5-k]    Intel I210 (rev 03)
>> Machine2 eth0 [e1000e 2.3.2-k] Intel I217-LM (rev 05)
>>
>> Machine1 eth1 hooked directly to Machine2 eth0
>>
>> Machine1 (master):
>> sudo ptp4l -i eth1 -m -2
>> sudo phc2sys -s eth1 -c CLOCK_REALTIME -w
>>
>> Machine2:
>> sudo ptp4l -i eth0 -m -2
>> sudo phc2sys -s eth0 -c CLOCK_REALTIME -w
>>
>> Normally the offset blows up immediately unless I sync the machines with
>> NTP before doing anything else.  If I do get them to sync it doesn't last 
>> very
>> long and the following will happen on Machine2:
>>
>> 16:30:03 ptp4l: [4679.655] master offset        777 s2 freq   +4403
>> path delay     67209
>> 16:30:04 phc2sys: [4679.935] sys offset      -658 s2 freq   +3877 delay   
>> 1836
>> 16:30:04 ptp4l: [4680.655] master offset       2280 s2 freq   +6139
>> path delay     67209
>> 16:30:05 phc2sys: [4680.936] sys offset      1353 s2 freq   +5690 delay   
>> 1504
>> 16:30:05 ptp4l: [4681.655] master offset      -1349 s2 freq   +3194
>> path delay     67123
>> 16:30:06 phc2sys: [4681.936] sys offset    -14484 s2 freq   -9741 delay   
>> 1840
>> 16:30:06 ptp4l: [4682.656] master offset 70368744179084 s2 freq
>> +599999999 path delay     67123
>> 16:30:07 phc2sys: [4682.936] sys offset -70368575979115 s2 freq
>> -500000 delay   1440
>> 16:30:07 ptp4l: [4683.656] master offset 70368127382914 s2 freq
>> +599999999 path delay  17621798
>> 16:30:08 phc2sys: [4683.936] sys offset -70367975616192 s2 freq
>> -500000 delay   1842
>> 16:30:08 ptp4l: [4684.657] master offset 70367522033588 s2 freq
>> +599999999 path delay  22920656
>> 16:30:09 phc2sys: [4684.937] sys offset -70367375237559 s2 freq
>> -500000 delay   1441
>>
>>
>> I have read that there was some problems with the e1000e driver so I tried
>> with the 3.1.0.2-NAPI version, but still have the same problem as above.
>>
>> Does anyone have any ideas what could be the problem here, what is
>> causing the I217-LM to suddenly have a 70368744179084nS offset?
>>
>> Thanks.
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> E1000-devel mailing list
>> E1000-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/e1000-devel
>> To learn more about Intel&#174; Ethernet, visit
>> http://communities.intel.com/community/wired
> ---------------------------------------------------------------------
> Intel Israel (74) Limited
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>

------------------------------------------------------------------------------
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel&#174; Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to