| Re: [chrony-users] late-arriving hardware timestamps |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] late-arriving hardware timestamps
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Tue, 23 Nov 2021 17:38:39 +0100
- Authentication-results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1637685527; 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=rHUmXnzIY5XoEqUpA617ZBtiVVyom99GaaC9ygeQzWk=; b=gE1nAdk4CmIk4bjEJvUSxUaod+fsM6qu77Q93WOCDX5a5IxQbFtgcvJEmR++9uE1sKsX2t 5cmHS5i1DQLpgcC7kTWqiKZDhOHLccmbU6jlSvSvH0ywHYvu54fMlJNogl0d2Hawf6Ucck ZV/0kAWK1N9ly9sF+nzbaIWNYP+t+gw=
On Tue, Nov 23, 2021 at 11:21:13AM -0500, Aaron Ball wrote:
> On our test hosts with X550 NICs, we're seeing fewer hardware
> timestamps under 4.1 than under 3.2.
There was a workaround added in 3.3 to wait (for up to 200
microseconds) for late HW TX timestamps of client requests. I'd expect
4.1 to be better than 3.2, not worse.
Can you please post your chrony.conf? Nothing else changed, like
kernel, drivers, firmware?
If you enable debug log (-d -d and chronyd compiled with
--enable-debug), does the problem disappear? It would be good to
confirm that you are getting the "Suspended RX processing" messages,
but you might need to patch the code to log those messages at a higher
log level and disable the debug output to still be able to reproduce
the problem.
--
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.