| Re: [chrony-users] Chrony on CM4 |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Chrony on CM4
- From: James Clark <jjc@xxxxxxxxxx>
- Date: Tue, 5 Sep 2023 13:29:48 +0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jclark-com.20230601.gappssmtp.com; s=20230601; t=1693895399; x=1694500199; darn=chrony.tuxfamily.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=o5AjLXWu7BIlIDSGcRCE1tjvxpi44X5JYEkvBjzu1IY=; b=EM71nITJqNrYRGCZkJIzoTl0O+daIzdR2FzBJXxkpp2CapGdPibn1S+uO128jj7/xb uSGJzDt2KfL8qv1pd29mRRaUlj7krOYvVHYnFEhL94f+AItgIbiAggsYl1v2HwRnjs3o 5FT/AUJxlPVlesGyvGYlCZ7AXHxaKcD9cn4mfamUEtqFTAWyXMbUbDIYMGUVToYC9iP8 KSp1D5G3BgGx5avUaxW2VPxIR+e4Qq7kPmssD4vDTe0tCD0bvn3yn2lRSc2P6J3BK+y7 WJv3STtxXjm4t/hqihw1z5XbONgx58SvJxW6FEY62lu4HlBMTqbFr0ghAlCL+pfBiMI4 3nVg==
I've now got NTP-over-PTP working on the Marvell AQC-107. I set up a
new PC with Fedora 38 as a server with a i210-T1 (same setup as with
the CM4 except for adding a width option to the PHC clock and changing
the offset). If I plug the server and the AQC-107 into the same
switch (a Unifi USW-Flex-XG), offsets were consistently in the low
tens of nanoseconds, and all the indicators. If there are multiple
switches between clients and servers, then the offsets get
significantly worse, as expected.
On the CM4 server, I've noticed another problem: there are spikes in
the PHC extpps refclock: instead of the offsets all being low tens of
nanoseconds (as with the i210), it spikes up to hundreds of
nanoseconds. I suspect this is the reading of the PHC interfering with
the extts events. See https://github.com/raspberrypi/linux/issues/5231
James
On Mon, Sep 4, 2023 at 9:31 PM Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
>
> On Mon, Sep 04, 2023 at 04:11:47PM +0200, Miroslav Lichvar wrote:
> > > Hardware Receive Filter Modes:
> > > none
> > > ptpv2-l4-event
> > > ptpv2-l2-event
> > > ptpv2-event
> >
> > That looks ok. I'm not sure why it doesn't work.
>
> Maybe it's limited to multicast. I've seen a Broadcom NIC doing that.
> Does ptp4l work in unicast mode on this NIC?
>
> Looking at the driver, it seems the timestamping filters are
> configured in software. I'm wondering if it could support an NTP
> filter.
>
> --
> Miroslav Lichvar
>
>
> --
> To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "unsubscribe" in the subject.
> For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "help" in the subject.
> Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.
>
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.