On Fri, Nov 25, 2022 at 02:43:34PM +0530, Amar B S wrote:
> Hi Miroslav,
>
> Do you see any problem in the trace?
The kernel doesn't seem to be responding with any vclocks to
the ETHTOOL_MSG_PHC_VCLOCKS_GET request for srio2.
Is directory /sys/class/ptp/ptp2/ptp8 present on the system? That
Hi Miroslav,
Do you see any problem in the trace?
Thanks
Amar
On Thu, Nov 24, 2022 at 9:59 AM Amar B S wrote:
> Hi,
>
> I have attached the strace log.
>
> Thanks,
> Amar B S
>
> On Wed, Nov 23, 2022 at 8:00 PM Miroslav Lichvar
> wrote:
>
>> On Wed, Nov 23, 2022 at 07:53:32PM +0530, Amar B S
Hi,
I have attached the strace log.
Thanks,
Amar B S
On Wed, Nov 23, 2022 at 8:00 PM Miroslav Lichvar
wrote:
> On Wed, Nov 23, 2022 at 07:53:32PM +0530, Amar B S wrote:
> > This part of the code checks if VPHC is present using NetLink messages,
> it
> > seems like we are not getting the
On Wed, Nov 23, 2022 at 07:53:32PM +0530, Amar B S wrote:
> This part of the code checks if VPHC is present using NetLink messages, it
> seems like we are not getting the expected response, hence failing to
> detect the VPHC.
Can you please run ptp4l in strace and post the output?
--
Miroslav
*} else if (p->phc_index >= 0 && *
* p->phc_index != interface_phc_index(interface)) {*
* if (rtnl_iface_has_vclock(interface_name(interface),*
* p->phc_index)) {*
*pr_info("%s: /dev/ptp%d is virtual clock",*
*p->log_name,
Hi Miroslav,
I checked your patch and tried it, but in my setup, it's failing well
before the part of the code you have changed.
The function "*rtnl_iface_has_vclock*" determines whether the given clock
is VPHC which is failing and hence it exits during the Initialization phase
itself.
On Wed, Nov 23, 2022 at 01:04:42PM +0530, Amar B S wrote:
> Hi Miroslav,
>
> May I know on which kernel version, this was working fine?
It turned out to be a linuxptp issue. See my patch on -devel.
--
Miroslav Lichvar
___
Linuxptp-users mailing
Hi Miroslav,
May I know on which kernel version, this was working fine?
Thanks,
Amar
On Mon, Nov 21, 2022 at 3:27 PM Miroslav Lichvar
wrote:
> On Mon, Nov 21, 2022 at 03:06:44PM +0530, Amar B S wrote:
> > Hi Miroslav,
> >
> > The code was built on a dev system and I copied binaries into to
On Mon, Nov 21, 2022 at 03:06:44PM +0530, Amar B S wrote:
> Hi Miroslav,
>
> The code was built on a dev system and I copied binaries into to test
> system. Is it required to build on the test system where kernel support is
> present ?
Actually, it shouldn't matter where it is built as linuxptp
Hi Miroslav,
The code was built on a dev system and I copied binaries into to test
system. Is it required to build on the test system where kernel support is
present ?
Thanks,
Amar
On Mon, Nov 21, 2022 at 1:18 PM Miroslav Lichvar
wrote:
> On Mon, Nov 21, 2022 at 12:13:05PM +0530, Amar B S
On Mon, Nov 21, 2022 at 12:13:05PM +0530, Amar B S wrote:
> When I run ptp4l it's unable to detect the virtual clock and prints out the
> error “phc device mismatch”.
> After reading through the code I see that *“rtnl_iface_has_vclock” *is
> failing to detect the virtual clock. Can you please
Hi LinuxPtp Community,
We are trying to run multiple instances of ptp4l on the same interface
using the virtual PHC clock feature that was submitted to linuxptp.
We are using the master branch of linuxPTP and kernel 6.0.8. I have created
virtual clocks using the command “echo 2 >
12 matches
Mail list logo
