Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-30 Thread Aditya Venu via Linuxptp-users
Cloned the latest git repo and tried the same. Getting single digit ns offset, frequency with some values and clock servo to locked state. Thanks for your time :) -Aditya On Mon, Jan 23, 2023 at 4:41 PM Miroslav Lichvar wrote: > On Mon, Jan 23, 2023 at 04:36:11PM +0530, Aditya Venu wrote: > >

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-23 Thread Aditya Venu via Linuxptp-users
*It seems the first clock step is disabled. Did you changefirst_step_threshold in your config?* It is set to the default value itself(0.2). On Mon, Jan 23, 2023 at 4:31 PM Miroslav Lichvar wrote: > On Mon, Jan 23, 2023 at 03:54:27PM +0530, Aditya Venu wrote: > > *Does it work if you enable

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-23 Thread Miroslav Lichvar
On Mon, Jan 23, 2023 at 04:36:11PM +0530, Aditya Venu wrote: > *It seems the first clock step is disabled. Did you > changefirst_step_threshold in your config?* > > It is set to the default value itself(0.2). I have no explanation. Sorry. -- Miroslav Lichvar

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-23 Thread Miroslav Lichvar
On Mon, Jan 23, 2023 at 03:54:27PM +0530, Aditya Venu wrote: > *Does it work if you enable SW timestamping on the client?* > > I'm pasting the output below with HW timestamping at master and SW > timestamping on client: It seems the first clock step is disabled. Did you change

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-23 Thread Aditya Venu via Linuxptp-users
*Does it work if you enable SW timestamping on the client?* I'm pasting the output below with HW timestamping at master and SW timestamping on client: *ptp4l[641.740]: port 1: INITIALIZING to LISTENING on INIT_COMPLETEptp4l[641.740]: port 0: INITIALIZING to LISTENING on

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-23 Thread Miroslav Lichvar
On Mon, Jan 23, 2023 at 11:54:25AM +0530, Aditya Venu wrote: > Any suggestions to the above issue please?! I don't see anything wrong in the phc2ctl output, but your ptp4l output shows frequency stuck at -1, which makes no sense to me. Does it work if you enable SW timestamping on client? What

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-22 Thread Aditya Venu via Linuxptp-users
Hi Miroslav, Any suggestions to the above issue please?! On Tue, Jan 17, 2023 at 4:21 PM Aditya Venu wrote: > Hi Miroslav, > > *Below is the output for master*: > > > > > > > > > *sudo ./phc_ctl /dev/ptp2phc_ctl[14216.300]: capabilities: 9 > maximum frequency adjustment (ppb) 0

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-17 Thread Aditya Venu via Linuxptp-users
Hi Miroslav, *Below is the output for master*: *sudo ./phc_ctl /dev/ptp2phc_ctl[14216.300]: capabilities: 9 maximum frequency adjustment (ppb) 0 programable alarms 0 external time stamp channels 0 programmable periodic signals doesn't have pulse per second support* *And this

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-17 Thread Miroslav Lichvar
On Tue, Jan 17, 2023 at 03:46:29PM +0530, Aditya Venu via Linuxptp-users wrote: > Corrected step_threshold to 0 and observed that slave's servo state going > to locked state. > > But the offset is continuously increasing.. It might be a driver issue. What does phc_ctl /dev/ptp0 (or the

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-17 Thread Aditya Venu via Linuxptp-users
Hi Richard, Corrected step_threshold to 0 and observed that slave's servo state going to locked state. But the offset is continuously increasing.. ptp4l[12074.007]: master offset -31076 s2 freq -1 path delay 4145 ptp4l[12075.008]: master offset -46783 s2 freq -1 path delay

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-17 Thread Richard Cochran
On Fri, Jan 13, 2023 at 12:32:21PM +0530, Aditya Venu via Linuxptp-users wrote: > d) I'm using default config files for both master and slave(attaching them > for reference) You are NOT using the default configuration. You changed step_threshold from the default of zero. This is the reason for

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-16 Thread Miroslav Lichvar
On Mon, Jan 16, 2023 at 03:40:20PM +0530, Aditya Venu wrote: > Hi Miroslav, > > Attaching the slave and master's config files below. Your config sets step_threshold to 2 microseconds, which is less than the offsets measured by the client and causes it to constantly step. Such a poor performance

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-16 Thread Aditya Venu via Linuxptp-users
Hi Miroslav, Attaching the slave and master's config files below. On Mon, Jan 16, 2023 at 3:38 PM Miroslav Lichvar wrote: > On Mon, Jan 16, 2023 at 12:17:33PM +0530, Aditya Venu via Linuxptp-users > wrote: > > Hi All, > > In other words, what could be the reason for slave's servo clock state >

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-16 Thread Miroslav Lichvar
On Mon, Jan 16, 2023 at 12:17:33PM +0530, Aditya Venu via Linuxptp-users wrote: > Hi All, > In other words, what could be the reason for slave's servo clock state not > going to locked state? Clock stepping would be one example. > Literally stuck at this point. Any inputs will help me in setting

Re: [Linuxptp-users] Slave's clock servo not going to locked state

2023-01-15 Thread Aditya Venu via Linuxptp-users
Hi All, In other words, what could be the reason for slave's servo clock state not going to locked state? Literally stuck at this point. Any inputs will help me in setting the direction for debugging. -Aditya On Fri, Jan 13, 2023 at 12:32 PM Aditya Venu wrote: > Hi fellow linuxptp users, > > I