RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1910125 - chrony is configured and documented as though CONFIG_RTC_SYSTOHC were enabled in the kernel
Summary: chrony is configured and documented as though CONFIG_RTC_SYSTOHC were enabled...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: chrony
Version: 7.9
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Miroslav Lichvar
QA Contact: rhel-cs-infra-services-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-22 18:31 UTC by Dan Astoorian
Modified: 2021-01-04 13:40 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-04 13:40:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dan Astoorian 2020-12-22 18:31:36 UTC
Description of problem:
Hardware clock is not being kept synchronized.

Version-Release number of selected component (if applicable):
chrony-3.4-1.el7.x86_64

How reproducible:
Consistently

Steps to Reproduce:
1. Ensure chrony is running with the "rtcsync" option enabled in /etc/chrony.conf (as it is by default).
2. Run timedatectl; compare the system time with the RTC time.  (If necessary, manually set the RTC time a few seconds fast or slow, and wait: "rtcsync" is supposed to cause the kernel to correct the error within 11 minutes.)

Actual results:
RTC may drift significantly from the system time, notwithstanding the note in Chapter 3 of the System Administrators Guide that "the kernel automatically synchronizes the hardware clock to the system clock every 11 minutes."

Expected results:
RTC should not drift significantly from the system time when chrony is running with rtcsync enabled.

Additional info:
Red Hat Enterprise Linux 7/8 kernels appear to be built without the CONFIG_RTC_SYSTOHC option, which appears to be the mechanism which is supposed to keep the hardware clock synchronized with the system time when NTP is active.

If CONFIG_RTC_SYSTOHC is not going to be set in shipped kernels, a different mechanism should be used to keep the hardware clock synchronized (e.g., running hwclock during shutdown as Red Hat Enterprise Linux 6 did), and/or the documentation should be corrected to indicate that chrony's rtcsync directive has no effect when using default Red Hat Enterprise Linux kernels; it may or may not be prudent to change the chrony configuration to use rtcfile or a similar mechanism by default to manage hardware clock drift instead.

Similar issues may apply to the ntp package, and also to Red Hat Enterprise Linux 8.

Comment 2 Miroslav Lichvar 2021-01-04 13:40:29 UTC
The RHEL kernel is built with the CONFIG_GENERIC_CMOS_UPDATE option, which uses the legacy RTC support as opposed to the newer RTC class support, which has the CONFIG_RTC_SYSTOHC option.

If you don't see the RTC being updated every 11 minutes, it might be due to unreliable timing of the update. That is a kernel issue. For RHEL8, it is tracked in bug #1793880.


Note You need to log in before you can comment on or make changes to this bug.