Thanks George Hansel.
On Tuesday, November 21, 2023 at 11:55:13 AM GMT+5:30, George Hansel
wrote:
IERS is the leap second authority:
https://hpiers.obspm.fr/iers/bul/bulc/ntp/leap-seconds.list
On Mon, Nov 20, 2023 at 9:34 PM ramesh t via Linuxptp-users
wrote:
> hello,
>
> D
hello,
Do we have latest leapsecond file available for use? Current one is expiring on
December 28th 2023.
https://www.ietf.org/timezones/data/leap-seconds.list (not working)
https://data.iana.org/time-zones/tzdb/leapseconds (File expires on: 28
December 2023)
Please suggest.
regards,
Ramesh
Hello,
Any idea when is the next planned release for ptp4l?
We are currently using 3.1.1 release, but we need fixes present in the current
base code.
Is it ok to take these missing fixes and merge into 3.1.1 local code base?
For Example:
commit e8dc364f9fd5fbdac5d2c5e433f28e9da0028d49
Hi,
Observed a issue where PTP is running is fine with single digit rms value. Due
to error in switch/GM, there is wrong time update towards the ptp4l. This
results in wrong update on PHC time on the NIC. PHC time seems to be set to
1970 or 2070 timeframe may be due to error condition in ptp4l.
Thanks for your response.
This issue is observed on NIC PHC and apart from ptp4l no other process will
update the NIC PHC in this case.
Will process (ptp4l) scheduling have an impact on this?
regards,
Ramesh
On Wednesday, August 3, 2022 at 12:03:10 PM GMT+5:30, Miroslav Lichvar
wrote:
Hello,
Observing once in while clockcheck error.
Any suggestion why this could happen??
Please suggest.
regards,
Ramesh
___
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
Hello Miroslav Lichvar,
Ptp4l instance is running fine and only one instance is running. But phc2sys is
getting struck.
RegardsRamesh
On Thursday, July 14, 2022 at 06:05:32 PM GMT+5:30, Miroslav Lichvar
wrote:
On Tue, Jul 12, 2022 at 05:36:42PM +, ramesh t via Linuxptp-devel wrote:
hi,
Please suggest, we are using linuxptp 2.0 version.
regards,
Ramesh
- Forwarded Message -
From: ramesh t
To: Aya Levin via Linuxptp-devel ;
Linuxptp-users ; Richard Cochran
Sent: Tuesday, July 12, 2022 at 11:06:42 PM GMT+5:30
Subject: phc2sys struck on "waiting for ptp4l"
Hello
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
,
Ramesh
On Thursday, March 17, 2022, 05:23:15 PM GMT+5:30, ramesh t via Linuxptp-users
wrote:
Hello Miroslav Lichvar,
Please find the value of ptp config as per 8275.1 standards.
logAnnounceInterval -3
announceReceiptTimeout 3
We can't increase beyond the above values.
regards,
R
, Mar 16, 2022 at 06:23:23PM +0000, ramesh t via Linuxptp-users wrote:
> ptp4l: [704774.649] port 1: announce timeout
> ptp4l: [704774.649] port 1: SLAVE to MASTER on
> ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
>
> On debugging further, when port 2 is configured for down state, we
Hello,
Have ptp4l running in BC mode providing clock to connected TestUnits (via port
2) and syncing clock from BC/GM (via port 1)
Did few more iterations of testing (ptp4l in BC mode) by doing ifconfig down.
Observing PTP4l reporting below error in port 1 connected to BC/GM
ptp4l: [704774.649
hi Richard,
> Feb 7 09:35:20 ptp4l: [610991.536] port 2: send sync failed
> Feb 7 09:35:20 ptp4l: [610991.536] port 2: MASTER to FAULTY on
> FAULT_DETECTED (FT_UNSPECIFIED)
> Feb 7 09:35:20 ptp4l: [610991.557] port 2: link down
> Feb 7 09:35:20 ptp4l: [610991.557] port 2: received link status
hi Richard,
Did few more iterations of testing (ptp4l in BC mode) by resetting TestUnit.
Still observing "send sync error" with txtimeout of 100ms.
Question:
1) ptp4l is running in BC mode providing clock to other connected TestUnits and
syncing clock from another BC/GM.
But in the below ca
+5:30, Miroslav Lichvar
wrote:
On Thu, Jan 20, 2022 at 06:11:57PM +, ramesh t via Linuxptp-users wrote:
> In clockcheck_sample function, we should depend on CLOCK_MONOTONIC to decide
> if its getting called more frequency than a second. But we also check on
> remote time:
hi,
ptp4l (2.0) is struck due to below error:
ptp4l: [97860.312] selected /dev/ptp14 as PTP clock
ptp4l: [97860.340] port 1: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l: [97860.340] PS_LISTENING: port_e2e_transition
ptp4l: [97860.340] port 0: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l
hi Richard,
In phc2sys code, for default config phc_interval, update_clock is called once
in a second based CLOCK_MONOTONIC timer. With sanity_check enabled,
clockcheck_sample is also called.
In clockcheck_sample function, we should depend on CLOCK_MONOTONIC to decide if
its getting called mo
hi Richard,
With Step 1, it seems to be working fine, will try few more variations and
check.
Thank you for your help.
But have few questions:
Patches provided doesn't seems to have any relation with error "timed out while
polling for tx timestamp" which occurred while transmitting Sync packets
hi Richard,
Issue:
Running ptp4l in BC mode. Have connected one NIC port to BC/GM and another NIC
port to testing unit (TU).
On resetting of the testing unit, temporarily observing ptp4l going into FAULTY
state though it shouldn't be impacted due to reset of testing unit.
On debugged this issu
hi Richard,
In BC mode, Port 2 is connected to TestingUnit and Port 1 is connected to BC/GM
unit.
Observing below behavior on reboot of TestingUnit, Port 1 is going from SLAVE
to UNCALIBRATED, which is not correct.
Below are the ptp4l and phc2sys command used.
ptp4l -2 -A -i enp175s0f1 -i enp95
hi Richard,
>>Why does BC/GM port go to PS_FAULTY? Link down?
Sorry, could be issues with my side of the changes.
Tried looking into code to find out if there is any variable in port or clock
struct which will tell if the interface is acting as client (slave) or server
side of PTP.
Please sugg
hi Richard,
>>Using option -a will automatically time sync all the PHC devices in the
>>system.
>>Is there a way to sync only those interface which are part of BC
>>configuration (port connected to Testing Unit)??
Please ignore above question.
Repeated the testing with phc2sys automatic mode (
hi Richard,
Using option -a will automatically time sync all the PHC devices in the system.
Is there a way to sync only those interface which are part of BC configuration
(port connected to Testing Unit)??
Using -a option, will it help to solve this issue seen? Because ptp4l is going
into PS_FA
hi,
Running ptp4l in BC mode, with clock_type set to BC and boundary_clock_jbod set
to 1. Have connected one NIC port to BC/GM and another NIC port to testing unit
(TU). Following is the ptp4l command.
./ptp4l -2 -A -w -i -i -f
/etc/ptp4l_bc.c
In BC mode, ptp4l getting clock from BC/GM and
(Nov 9 21.52.19
+ 21408 secs (5 hour + 56 minutes) around Nov 10 3:49.
Please suggest.
regards,
Ramesh
On Thursday, November 11, 2021, 10:26:28 PM GMT+5:30, ramesh t via
Linuxptp-users wrote:
hi Richard,
Verified on the nodes where the problem re-occurred after almost a week using
hi,
step_threshold default config is 0.0. Hence it was not doing time-sync when
moving from s0 to s2 via s1. After changing value of step_threshold, time-sync
is happening.
Question: Any reason as to why step_threshold is set 0.0? What should be the
proper value?
Also first_step_threshold valu
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
hi Richard,
Verified on the nodes where the problem re-occurred after almost a week using
phc_ctl. NIC phc time was fine. But only system time had changed.
Also as suggested was running a script to capture phc_ctl periodically, but the
issue didn't happen on those node. Even nodes running ptp2.0
hi,
Rms value of PTP slave/support is taking longer duration (1-2 hours) to come
back to single/two digit value.
Oct 29 01:21:37 ptp4l_slave: [2115639.889] handle_state_decision_event
PS_LISTENING
Oct 29 01:21:37 ptp4l_slave: [2115640.178] selected best master clock
28affd.fffe.e5de3f
Oct 29 0
2021
x86_64 GNU/Linux
Please suggest.
regards,
Ramesh
On Wednesday, November 3, 2021, 01:38:01 AM GMT+5:30, Keller, Jacob E
wrote:
On 11/2/2021 2:55 AM, ramesh t via Linuxptp-users wrote:
> hi,
>
> We are using Dell Supermicro 6212 with Intel E810 NIC card. And system was
>
Thanks Richard.
Will trigger a script to capture the output.
regards,
Ramesh
On Tuesday, November 2, 2021, 10:02:01 PM GMT+5:30, Richard Cochran
wrote:
On Tue, Nov 02, 2021 at 03:32:04PM +, ramesh t wrote:
> hi,
>
> Any suggestion for the below mentioned issue? Please let me kno
hi,
Is there a way to find all the code commit between ptp 2.0 and ptp 3.0.
Please suggest.
regards,
Ramesh
___
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
hi,
Any suggestion for the below mentioned issue? Please let me know.
regards,
Ramesh
On Tuesday, November 2, 2021, 03:27:54 PM GMT+5:30, ramesh t via Linuxptp-users
wrote:
hi,
We are using Dell Supermicro 6212 with Intel E810 NIC card. And system was
stable with ptp2.0 load.
We have
hi,
We are using Dell Supermicro 6212 with Intel E810 NIC card. And system was
stable with ptp2.0 load.
We have disable ntpd, chronyd, systemd-timesyncd and systemd-timedated
services.
regards,
Ramesh
On Tuesday, November 2, 2021, 02:37:27 PM GMT+5:30, Miroslav Lichvar
wrote:
On Tue,
hi,
We are using ptp3.0 version in C3 mode. Both ptp4l and phc2sys (to sync system
clock) are running fine.
Ptp4l rms value is in single digits and we see a sudden jump in phc offset as
captured below resulting in date change.
Oct 26 19:15:48 phc2sys_slave: [1177711.923] CLOCK_REALTIME phc off
hi,
We are planning to upgrade ptp4l to latest version (3.1.1), had few questions
1) From which release onwards of ptp4l IEEE 1588-2019 is supported?
2) Is IEEE 1588-2019 backward compatible with switches and NIC supporting IEEE
1588-2008 version?
3) After moving to latest version 3.1.1, was the
hi,
Debugging a ptp4l issue, observed its getting blocked while writing into
/var/log/messages file. Blocking of ptp4l can vary from few minutes to forever.
Blocking could be related to system buffer or sockets issue or remote peer is
busy.
But ptp4l blocked for writing messages and not updati
pport on this issue.
>
> Regards,
> Ramesh
> On Thursday, April 29, 2021, 07:33:49 AM GMT+5:30, ramesh t via
> Linuxptp-users wrote:
___
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
+, 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. Also i'm not sure if re
issue.
Please suggest a way to fix in the phc2sys offset code?1) Should we prevent
update on phc2sys value if there is momentarily jump?
Please suggest.
Thanks for your support on this issue.
Regards,Ramesh On Thursday, April 29, 2021, 07:33:49 AM GMT+5:30, ramesh t
via Linuxptp-users wrote:
c -
tdst1.tv_nsec;This interval maps to delay.
Please suggest.
Regards,Ramesh
On Thursday, April 29, 2021, 04:05:34 AM GMT+5:30, Jacob Keller
wrote:
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
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
esh 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 PM GMT+5:30, ramesh t via
>L
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
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
hi,
Observing below error once in while in the ptp log messages:
Feb 1 15:37:48 k8s-worker-0 phc2sys: phc2sys[543830.623]: CLOCK_REALTIME phc
offset -13 s2 freq -81987 delay 527Feb 1 15:37:48 k8s-worker-0
phc2sys: phc2sys[543830.623]: /dev/ptp7 phc offset 3 s2 freq +1312
de
doing weird stuff, but I reformatted the message to
make it legible ...
On Fri, Dec 11, 2020 at 10:55:04AM +, ramesh t via Linuxptp-users wrote:
> Have connected two servers (Intel NIC: XXV710) with 10Gige
> interface. One server is running PTP master instance and another
> server is ru
hello,
Have connected two servers (Intel NIC: XXV710) with 10Gige interface. One
server is running PTP master instance and another server is running PTP slave
instance. With no data traffic the rms and path delay seems to be stable.
ptp4l[6406.152]: rms 4 max 9 freq +6569 +/- 6 delay 5
48 matches
Mail list logo
