static int ts2phc_slave_event(struct ts2phc_slave *slave,
break;
case SERVO_LOCKED:
case SERVO_LOCKED_STABLE:
+if (llabs(offset) < 500) {
+slave->current_offset_skip_count = 0;
+}
+
clockadj_set_freq(slave->clk, -adj);
break;
}
--
2.20.1
On Friday, Nov
PORT_ITEM_INT("max_phc_update_skip_cnt", 120, 0, 14400),
};
static struct unicast_master_table *current_uc_mtab;
--
2.20.1
On Friday, October 20, 2023 at 07:34:45 AM GMT+5:30, ramesh t
wrote:
hi,
Please provide review comments and help in closure of the issue.
regards,
hi,
Please provide review comments and help in closure of the issue.
regards,
Ramesh
On Thursday, October 12, 2023 at 10:22:02 PM GMT+5:30, ramesh t via
Linuxptp-devel wrote:
From bbb7479baba6fe58a02aee0898777cbdb0c9005b Mon Sep 17 00:00:00 2001
From: Ramesh Gowda
Date: Thu, 12 Oct 2023
>From bbb7479baba6fe58a02aee0898777cbdb0c9005b Mon Sep 17 00:00:00 2001
From: Ramesh Gowda
Date: Thu, 12 Oct 2023 15:26:27 +0530
Subject: [PATCH] Problem: Under GNSS error condition/fluctuation, ts2phc
updating 1sec time into PHC resulting in wrong time. This issue of 1sec jump
is seen
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
Hello,
Observing once in while clockcheck error.
Any suggestion why this could happen??
Please suggest.
regards,
Ramesh
___
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
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,
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
Hello Miroslav Lichvar,
Tried as suggested, observed below error.
ptp4l: [806352.926] clockcheck: clock jumped backward or running slower than
expected!
So set sanity_freq_limit to 0, but still observing errors:
ptp4l: [806913.536] timed out while polling for tx timestamp
ptp4l: [806913.536]
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,
Ramesh
On Thursday, March 17, 2022, 04:10:38 PM GMT+5:30, Miroslav Lichvar
wrote:
On Wed, Mar
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:
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
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
hi Miroslav Lichvar,
You are correct, "the timestamp checked in the clockcheck code should always be
a timestamp of the clock synchronized by phc2sys"
In this case, we have connected testUnit to interface A. Interface A is
providing clock to testUnit (with ptp4l in BC mode) and time is
clockcheck_sample again mono_interval may be a higher value, resulting in
variation of min and max freq_offset calculation.
Can you please check this and suggest.
regards,
Ramesh
On Tuesday, January 18, 2022, 11:10:22 PM GMT+5:30, ramesh t via Linuxptp-devel
wrote:
hi Richard,
With
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
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
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
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
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
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
hi Jake, Richard,
Observed issue with ptp 2.0 also. But based on below logs.
Nov 10 03:49:04 ptp4l: [21956.414] rms 3 max 6 freq +2783 +/- 5 delay
85 +/- 1
Nov 10 03:49:05 phc2sys: [21956.824] CLOCK_REALTIME phc offset 8 s2
freq +9775 delay 2252
Nov 4 12:50:40 ptp4l:
value is set to 20 microseconds.
Please suggest.
regards,
Ramesh
On Tuesday, November 23, 2021, 12:00:53 AM GMT+5:30, ramesh t via
Linuxptp-devel wrote:
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
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
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
Hello Jake,
Please find the requested info below.
NIC driver:
driver: ice
version: 1.3.2
firmware-version: 2.30 0x80006c8d 1.2877.0
Kernel version:
uname -a
Linux cyswy002r-mvnr-p004-sdlas00222a-mv-du001-55d64d7457-dmp8s
4.19.177-rt72-2.ph3-rt #1-photon SMP PREEMPT RT Fri Mar 5 02:22:24 UTC
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
hi,
Is there a way to find all the code commit between ptp 2.0 and ptp 3.0.
Please suggest.
regards,
Ramesh
___
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
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, Nov 02, 2021 at 09:02:19AM +, ramesh t via Linuxptp-devel wrote:
> hi,
>
> We are using ptp3.0 version i
, Nov 02, 2021 at 09:02:19AM +, ramesh t via Linuxptp-devel wrote:
> 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
> cap
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
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
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
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.
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
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.
39 matches
Mail list logo
