Re: Chrony on CM4
James Clark <[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <CANz3_Eaxt-YVhrduFVutipnjQhFqXaRqvsPFe0H4_8vEg18EbA@mail.gmail.com> |
On Mon, Sep 4, 2023 at 3:46 PM Miroslav Lichvar <[email protected]> wrote: > > > It seems to be working properly: I get no errors and much better > > results than with another local chrony server that is not using > > hardware timestamping. But how do I tell if the hardware timestamping > > is working properly in both directions? > > On the client, "chronyc ntpdata" should consistently show Hardware for > both "TX timestamping" and "RX timestamping". On the server, "chronyc > serverstats" should show increasing "NTP hardware RX timestamps" and > "NTP hardware TX timestamps". The number of daemon and kernel > timestamps should be incrementing only with new/restarted clients and > clients not using interleaved mode. > "chronyc serverstats" looks good: I'm seeing increasing "NTP hardware RX timestamps" and "NTP hardware TX timestamps". 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 - 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'm not quite sure what's going on. James