Hi Miroslav,
We were following one issue, which we are now sure that it is not because of
the changes submitted.
Your changes are working fine for us and we are not seeing any clock check
prints.
Thanks,
Amar B S
> -Original Message-
> From: Amar Subramanyam
> Sent: 03 June 2021 18:47
Hi Miroslav,
Please find our response inline.
Thanks,
Amar B S
> -Original Message-
> From: Miroslav Lichvar [mailto:mlich...@redhat.com]
> Sent: 31 May 2021 14:38
> To: linuxptp-devel@lists.sourceforge.net
> Subject: [Linuxptp-devel] [PATCH v3 5/5] clockcheck: Increase minimum
>
Hi Miroslav,
Please find our response inline.
Thanks,
Amar B S
> -Original Message-
> From: Miroslav Lichvar [mailto:mlich...@redhat.com]
> Sent: 27 May 2021 15:14
> To: Amar Subramanyam
> Cc: linuxptp-devel@lists.sourceforge.net
> Subject: Re: [PATCH v2 3/3] port: Don't check
Hi Miroslav,
I am afraid, the patches that was intended to fix the reported issue doesn't do
so. The issue that we reported was not due to timestamps from non-slave port
being compared in jbod mode. But due to mono_interval (CLOCK_MONOTIC interval
b/w two successive calls to
The port other than SLAVE (LISTENING port) prints an error
"port 1: master state recommended in slave only mode
ptp4l[1205469.356]: port 1: defaultDS.priority1 probably misconfigured"
for every ANNOUNCE RECEIPT Timeout.
This log is printed when the event EV_RS_MASTER is thrown
in clientOnly mode.
The LISTENING port prints continuously
"selected best master clock 00..03
updating UTC offset to 37"
We limited the log such that now it prints only when there is a
change in the best-master clock.
Signed-off-by: Amar Subramanyam
Signed-off-by: Karthikkumar Valoor
Signed-off-by:
The port other than SLAVE (LISTENING port) prints an error
"port 1: master state recommended in slave only mode
ptp4l[1205469.356]: port 1: defaultDS.priority1 probably misconfigured"
for every ANNOUNCE RECEIPT Timeout.
This log is printed when the event EV_RS_MASTER is thrown
in clientOnly mode.
The LISTENING port prints continuously
"selected best master clock 00..03
updating UTC offset to 37"
We limited the log such that now it prints only when there is a
change in the best-master clock.
Signed-off-by: Amar Subramanyam
Signed-off-by: Karthikkumar Valoor
Signed-off-by:
e sure the
> content is safe. You will never be asked to reset your Altiostar password via
> email.
>
>
> On Mon, May 17, 2021 at 10:02:59AM +0300, Amar Subramanyam via Linuxptp-
> devel wrote:
> > This patch addresses the following issues when ptp4l is run on
> > m
This patch addresses the following issues when ptp4l is run on multiple ports
with jbod and client only mode (i.e. clientOnly=1 and boundary_clock_jbod=1):-
1.The LISTENING port prints continuously
"selected best master clock 00..03
updating UTC offset to 37"
the
content is safe. You will never be asked to reset your Altiostar password via
email.
On Tue, May 11, 2021 at 02:16:04PM +, Amar Subramanyam via Linuxptp-devel
wrote:
>> What happens here exactly is, due to the continuous triggering of
>> BMCA, the value of mono_interval (
the
content is safe. You will never be asked to reset your Altiostar password via
email.
On Tue, May 11, 2021 at 02:16:04PM +, Amar Subramanyam via Linuxptp-devel
wrote:
>> What happens here exactly is, due to the continuous triggering of
>> BMCA, the value of mono_interval (
Hi Miroslav Lichvar,
Thanks for your review. Please find our comments inline.
Thanks,
Amar B S
-Original Message-
From: Miroslav Lichvar [mailto:mlich...@redhat.com]
Sent: 10 May 2021 16:58
To: Amar Subramanyam
Cc: linuxptp-devel@lists.sourceforge.net; Ramana Reddy ;
Karthikkumar
Altiostar password via
email.
On Tue, May 04, 2021 at 01:51:24PM +0300, Amar Subramanyam via Linuxptp-devel
wrote:
> This patch addresses the following issues when ptp4l is ran on
> multiple ports with jbod and client only mode (i.e clientOnly=1 and
> boundary_clock_jbod=1
Hi,
The commands we used for testing below issues are:
For 8275.1 profile:
ptp4l -f config_ptp_8275_1.conf -i sriov1 -i sriov0 -H -m 2 --boundary_clock=1
--slaveOnly=1
phc2sys -a -r -m -R 16 -n 24
For 8275.2 profile:
ptp4l -f config_ptp_8275_2.conf -i sriov1 -i sriov0 -H -m 4
Hi,
Based on your comments, we are pulling back this change.
For the issues we saw with the clientOnly=1 and boundary_clock_jbod=1, we have
sent out a new patch fixing them alone.
Thank you for your feedback.
Thanks,
Amar B S
-Original Message-
From: Ramana Reddy
Sent: 28 April 2021
This patch addresses the following issues when ptp4l is ran on multiple ports
with jbod and client only mode (i.e clientOnly=1 and boundary_clock_jbod=1):-
1.SYNCHRONIZATION FAULT occurs at every ANNOUNCE RECEIPT Timeout on LISTENING
port,
which leads to PTP port state of SLAVE port to flap
u recognize the sender and you are sure the
content is safe. You will never be asked to reset your Altiostar password via
email.
On Thu, Apr 15, 2021 at 11:16:00AM +0300, Amar Subramanyam via Linuxptp-devel
wrote:
> This change brings slave clock jbod feature which allows ptp4l to work as a
>
This change brings slave clock jbod feature which allows ptp4l to work as a
Ordinary Subordinate/Slave clock using "just a bunch of devices" that are not
synchronized to each other but a collection of clocks synchronized by an
external
source.The best master will be decided by BMCA among the
19 matches
Mail list logo
