On Wed, Nov 29, 2023 at 10:27:54PM +0800, paulzhn via Linuxptp-users wrote:
> I'm wondering why the offset exists.
- Linux system clock is in UTC timescale.
- PHC is in TAI timescale.
HTH,
Richard
___
Linuxptp-users mailing list
Linuxptp-users@lists.
Hi,
I want to sync my PHC clock with system clock as the source, so I executed the
command:
ptp4l -i ens2f1np1 -m
phc2sys -a -r -r -m
The phc2sys seems running correctly:
$phc2sys -a -r -r -m
phc2sys[7362514.851]: reconfiguring after port state change
phc2sys[7362514.851]: selecting ens2f1np
This is helpful, thank you Ed.
Thanks,
Nemo
On Friday, 16 June, 2023 at 03:08:38 pm GMT-4, Ed Branch
wrote:
TLDR: It could also be the GM.
I see this on embedded networks, ie. the whole network including the GM
is on the same power switch, it all comes up together, and none of the
TLDR: It could also be the GM.
I see this on embedded networks, ie. the whole network including the GM
is on the same power switch, it all comes up together, and none of the
RTC's have battery backup.
Maybe the "GM" is just another embedded computer that gets time from GPS
or something like
Thank you Ed!
I am using -w option but not -S. I now understand why the clock step is not
happening. But with -w phc2sys should start only after ptp4l, isn't it?
If yes, then why would this happen - "the clock has jumped from the epoch after
phc2sys started".
The only way is probably that "-w" o
You need either of:
1) a battery backup for the real-time clock so that it starts at a
reasonable time.
2) Use -w option to phc2sys so that it waits until ptp4l is synchronized.
3) Use the -S option to phc2sys so that it steps the clock if the offset
is above some threshold.
By default, phc2
Hi LinuxPTPUsers,
I have this weird problem sometimes with phc2syc. Please look at the log below,
ptp4l service is perfectly okay. But the phc2sys is stuck (although it measures
the offset correctly) and not adjusting the system time for some reason. Why
would this happen? Waiting for more than
Hi,
>Q1, I have learned the rms, and how can I get the offset value in the log
> of ptp4l?
If you want to see the raw offset value, you should turn
'summary_interval' down, in ptp4l.conf,
when summary_interval - sync_interval <= 0, the stats output raw
measurement value instead of
rms val
Hi,
> Q1， I can only find rms value in log of ptp4l, but no offset value. And this
> rms value does not converge. Is it normal? How can I get offset log?
The rms value is the statistic value of offset.
It depends on whether your test suites supports hwtimestamp or only
software timestamp, and the
Hi, I am using a embeded board, which contains a mcu and a soc.
Two chips communicate through a switch chip. The mcu works as ptp master, the
soc works as slave. The period of sync&follow up message is 0.125s.
Here is log of ptp slave:
# ptp4l -i vlan12 -f automotive-slave.cfg -m
We are just what is using what is there in the source code for phc2sys. the
code in question is in the sysoff.c file:
44 static int sysoff_precise(int fd, int64_t *result, uint64_t *ts)
45 {
46 struct ptp_sys_offset_precise pso;
47 memset(&pso, 0, sizeof(pso));
48 if (
On 5/18/2023 3:16 PM, Bernie Elayda wrote:
> And more detail on the Ethernet driver used on our NUC(duplicating previous
> info for completeness, too)
>
> Ubutnu 18.04 with kernel 5.4.0-generic
> System-manufacturer : Intel(R) Client Systems
> System-product-name : NUC10i7FNH
> Bios-release-
This is probably more useful than just 'intel NUC i7'::
System-manufacturer : Intel(R) Client Systems
System-product-name : NUC10i7FNH
Bios-release-date : 04/09/2021
Bios-version : FNCML357.0052.2021.0409.1144
Let me know if you need more detailed info. regards,bernardo
On Thu, May 18, 2023
an Intel i7 NUC running Ubutnu 18.04 with kernel 5.4.0-generic
Sent from fruit phone
> On May 18, 2023, at 10:20 AM, Jacob Keller wrote:
>
>
>
>> On 5/18/2023 9:14 AM, Bernie Elayda wrote:
>> Hello, I have an update. I obtained the HEAD for linuxptp yesterday and
>> re-ran my setup. Unfort
On 5/18/2023 9:14 AM, Bernie Elayda wrote:
> Hello, I have an update. I obtained the HEAD for linuxptp yesterday and
> re-ran my setup. Unfortunately, phc2sys failed again with a Connection
> timed out:
>
> phc2sys[470789.265]: CLOCK_REALTIME phc offset -63 s2 freq -9645
> delay 0
Hello, I have an update. I obtained the HEAD for linuxptp yesterday and
re-ran my setup. Unfortunately, phc2sys failed again with a Connection
timed out:
phc2sys[470789.265]: CLOCK_REALTIME phc offset -63 s2 freq -9645
delay 0
phc2sys[470790.265]: CLOCK_REALTIME phc offset -797
Thank you! We have the HEAD and re-running our test overnight. Will report back
on our results tomorrow
regards,bernardo
Sent from fruit phone
> On May 17, 2023, at 3:24 AM, Miroslav Lichvar wrote:
>
> On Fri, May 12, 2023 at 04:28:40PM -0700, Bernie Elayda wrote:
>> phc2sys will stop but p
On Fri, May 12, 2023 at 04:28:40PM -0700, Bernie Elayda wrote:
> phc2sys will stop but ptp4l will continue to run. This error appears to
> originate from the sysoff_precise function;Doesn't this error just mean
> when attempting to read PTP_SYS_OFFSET_PRECISE the kernel was just busy?
> Wouldn't i
Hello,
We are using linuxtptp 3.1.1 on an Intel i7 NUC running Ubutnu 18.04 with
kernel 5.4.0-generic.. We have linuxptp running on the Intel NUC configured
as an OC. Our grandmaster is a 3rd party device. This is all running on a
stand-alone network dedicated to PTP.
Every few hours, our phc2sys
Hello,
Have connected Server to a switch. The switch act as a Boundary clock and
provides timing to the server using ptp.
On the server, we are running ptp4l and phc2sys process.
As part of testing, we are doing disable and enable of PTP on the switch.
Sometimes we are observing phc2sys proces
On Wed, Mar 30, 2022 at 01:41:18AM +0300, Vladimir Oltean wrote:
> I think your comparison between NTP and PTP is a bit flawed because they
> serve different purposes, PTP being there for 'precise' synchronization
> rather than following the time of day.
I don't think they are that different. But
Hi Miroslav,
On Tue, Mar 29, 2022 at 09:10:59AM +0200, Miroslav Lichvar wrote:
> On Fri, Mar 25, 2022 at 02:45:04AM +0200, Vladimir Oltean wrote:
> > In general, we all seem to agree that the initial PTP time is largely
> > irrelevant until you start looking at it for some particular reason
> > (d
> In the Master I didn't use phc2sys in my first tests,
> and I was getting -300ms latency values between
> the two setups.
That is a different issue than first described. I was referring to the
problem of the date from the master being set to 2018 rather than the
current date.
I do not remember
On Fri, Mar 25, 2022 at 02:45:04AM +0200, Vladimir Oltean wrote:
> In general, we all seem to agree that the initial PTP time is largely
> irrelevant until you start looking at it for some particular reason
> (debugging). Or at least, almost everyone seems to agree. I remember
> Miroslav Lichvar ar
> -Original Message-
> From: Vladimir Oltean
> Sent: Thursday, March 24, 2022 6:13 PM
> To: Keller, Jacob E
> Cc: ch...@chriscaudle.org; linuxptp-users@lists.sourceforge.net
> Subject: Re: [Linuxptp-users] phc2sys not synchr. to right time and date
>
> On Fr
On Sat, Mar 26, 2022 at 10:25:43AM +, Federico Murciano wrote:
> Do you have concrete instrucctions that I could try in master and
> slave in order to correct this? Do you think it is possible that due
> to the setups where I just plug in the device to electricity and
> other setup that is plu
ted Artificial Intelligence Laboratory Chief Executive
Director: Prof. Dr. Dr. h.c. Sahin Albayrak
Von: Chris Caudle <6807.ch...@pop.powweb.com>
Gesendet: Donnerstag, 24. März 2022 21:04
An: linuxptp-users@lists.sourceforge.net
Betreff: Re: [Linuxpt
acob E
> > > Cc: ch...@chriscaudle.org; linuxptp-users@lists.sourceforge.net
> > > Subject: Re: [Linuxptp-users] phc2sys not synchr. to right time and date
> > >
> > > On Fri, Mar 25, 2022 at 12:27:53AM +, Keller, Jacob E wrote:
> > > > > (
On Fri, Mar 25, 2022 at 12:52:02AM +, Keller, Jacob E wrote:
> > -Original Message-
> > From: Vladimir Oltean
> > Sent: Thursday, March 24, 2022 5:45 PM
> > To: Keller, Jacob E
> > Cc: ch...@chriscaudle.org; linuxptp-users@lists.sourceforge.net
&g
> -Original Message-
> From: Vladimir Oltean
> Sent: Thursday, March 24, 2022 5:45 PM
> To: Keller, Jacob E
> Cc: ch...@chriscaudle.org; linuxptp-users@lists.sourceforge.net
> Subject: Re: [Linuxptp-users] phc2sys not synchr. to right time and date
>
> On Fr
On Fri, Mar 25, 2022 at 12:27:53AM +, Keller, Jacob E wrote:
> > (there might be other reasons why his setup is working, but)
> > Some kernel Ethernet drivers have a bad habit of writing the current
> > (UTC) system time (derived from the battery-backed RTC) into the PHC
> > current (TAI) time
> -Original Message-
> From: Vladimir Oltean
> Sent: Thursday, March 24, 2022 11:10 AM
> To: ch...@chriscaudle.org
> Cc: linuxptp-users@lists.sourceforge.net
> Subject: Re: [Linuxptp-users] phc2sys not synchr. to right time and date
>
> On Thu, Mar 24, 2022 at
> -Original Message-
> From: Federico Murciano
> Sent: Thursday, March 24, 2022 3:02 AM
> To: Keller, Jacob E ; linuxptp-
> us...@lists.sourceforge.net
> Cc: Sebastian Peters
> Subject: AW: phc2sys not synchr. to right time and date
>
> Hi Jacob,
>
> Thank you for your answer. That i
> I can also see in the Master devices this difference in its clocks:
> from 32 seconds to 31 in the RTC time:
> I did hwclock -w and still get this values
None of that has anything to do with the PTP hardware clock (PHC) in the
network controller.
The system clock runs on the system processor, th
;
Gesendet: Mittwoch, 23. März 2022 18:33
An: linuxptp-users@lists.sourceforge.net
Betreff: Re: [Linuxptp-users] phc2sys not synchr. to right time and date
> From: Federico Murciano
> Subject: [Linuxptp-users] phc2sys not synchr. to right time and date
> Message-ID: <1648054395763.43...
ctor: Prof. Dr. Dr. h.c. Sahin Albayrak
Von: Vladimir Oltean
Gesendet: Donnerstag, 24. März 2022 19:09
An: ch...@chriscaudle.org
Cc: linuxptp-users@lists.sourceforge.net
Betreff: Re: [Linuxptp-users] phc2sys not synchr. to right time and date
On Thu, Mar 24,
On Thu, Mar 24, 2022 at 09:14:08AM -0500, Chris Caudle wrote:
> On Thu, March 24, 2022 5:02 am,
> linuxptp-users-requ...@lists.sourceforge.net wrote:
> > From: Federico Murciano
> > Subject: Re: [Linuxptp-users] phc2sys not synchr. to right time and
> > date
> >
On Thu, March 24, 2022 5:02 am,
linuxptp-users-requ...@lists.sourceforge.net wrote:
> From: Federico Murciano
> Subject: Re: [Linuxptp-users] phc2sys not synchr. to right time and
> date
> Message-ID: <1648115598945.22...@dai-labor.de>
> Thank you for your answer. Yes
, Jacob E
Mi 23.03.2022 18:39
-Original Message- From: Federico Murciano
Sent: Wednesday, March 23, 2022 10:13 AM To:
linuxptp-users@lists.sourceforge.net Cc: Sebastian Peters
Subject: Re: [Linuxptp-users] phc2sys
Federico Murciano
Mi 23.03.2022 18:15
Hey agai, I also tried using
;
Gesendet: Mittwoch, 23. März 2022 18:33
An: linuxptp-users@lists.sourceforge.net
Betreff: Re: [Linuxptp-users] phc2sys not synchr. to right time and date
> From: Federico Murciano
> Subject: [Linuxptp-users] phc2sys not synchr. to right time and date
> Message-ID: <1648054395763.43...
> From: Federico Murciano
> Subject: [Linuxptp-users] phc2sys not synchr. to right time and date
> Message-ID: <1648054395763.43...@dai-labor.de>
> sudo phc2sys -s enp0s31f6 -O 0 -m
That is on the slave computer?
What is the phc2sys options and output messages on the maste
> -Original Message-
> From: Federico Murciano
> Sent: Wednesday, March 23, 2022 10:13 AM
> To: linuxptp-users@lists.sourceforge.net
> Cc: Sebastian Peters
> Subject: Re: [Linuxptp-users] phc2sys not synchr. to right time and date
>
> edge2@
yrak
Von: Federico Murciano
Gesendet: Mittwoch, 23. März 2022 17:53
An: linuxptp-users@lists.sourceforge.net
Cc: Sebastian Peters
Betreff: [Linuxptp-users] phc2sys not synchr. to right time and date
Hello everyone,
I am trying to sync different Ubuntu computers to the ptp ma
Hello everyone,
I am trying to sync different Ubuntu computers to the ptp master clock from
another device connected to each of them.
The setup is very easy:
Ubuntu Laptop as Slave <-> Ubuntu device with GPS signal as Master
The problem is that for one system, everything is working right, b
Hey everyone,
I have been trying for a while to set up my master-slave PTP sync but in the
slave I can see an offset. When I ask for the date in the slave and the master
they have around 36 seconds difference.
If I do not run this command after synchronizing with ptp4l, the slave is 36
secon
hi,
phc2sys has 3 phases
1) unlock (s0, SERVO_UNLOCKED
2) time-sync (s1, SERVO_JUMP)
3) freq-sync (s2, SERVO_LOCKED)
Based on the log capture below:
Nov 10 03:49:05 phc2sys: [21956.824] CLOCK_REALTIME phc offset 8 s2
freq +9775 delay 2252
Nov 4 12:50:40 ptp4l: [21957.406] rms 3
On Mon, Nov 08, 2021 at 06:44:28AM -0800, Richard Cochran wrote:
> On Sun, Nov 07, 2021 at 04:22:52PM +0200, Vladimir Oltean wrote:
> > On Sun, Nov 07, 2021 at 04:19:55PM +0200, Vladimir Oltean wrote:
> > > On Sun, Nov 07, 2021 at 05:55:43AM -0800, Richard Cochran wrote:
> > > > On Sun, Nov 07, 202
On Sun, Nov 07, 2021 at 04:22:52PM +0200, Vladimir Oltean wrote:
> On Sun, Nov 07, 2021 at 04:19:55PM +0200, Vladimir Oltean wrote:
> > On Sun, Nov 07, 2021 at 05:55:43AM -0800, Richard Cochran wrote:
> > > On Sun, Nov 07, 2021 at 01:32:59PM +0200, Vladimir Oltean wrote:
> > > > 1. ptp4l in the rol
On Sun, Nov 07, 2021 at 04:19:55PM +0200, Vladimir Oltean wrote:
> On Sun, Nov 07, 2021 at 05:55:43AM -0800, Richard Cochran wrote:
> > On Sun, Nov 07, 2021 at 01:32:59PM +0200, Vladimir Oltean wrote:
> > > 1. ptp4l in the role of a GM appears to listen for GRANDMASTER_SETTINGS_NP
> > >PTP mana
On Sun, Nov 07, 2021 at 05:55:43AM -0800, Richard Cochran wrote:
> On Sun, Nov 07, 2021 at 01:32:59PM +0200, Vladimir Oltean wrote:
> > 1. ptp4l in the role of a GM appears to listen for GRANDMASTER_SETTINGS_NP
> >PTP management messages on the local r/w UDS socket and that's how it
> >upda
On Sun, Nov 07, 2021 at 01:32:59PM +0200, Vladimir Oltean wrote:
> 1. ptp4l in the role of a GM appears to listen for GRANDMASTER_SETTINGS_NP
>PTP management messages on the local r/w UDS socket and that's how it
>updates its ANNOUNCE message contents. Who is supposed to construct and
>
phc2sys sets the CLOCK_TAI offset of the kernel since commit
commit fefd5b4b05039ea0a0770291b12b0eb931079970
Author: Miroslav Lichvar
Date: Wed Jun 18 15:44:49 2014 +0200
Set TAI offset of system clock.
When synchronizing the system clock and the PTP UTC offset is valid and
tracea
> -Original Message-
> From: JP
> Sent: Thursday, August 19, 2021 6:51 AM
> To: linuxptp-users@lists.sourceforge.net
> Subject: [Linuxptp-users] phc2sys quick start
>
> Hi,
>
> Apologies if this has been asked before.
>
> I'm trying to get phc2
Hi,
Apologies if this has been asked before.
I'm trying to get phc2sys to sync CLOCK_REALTIME to a NIC as quickly as
possible. The best I can achieve is something between 50-100ms.
After some experimentation I have come up with this incantation:
phc2sys -s interface_name
We are running ptp4l on our grandmaster clock. It has a ptp device, which the
kernel identifies, which is not attached to a particular interface device. We
use an upstream ICD-GPS-153 receiver to provide 1PPS and timestamps. I wrote
some code for ts2phc to interface with this device. It beha
hi Jake,
Thanks for your response.
Not sure I follow here. You mean BC as in the boundary clock you're
connected to?
>> Yes.
You could possibly filter or average the delay to remove outliers, but I
am not sure how this impacts things. Other experts on this list are
probably better to answer that.
On 4/29/2021 8:04 AM, ramesh t wrote:
> hello Jake,
>
> Did time profiling using time ticks.
> Under the problem condition, observing clock_gettime of interface
> connected to BC is taking more time ticks. This results in phc offset
> jumping to 4 digit value momentarily. Also i'm not sure if r
On 4/28/2021 7:00 PM, ramesh t wrote:
> hi Jake,
>
>> enp104s0f1 phc offset 3 s2 freq -11417 delay 3568
>> enp104s0f1 phc offset -4973 s2 freq -16393 delay 19341* <<> enp104s0f1 phc offset 4977 s2 freq -7934 delay 3594*
>> enp104s0f1 phc offset 1471 s2 freq -
hi Richard,
We have core pinned the ptp4l and phc2sys process to run on non system cores.
Do think chrt is required?
Please suggest.
Thanks for your support.
Regards,Ramesh
On Thursday, April 29, 2021, 08:45:26 PM GMT+5:30, Richard Cochran
wrote:
On Thu, Apr 29, 2021 at 03:04:07PM +000
On Thu, Apr 29, 2021 at 03:04:07PM +, ramesh t via Linuxptp-users wrote:
> Did time profiling using time ticks. Under the problem condition,
> observing clock_gettime of interface connected to BC is taking more
> time ticks. This results in phc offset jumping to 4 digit value
> momentarily. Al
hello Jake,
Did time profiling using time ticks. Under the problem condition, observing
clock_gettime of interface connected to BC is taking more time ticks. This
results in phc offset jumping to 4 digit value momentarily. Also i'm not sure
if reading across numa is triggering this issue.
Pleas
hi Jake,
> enp104s0f1 phc offset 3 s2 freq -11417 delay 3568
> enp104s0f1 phc offset -4973 s2 freq -16393 delay 19341* <<
> enp104s0f1 phc offset 4977 s2 freq -7934 delay 3594*
> enp104s0f1 phc offset 1471 s2 freq -9947 delay 3591*
> enp104s0f1 phc offset
On 4/28/2021 12:01 AM, ramesh t via Linuxptp-users wrote:
> hi,
>
> In our system, we have 3-4 ptp4l services running as master (C1 mode)
> providing clock to external device. Our system is synced using ptp
> support/slave connected to a BC. From the synced slave/support
> interface, phc2sys is
hi,
In our system, we have 3-4 ptp4l services running as master (C1 mode) providing
clock to external device. Our system is synced using ptp support/slave
connected to a BC. From the synced slave/support interface, phc2sys is used to
sync master interface. All the master and slave ptp4l and phc2
hi Richard,
Email in sent folder seems to be fine. But the email received seems to have
become unreadable. I'm re-attaching the email below. I hope this looks fine.
Also, have attached same as text file.
Regards,Ramesh
hello,
Have a testline where ptp4l application is running as master on a ser
On Tue, Mar 23, 2021 at 05:33:39PM +, ramesh t via Linuxptp-users wrote:
> hello,
> Please suggest.
Your mailer has totally mangled the logs, making them unreadable.
Fix that, and then maybe somebody will respond.
Thanks,
Richard
> Regards,Ramesh
> On Tuesday, March 23, 2021, 02:23:06
hello,
Please suggest.
Regards,Ramesh
On Tuesday, March 23, 2021, 02:23:06 PM GMT+5:30, ramesh t via
Linuxptp-users wrote:
hello,
Have a testline where ptp4l application is running as master on a server and is
connected to remote end running ptp as support/slave unit.
When the remote e
hello,
Have a testline where ptp4l application is running as master on a server and is
connected to remote end running ptp as support/slave unit.
When the remote end application is restarted, the interface between ptp master
and support/slave ptp is going down. This is resulting in phc2sys jumpin
On Mon, Jan 18, 2021 at 08:08:58PM +0100, Maheen Iqbal wrote:
> Thanks a lot. Is it possible to reduce the offset of the phc2sys.
Probably not, unless you want to buy special hardware.
Sorry,
Richard
___
Linuxptp-users mailing list
Linuxptp-users@list
Hi,
Thanks a lot. Is it possible to reduce the offset of the phc2sys.
-Maheen
On Sun, Jan 17, 2021 at 10:24 PM Richard Cochran
wrote:
> On Sun, Jan 17, 2021 at 04:51:19PM +0100, Maheen Iqbal wrote:
> > ptp4l[7405.869]: rms 19 max 27 freq -95696 +/- 18 delay -1 +/- 0
> > ptp4l[7406.869]: rms 18
On Sun, Jan 17, 2021 at 04:51:19PM +0100, Maheen Iqbal wrote:
> ptp4l[7405.869]: rms 19 max 27 freq -95696 +/- 18 delay -1 +/- 0
> ptp4l[7406.869]: rms 18 max 29 freq -95715 +/- 13 delay 1 +/- 0
> but when I am running the phc2sys with the below mentioned command the
> offset is around 3 to 4 dig
Hi,
I synchronized the ptp clock with the below mentioned command and it seems
that it is synchronized
sudo /usr/sbin/ptp4l -m -f /etc/linuxptp/ptp4l.conf_as_final
ptp4l[7344.881]: selected /dev/ptp0 as PTP clock
ptp4l[7344.920]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[7344.952]:
On 1/14/2021 11:30 AM, Ankur Sharma wrote:
> Hi Jacob, Linux PTP members,
>
> We saw that we have an e1000e module installed on the systems where we
> are seeing phc2sys offset spikes.
>
The device you listed is using the igb driver module, not e1000e.
> _Output of *lsmod | grep ptp*_
> ptp
Hi Jacob, Linux PTP members,
We saw that we have an e1000e module installed on the systems where we are
seeing phc2sys offset spikes.
*Output of lsmod | grep ptp*
ptp19231 7 igb,e1000e,mlx4_en,mlx5_core
We tried to create the setup in our lab with the above kernel and OS
ver
Hi Jacob,
Here are the additional details you requested:
*ethtool -i eno1 OUTPUT:*
driver: igb
version: 5.6.0-k
firmware-version: 3.25, 0x85cc
expansion-rom-version:
bus-info: :06:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supp
On 1/7/2021 2:58 PM, Ankur Sharma wrote:
> Hi,
>
> We are using PTP4L to synchronize the physical hardware clock on our
> intel interface from the external PTP master. Also we are using PHC2SYS
> to synchronize system clock using the Physical hardware clock on intel
> interface. However, we see
Hi,
We are using PTP4L to synchronize the physical hardware clock on our intel
interface from the external PTP master. Also we are using PHC2SYS to
synchronize system clock using the Physical hardware clock on intel
interface. However, we see that the phc2sys process shows an explosion of
offset a
Yes i can get it working with multiple instances of phc2sys, but was not
sure that was the best way to move forward. Also does any one have
experience using the ptp_kvm module (/dev/ptp_kvm) as a source PHC.
I was looking at the latest devel linuxptp code that has a new program
called "ts2phc"
On Tue, Jul 21, 2020 at 08:43:10PM -0400, nasir via Linuxptp-users wrote:
>
> No. I am passing in both ports to the KVM. The KVM sees three ptpt
> devices. One is using the ptp_kvm module and the other two are the
> mellanox NICS. I am trying to sync the mellanox clocks using ptp_kvm
> as source
ptp device in the
command as its destination deviceSent from my Samsung Galaxy smartphone.
Original message From: Jacob Keller
Date: 7/21/20 7:28 PM (GMT-05:00) To: linuxptp-users@lists.sourceforge.net
Subject: Re: [Linuxptp-users] phc2sys with ptp_kvm and mutiport mellanox NICs
On 7/21/2020 3:24 PM, Hussamuddin Nasir via Linuxptp-users wrote:
> Hello folks,
>
> I am using Mellanox Connect X5 dual port 100G card whose PTP clock
> devices (/dev/ptp0, /dev/ptp1) were synced using ptp4l and phc2sys via a
> PTP Appliance. We now install a KVM on the physical host and se
Hello folks,
I am using Mellanox Connect X5 dual port 100G card whose PTP clock
devices (/dev/ptp0, /dev/ptp1) were synced using ptp4l and phc2sys via a
PTP Appliance. We now install a KVM on the physical host and setup the
Mellanox NIC as pass thru to the KVM. The KVM has the module ptp_kvm
On Mon, Apr 20, 2020 at 07:58:53AM +, Christian Leeb wrote:
> - I'd rather claim that typically all clocks of a SoC are derived from
> a single crystal oscillator. For our TI Sitara based HW this is certainly the
> case.
I can only say, well done! However, most ARM boards I've seen a
sourceforge.net; Henrik Pind ;
Erdahl, Michael
Subject: Re: [Linuxptp-users] phc2sys with REALTIMECLOCK
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you recognize the sender and know the content
is safe.
On Fri, Apr 17, 2020 at 0
On Fri, Apr 17, 2020 at 06:47:57AM +, Christian Leeb wrote:
> ok. So far. But the CLOCK_REALTIME is not added to list of dst clocks! As a
> consequence, CLOCK_REALTIME is not synced anymore.
>
> phc2sys[1530254.251]: eth0 phc offset-89483 s0 freq -9955
> phc2sys[1530256.350]: eth0 phc
Hi,
I have a boundary clock with ports eth0 and pru10:
ptp4l config (most important params shown):
[eth0]
boundary_clock_jbod 1
[pru10]
boundary_clock_jbod 1
GMC is connected to pru10, nothing connected to eth0. I start ptp4l and phc2sys:
ptp4l -f
phc2sys -arm
Everything goes well:
phc2sys[
> -Original Message-
> From: Richard Cochran
> Sent: Friday, December 06, 2019 8:25 PM
> To: Hutchinson, Brian
> Cc: Keller, Jacob E ; linuxptp-
> us...@lists.sourceforge.net
> Subject: Re: [Linuxptp-users] phc2sys stuck ... "Waiting for ptp4l..." and pm
On Fri, Dec 06, 2019 at 10:22:07PM +, Hutchinson, Brian via Linuxptp-users
wrote:
> I've been "aware" of systemd for a long time (and the holy wars
> around it) but to date have always used sysV init on embedded
> devices so this is first project with systemd so I have a bit of a
> learning c
On Fri, Dec 06, 2019 at 07:58:03PM +, Hutchinson, Brian via Linuxptp-users
wrote:
> It all works now! You are the man!!!
+1
Nice call, Jake! I was scratching my head on this one...
Thanks,
Richard
___
Linuxptp-users mailing list
Linuxptp-user
> -Original Message-
> From: Keller, Jacob E
> Sent: Friday, December 6, 2019 5:15 PM
> To: Hutchinson, Brian (US) ; linuxptp-
> us...@lists.sourceforge.net
> Subject: RE: phc2sys stuck ... "Waiting for ptp4l..." and pmc returns nothing
>
> > -Original Message-
> > From: Hutchinso
> -Original Message-
> From: Hutchinson, Brian
> Sent: Friday, December 06, 2019 2:04 PM
> To: Keller, Jacob E ; linuxptp-
> us...@lists.sourceforge.net
> Subject: RE: phc2sys stuck ... "Waiting for ptp4l..." and pmc returns nothing
>
> > -Original Message-
> > From: Keller, Jacob
> -Original Message-
> From: Keller, Jacob E
> Sent: Friday, December 6, 2019 4:57 PM
> To: Hutchinson, Brian (US) ; linuxptp-
> us...@lists.sourceforge.net
> Subject: RE: phc2sys stuck ... "Waiting for ptp4l..." and pmc returns nothing
>
> > -Original Message-
> > From: Hutchinso
> -Original Message-
> From: Hutchinson, Brian
> Sent: Friday, December 06, 2019 1:49 PM
> To: Keller, Jacob E ; linuxptp-
> us...@lists.sourceforge.net
> Subject: RE: phc2sys stuck ... "Waiting for ptp4l..." and pmc returns nothing
>
>
> >
> > Out of curiosity, what version of linuxptp
>
> Out of curiosity, what version of linuxptp are you using? it looks like the -f
> option is documented on master.
>
> Thanks,
> Jake
>
I started out with whatever was in Yocto Sumo (2.5) release (I think it was
linuxptp 1.8) but quickly realized that it didn't support the G.8275.2 profile
nal Message-
> > > From: Hutchinson, Brian via Linuxptp-users > > us...@lists.sourceforge.net>
> > > Sent: Friday, December 06, 2019 8:32 AM
> > > To: linuxptp-users@lists.sourceforge.net
> > > Subject: [Linuxptp-users] phc2sys stuck ... "Waiting for
gt; > > From: Hutchinson, Brian via Linuxptp-users > > us...@lists.sourceforge.net>
> > > Sent: Friday, December 06, 2019 8:32 AM
> > > To: linuxptp-users@lists.sourceforge.net
> > > Subject: [Linuxptp-users] phc2sys stuck ... "Waiting for ptp4l...&quo
tchinson, Brian via Linuxptp-users > us...@lists.sourceforge.net>
> > Sent: Friday, December 06, 2019 8:32 AM
> > To: linuxptp-users@lists.sourceforge.net
> > Subject: [Linuxptp-users] phc2sys stuck ... "Waiting for ptp4l..." and
> > pmc returns nothing
> &g
Hi,
So I think I have ptp4l running ok:
ethtool -T eth0
Time stamping parameters for eth0:
Capabilities:
hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE)
software-transmit (SOF_TIMESTAMPING_TX_SOFTWARE)
hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE)
EALTIME -c eno2 -w"
[root@localhost ~]#
Best Regards,
Ganganath
-Original Message-
From: Miroslav Lichvar
Sent: Wednesday, October 2, 2019 04:15 PM
To: gangana...@lankabell.net
Cc: linuxptp-users@lists.sourceforge.net
Subject: Re: [Linuxptp-users] ph
On Wed, Oct 02, 2019 at 04:02:44PM +0530, gangana...@lankabell.net wrote:
> [root@localhost /]# cat /etc/timemaster.conf
> # Configuration file for timemaster
>
> [ptp4l.conf]
> includefile /etc/ptp4l.conf
Oh, I see.
ptp4l doesn't support an "includefile" option. The content of
/etc/ptp4l.co
1 - 100 of 139 matches
Mail list logo
