Am 12.06.25 um 16:10 schrieb Miroslav Lichvar:
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.
Kernel bug then - in the example I picked, the 3600 seconds step is
merely accidental. I have a better one, this is after most recent resume:
$ timedatectl
Local time: Do 2025-06-12 13:42:26 CEST
Universal time: Do 2025-06-12 11:42:26 UTC
RTC time: Do 2025-06-12 19:47:02
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: no
NTP service: active
RTC in local TZ: no
RTC is already in UTC. According to systemd journal, approx. four
minutes have passed between suspend and resume.
If it is a kernel bug, where should I report it to? I tried PM component
in kernel bugzilla [1], but got no response so far.
Best regards,
Julian
[1] https://bugzilla.kernel.org/show_bug.cgi?id=220208
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
