| Re: [chrony-users] Using Chrony with a DS3231 RTC without RTC_UIE_ON |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Using Chrony with a DS3231 RTC without RTC_UIE_ON
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 15 Jun 2020 08:56:46 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1592204211; 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=kCrRyT5C/0ZwkDY8q92+d4hV5dTqddHmkXBZkb/o0gc=; b=PgfdVqf5T35QjHEK4ars1MGHFCA2dM7d5OvB8DtUYEjcdUykRz/wkESX870Cb2AixUSvJH IqRoNPC2Pj7RNHGvC1qeaZ522zhxvbOi0qT8KxumqAeQORpOHv03VgANXCi0IegT1DGDo6 UhHg7STUkdnO4a7IPlhUQzSI520sB4M=
On Thu, Jun 11, 2020 at 07:57:15PM +0300, Avamander wrote:
> Hi,
>
> I'm using chrony version 3.5 (latest available) on Ubuntu 20.04 on my RPi4
> and Chrony refuses to use my DS3231 RTC, but hwclock on the other hand
> can use it just fine, maybe someone here has any ideas how to get it
> working?
It seems hwclock has a fallback to handle RTCs without interrupts by
reading the RTC time in a busy loop. I don't think that would be
acceptable for chronyd to consume 100% of a CPU core just to track an
RTC.
--
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.