| 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: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 4 Sep 2023 13:50:43 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1693828246; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=eggftoZX03HbjkSaei0+paIL9/TpNTyKnDAY+FKsB2U=; b=AO6mLTEyF8SoVGrHbXKslaABscQgdv+ZjqlbrDsXUW3WWnBp9YbHwuSCPZq6SG+/UBHv6w kL6hNWLRND7OH06MNWCOHaP1lQ8DkZjq2ruGNqLXmazudZGXgUAb1bBaGWmnAB4V8Oefcr 1hHKuuV64eHdqzPHj5oJ5SWwmbA6CRc=
On Mon, Sep 04, 2023 at 06:30:06PM +0700, James Clark wrote:
> "chronyc serverstats" looks good: I'm seeing increasing "NTP hardware RX
> timestamps" and
> "NTP hardware TX timestamps".
Is the server running on CM4?
> I'm now trying two clients, and I see different results with chronyc
> ntpdata:
>
> - another CM4: here I see RX timestamping : Hardware but TX timestamping :
> Kernel
Can you please enable the measurements log and see if all TX
timestamps are kernel or there is a mix of kernel and hardware? The HW
timestamping might be unreliable. You could try increasing hwtstimeout
to 1 to wait even longer for the TX timestamp.
You could also try adding "minpoll 2" to the hwtimestamp directive to
read the clock less frequently to avoid some collisions with the
timestamping access. IIRC the HW or driver might have an issue with
that.
> - an x86 box with the AQC107: here I see TX timestamping : Hardware and RX
> timestamping : Hardware
> but on the client "chronyc ntpdata" shows Kernel for TX timestamping and RX
> timestamping.
I have no experience with this NIC. What does ethtool -T show?
--
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.