Menu
▾
▴
linuxptp-users
|
From: Ledda W. E. <Wil...@it...> - 2013-07-26 11:42:19
|
Hi all, I have encountered some trouble using the phc2sys and I don't know how to solve. After some times (about ten minutes), during the execution, the offset reported between the two clock become suddenly very high. ... phc 27 s4 1374832244.265263254 drift -5661.93 phc 36 s4 1374832245.265387488 drift -5651.13 phc -56 s4 1374832246.265498437 drift -5667.93 phc 82 s4 1374832247.265616591 drift -5643.33 phc 43 s4 1374832248.265710877 drift -5630.43 phc -35004266893 s4 1374832214.261566870 drift -5630.43 phc -35003773008 s4 1374832215.261718369 drift -5630.43 phc -35003278873 s4 1374832216.261850060 drift -5630.43 phc -35002784574 s4 1374832217.261959739 drift -5630.43 phc -35002290414 s4 1374832218.262081436 drift -5630.43 phc -35001796210 s4 1374832219.262191674 drift -5630.43 phc -35001302057 s4 1374832220.262308201 drift -5630.43 phc -35000807865 s4 1374832221.262399782 drift -5630.43 phc -35000313287 s4 1374832222.262549779 drift -5630.43 phc -34999819463 s4 1374832223.262670778 drift -5630.43 phc -34999325427 s4 1374832224.262761871 drift -5630.43 phc -34998831261 s4 1374832225.262880912 drift -5630.43 phc -34998337019 s4 1374832226.263005684 drift -5630.43 ... Only when a restart the pch2sys the offset returns to a low value. Monitoring the output of ptp4l I don't see any changes in the status. The PHC remains synched with the GMC with an acceptable offset. Any idea? Reagrds William |
|
From: Richard C. <ric...@gm...> - 2013-07-26 12:53:20
|
On Fri, Jul 26, 2013 at 11:42:09AM +0000, Ledda William EXT wrote: > ... > phc 27 s4 1374832244.265263254 drift -5661.93 > phc 36 s4 1374832245.265387488 drift -5651.13 > phc -56 s4 1374832246.265498437 drift -5667.93 > phc 82 s4 1374832247.265616591 drift -5643.33 > phc 43 s4 1374832248.265710877 drift -5630.43 > phc -35004266893 s4 1374832214.261566870 drift -5630.43 This is 35 seconds, or the UTC-TAI offset. Can you show us the phc2sys command line? Are you using the Intel i210? Can you monitor the TIME_PROPERTIES_DATA_SET? For example: watch 'pmc -b 0 -u "get TIME_PROPERTIES_DATA_SET"' Thanks, Richard |
|
From: Ledda W. E. <Wil...@it...> - 2013-07-26 14:28:19
|
Hi, the command line is the following # pch2sys -i eth1 Now I will try also watch 'pmc -b 0 -u "get TIME_PROPERTIES_DATA_SET" I'm using the Intel i350 (not the i210) and the package release distributed with RHEL 6.4. linuxptp.x86_64 0-0.6.20121114gite6bbbb.el6 @rhel-x86_64-server-6 I know that it is not last one. I have tried to compile the version 1.2 but I can't since the HWTSTAMP_TX_ONESTEP_SYNC is not defined in net_tstamp.h -----Original Message----- From: Richard Cochran [mailto:ric...@gm...] Sent: 26 July 2013 14:53 To: Ledda William EXT Cc: lin...@li... Subject: Re: [Linuxptp-users] phc2sys trouble On Fri, Jul 26, 2013 at 11:42:09AM +0000, Ledda William EXT wrote: > ... > phc 27 s4 1374832244.265263254 drift -5661.93 > phc 36 s4 1374832245.265387488 drift -5651.13 > phc -56 s4 1374832246.265498437 drift -5667.93 > phc 82 s4 1374832247.265616591 drift -5643.33 > phc 43 s4 1374832248.265710877 drift -5630.43 > phc -35004266893 s4 1374832214.261566870 drift -5630.43 This is 35 seconds, or the UTC-TAI offset. Can you show us the phc2sys command line? Are you using the Intel i210? Can you monitor the TIME_PROPERTIES_DATA_SET? For example: watch 'pmc -b 0 -u "get TIME_PROPERTIES_DATA_SET"' Thanks, Richard |
|
From: Richard C. <ric...@gm...> - 2013-07-27 18:49:44
|
On Fri, Jul 26, 2013 at 02:27:53PM +0000, Ledda William EXT wrote: > I'm using the Intel i350 (not the i210) and the package release distributed with RHEL 6.4. > > linuxptp.x86_64 0-0.6.20121114gite6bbbb.el6 @rhel-x86_64-server-6 > > I know that it is not last one. I have tried to compile the version 1.2 but I can't since the HWTSTAMP_TX_ONESTEP_SYNC is not defined in net_tstamp.h If you install the "kernel header" package that goes with your kernel, then you should be able to compile ptp4l from source. Thanks, Richard |
|
From: Ledda W. E. <Wil...@it...> - 2013-07-26 15:10:07
|
Hi Richard,
I have tried to monitor the TIME_PROPERTIES_DATA_SET using the following command
./pmc -b 0 -i eth1 "get TIME_PROPERTIES_DATA_SET"
I get the always the following even when the problem appears
sending: GET TIME_PROPERTIES_DATA_SET
ece555.fffe.0bab40-1 seq 0 RESPONSE MANAGMENT_ERROR_STATUS
ece555.fffe.0bac80-16 seq 0 RESPONSE MANAGMENT TIME_PROPERTIES_DATA_SET
currentUtcOffset 35
leap61 0
leap59 0
currentUtcOffsetValid 1
ptpTimescale 1
timeTraceable 1
frequencyTraceable 1
timeSource 0x20
ece555.fffe.0bab00-16 seq 0 RESPONSE MANAGMENT TIME_PROPERTIES_DATA_SET
currentUtcOffset 35
leap61 0
leap59 0
currentUtcOffsetValid 1
ptpTimescale 1
timeTraceable 1
frequencyTraceable 1
timeSource 0x20
ece555.fffe.3fbf80-16 seq 0 RESPONSE MANAGMENT TIME_PROPERTIES_DATA_SET
currentUtcOffset 35
leap61 0
leap59 0
currentUtcOffsetValid 1
ptpTimescale 1
timeTraceable 1
frequencyTraceable 1
timeSource 0x20
008063.fffe.db5e80-16 seq 0 RESPONSE MANAGMENT TIME_PROPERTIES_DATA_SET
currentUtcOffset 35
leap61 0
leap59 0
currentUtcOffsetValid 1
ptpTimescale 1
timeTraceable 1
frequencyTraceable 1
timeSource 0x20
ece555.fffe.3f3600-5 seq 0 RESPONSE MANAGMENT TIME_PROPERTIES_DATA_SET
currentUtcOffset 35
leap61 0
leap59 0
currentUtcOffsetValid 1
ptpTimescale 1
timeTraceable 1
frequencyTraceable 1
timeSource 0x20
-----Original Message-----
From: Ledda William EXT [mailto:Wil...@it...]
Sent: 26 July 2013 16:28
To: Richard Cochran
Cc: lin...@li...
Subject: Re: [Linuxptp-users] phc2sys trouble
Hi,
the command line is the following
# pch2sys -i eth1
Now I will try also watch 'pmc -b 0 -u "get TIME_PROPERTIES_DATA_SET"
I'm using the Intel i350 (not the i210) and the package release distributed with RHEL 6.4.
linuxptp.x86_64 0-0.6.20121114gite6bbbb.el6 @rhel-x86_64-server-6
I know that it is not last one. I have tried to compile the version 1.2 but I can't since the HWTSTAMP_TX_ONESTEP_SYNC is not defined in net_tstamp.h
-----Original Message-----
From: Richard Cochran [mailto:ric...@gm...]
Sent: 26 July 2013 14:53
To: Ledda William EXT
Cc: lin...@li...
Subject: Re: [Linuxptp-users] phc2sys trouble
On Fri, Jul 26, 2013 at 11:42:09AM +0000, Ledda William EXT wrote:
> ...
> phc 27 s4 1374832244.265263254 drift -5661.93
> phc 36 s4 1374832245.265387488 drift -5651.13
> phc -56 s4 1374832246.265498437 drift -5667.93
> phc 82 s4 1374832247.265616591 drift -5643.33
> phc 43 s4 1374832248.265710877 drift -5630.43
> phc -35004266893 s4 1374832214.261566870 drift -5630.43
This is 35 seconds, or the UTC-TAI offset.
Can you show us the phc2sys command line?
Are you using the Intel i210?
Can you monitor the TIME_PROPERTIES_DATA_SET?
For example:
watch 'pmc -b 0 -u "get TIME_PROPERTIES_DATA_SET"'
Thanks,
Richard
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Linuxptp-users mailing list
Lin...@li...
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
|
|
From: Richard C. <ric...@gm...> - 2013-07-27 18:46:45
|
Can it be that you are also running ntpd (or some other program that sets the clock) at the same time? Thanks, Richard |
|
From: Ledda W. E. <Wil...@it...> - 2013-07-28 16:24:01
|
Great Richard! The ntpd was running at the same time! I have performed the following test: 1) run pch2sys without ntpd. The two clocks remains synchronized with low offset. 2) run ntpd: after some minutes the offset is influenced by the (UTC - TAI) 3) stop ntpd: the offset remains influenced by the UTC - TAI I expect to see a low offset after the stop of the ntpd service. Any suggestion for this? Thanks William -----Original Message----- From: Richard Cochran [mailto:ric...@gm...] Sent: 27 July 2013 20:46 To: Ledda William EXT Cc: lin...@li... Subject: Re: [Linuxptp-users] phc2sys trouble Can it be that you are also running ntpd (or some other program that sets the clock) at the same time? Thanks, Richard |
|
From: Richard C. <ric...@gm...> - 2013-07-28 18:40:30
|
On Sun, Jul 28, 2013 at 04:23:51PM +0000, Ledda William EXT wrote: > Great Richard! The ntpd was running at the same time! > > I have performed the following test: > > 1) run pch2sys without ntpd. The two clocks remains synchronized with low offset. > 2) run ntpd: after some minutes the offset is influenced by the (UTC - TAI) > 3) stop ntpd: the offset remains influenced by the UTC - TAI > > I expect to see a low offset after the stop of the ntpd service. Any suggestion for this? Sorry, I don't really follow what you mean here. In any case, you should run phc2sys so that it correctly accounts for the timescale difference. You i310 gets PTP timescale (TAI) from the network, and your Linux system clock is in UTC. If you run phc2sys in this way, then you don't need ntpd at all. HTH, Richard |
|
From: Richard C. <ric...@gm...> - 2013-07-28 18:47:54
|
On Sun, Jul 28, 2013 at 08:40:12PM +0200, Richard Cochran wrote:
>
> If you run phc2sys in this way, then you don't need ntpd at all.
For example:
phc2sys -i eth0 -O -35
HTH,
Richard
|
|
From: Ledda W. E. <Wil...@it...> - 2013-07-29 07:47:16
|
Ok Richard, thanks for the help!
Reagrds
William
-----Original Message-----
From: Richard Cochran [mailto:ric...@gm...]
Sent: 28 July 2013 20:48
To: Ledda William EXT
Cc: lin...@li...
Subject: Re: [Linuxptp-users] phc2sys trouble
On Sun, Jul 28, 2013 at 08:40:12PM +0200, Richard Cochran wrote:
>
> If you run phc2sys in this way, then you don't need ntpd at all.
For example:
phc2sys -i eth0 -O -35
HTH,
Richard
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X