On Thu, Jun 12, 2025 at 12:42:50PM +0200, Julian Sikorski wrote: > After more detailed investigation, it appears that the hardware clock keeps > ticking, the system time does not. This is after an affected resume - after > running chrony makestep, date and hwclock outputs match: Is the step reported by chronyd close to 3600 seconds? If the RTC is keeping time in local time (not UTC), it might be an offset caused by the DST change. It's best to switch RTC to UTC. If the step corresponds to the time the machine was suspended, it's more likely a kernel bug. -- Miroslav Lichvar -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
