[RESPONDED] FW13 AMD Fedora 39: System clock advances 50+ years during overnight suspend

Framework Laptop 13 Linux
1

First multi-hour suspend on this brand new machine. On resume this morning, from journalctl -b --output=short-full:

Tue 2023-11-14 23:46:33 PST angua systemd[1]: Reached target sleep.target - Sleep.
Tue 2023-11-14 23:46:33 PST angua systemd[1]: Starting systemd-suspend.service - System Suspend...
Tue 2023-11-14 23:46:33 PST angua systemd-sleep[31022]: Entering sleep state 'suspend'...
Tue 2023-11-14 23:46:33 PST angua kernel: PM: suspend entry (s2idle)
Tue 2023-11-14 23:46:34 PST angua rtkit-daemon[1675]: Successfully made thread 8887 of process 8852 (/usr/bin/gnome-shell) owned by '1000' high priority at nice level 0.
Tue 2023-11-14 23:46:34 PST angua kernel: Filesystems sync: 0.021 seconds
Tue 2023-11-14 23:46:34 PST angua rtkit-daemon[1675]: Successfully made thread 8887 of process 8852 (/usr/bin/gnome-shell) owned by '1000' RT at priority 20.
Tue 2077-09-28 18:41:15 PDT angua kernel: Freezing user space processes
Tue 2077-09-28 18:41:16 PDT angua kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Tue 2077-09-28 18:41:16 PDT angua kernel: OOM killer disabled.
Tue 2077-09-28 18:41:16 PDT angua kernel: Freezing remaining freezable tasks
Tue 2077-09-28 18:41:16 PDT angua kernel: Freezing remaining freezable tasks completed (elapsed 0.058 seconds)
Tue 2077-09-28 18:41:16 PDT angua kernel: printk: Suspending console(s) (use no_console_suspend to debug)
...
Tue 2077-09-28 18:41:16 PDT angua kernel: PM: suspend exit
...

This is a pretty vanilla Fedora 39 install, GNOME/Wayland running latest 6.5.11-300.fc39.x86_64 kernel from updates-testing. Kernel command line:

BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.5.11-300.fc39.x86_64 root=UUID=<uuid> ro rootflags=subvol=root rd.luks.uuid=luks-<uuid> rhgb quiet rtc_cmos.use_acpi_alarm=1

Edit: Machine came with BIOS 3.03.

More edit: Machine was plugged into a TB4 dock (power, assorted USB devices) throughout. External monitor separate on HDMI extension.

2

Time sync daemon log from this boot. I did the service restart towards the end to force the clock to adjust.

Tue 2023-11-14 18:52:00 PST angua systemd[1]: Starting chronyd.service - NTP client/server...
Tue 2023-11-14 18:52:00 PST angua chronyd[1711]: chronyd version 4.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 +DEBUG)
Tue 2023-11-14 18:52:00 PST angua chronyd[1711]: Frequency -45.435 +/- 160.681 ppm read from /var/lib/chrony/drift
Tue 2023-11-14 18:52:00 PST angua chronyd[1711]: Using right/UTC timezone to obtain leap second data
Tue 2023-11-14 18:52:00 PST angua chronyd[1711]: Loaded seccomp filter (level 2)
Tue 2023-11-14 18:52:00 PST angua systemd[1]: Started chronyd.service - NTP client/server.
Tue 2023-11-14 18:52:12 PST angua chronyd[1711]: Selected source 5.161.213.25 (2.fedora.pool.ntp.org)
Tue 2023-11-14 18:52:12 PST angua chronyd[1711]: System clock TAI offset set to 37 seconds
Tue 2023-11-14 18:52:14 PST angua chronyd[1711]: Selected source 172.233.153.85 (2.fedora.pool.ntp.org)
Tue 2023-11-14 19:35:25 PST angua chronyd[1711]: Detected falseticker 108.175.15.67 (2.fedora.pool.ntp.org)
Tue 2023-11-14 19:36:40 PST angua chronyd[1711]: Source 199.68.201.236 offline
Tue 2023-11-14 19:36:40 PST angua chronyd[1711]: Source 5.161.213.25 offline
Tue 2023-11-14 19:36:40 PST angua chronyd[1711]: Source 108.175.15.67 offline
Tue 2023-11-14 19:36:40 PST angua chronyd[1711]: Can't synchronise: no selectable sources
Tue 2023-11-14 19:36:40 PST angua chronyd[1711]: Source 172.233.153.85 offline
Tue 2023-11-14 19:37:50 PST angua chronyd[1711]: Forward time jump detected!
Tue 2023-11-14 19:37:50 PST angua chronyd[1711]: Source 199.68.201.236 online
Tue 2023-11-14 19:37:50 PST angua chronyd[1711]: Source 172.233.153.85 online
Tue 2023-11-14 19:37:50 PST angua chronyd[1711]: Source 5.161.213.25 online
Tue 2023-11-14 19:37:50 PST angua chronyd[1711]: Source 108.175.15.67 online
Tue 2023-11-14 19:37:55 PST angua chronyd[1711]: Selected source 5.161.213.25 (2.fedora.pool.ntp.org)
Tue 2023-11-14 19:39:01 PST angua chronyd[1711]: Selected source 199.68.201.236 (2.fedora.pool.ntp.org)
Tue 2023-11-14 19:39:02 PST angua chronyd[1711]: Detected falseticker 108.175.15.67 (2.fedora.pool.ntp.org)
Tue 2023-11-14 19:40:57 PST angua chronyd[1711]: Source 172.233.153.85 offline
Tue 2023-11-14 19:40:57 PST angua chronyd[1711]: Source 5.161.213.25 offline
Tue 2023-11-14 19:40:57 PST angua chronyd[1711]: Source 108.175.15.67 offline
Tue 2023-11-14 19:40:57 PST angua chronyd[1711]: Can't synchronise: no selectable sources
Tue 2023-11-14 19:40:57 PST angua chronyd[1711]: Source 199.68.201.236 offline
Tue 2023-11-14 19:41:12 PST angua chronyd[1711]: Source 199.68.201.236 online
Tue 2023-11-14 19:41:12 PST angua chronyd[1711]: Source 172.233.153.85 online
Tue 2023-11-14 19:41:12 PST angua chronyd[1711]: Source 5.161.213.25 online
Tue 2023-11-14 19:41:12 PST angua chronyd[1711]: Source 108.175.15.67 online
Tue 2023-11-14 19:41:13 PST angua chronyd[1711]: Detected falseticker 199.68.201.236 (2.fedora.pool.ntp.org)
Tue 2023-11-14 19:41:13 PST angua chronyd[1711]: Selected source 172.233.153.85 (2.fedora.pool.ntp.org)
Tue 2023-11-14 19:41:13 PST angua chronyd[1711]: Can't synchronise: no majority
Tue 2023-11-14 19:41:13 PST angua chronyd[1711]: Detected falseticker 108.175.15.67 (2.fedora.pool.ntp.org)
Tue 2023-11-14 19:41:13 PST angua chronyd[1711]: Selected source 172.233.153.85 (2.fedora.pool.ntp.org)
Tue 2023-11-14 19:41:13 PST angua chronyd[1711]: Detected falseticker 108.175.15.67 (2.fedora.pool.ntp.org)
Tue 2023-11-14 19:41:16 PST angua chronyd[1711]: Source 108.175.15.67 replaced with 2001:470:6f:483::1 (2.fedora.pool.ntp.org)
Tue 2023-11-14 19:42:23 PST angua chronyd[1711]: Selected source 199.68.201.236 (2.fedora.pool.ntp.org)
Tue 2023-11-14 19:42:23 PST angua chronyd[1711]: Detected falseticker 5.161.213.25 (2.fedora.pool.ntp.org)
Tue 2023-11-14 19:45:37 PST angua chronyd[1711]: Selected source 172.233.153.85 (2.fedora.pool.ntp.org)
Tue 2023-11-14 21:06:43 PST angua chronyd[1711]: Source 2001:470:6f:483::1 offline
Tue 2023-11-14 21:06:43 PST angua chronyd[1711]: Source 199.68.201.236 offline
Tue 2023-11-14 21:06:43 PST angua chronyd[1711]: Source 5.161.213.25 offline
Tue 2023-11-14 21:06:43 PST angua chronyd[1711]: Can't synchronise: no selectable sources
Tue 2023-11-14 21:06:43 PST angua chronyd[1711]: Source 172.233.153.85 offline
Tue 2023-11-14 23:21:55 PST angua chronyd[1711]: Forward time jump detected!
Tue 2023-11-14 23:21:55 PST angua chronyd[1711]: Source 172.233.153.85 online
Tue 2023-11-14 23:21:55 PST angua chronyd[1711]: Source 199.68.201.236 online
Tue 2023-11-14 23:21:55 PST angua chronyd[1711]: Source 5.161.213.25 online
Tue 2023-11-14 23:21:57 PST angua chronyd[1711]: Source 2001:470:6f:483::1 online
Tue 2023-11-14 23:21:59 PST angua chronyd[1711]: Selected source 172.233.153.85 (2.fedora.pool.ntp.org)
Tue 2023-11-14 23:39:00 PST angua chronyd[1711]: Source 2001:470:6f:483::1 offline
Tue 2023-11-14 23:39:00 PST angua chronyd[1711]: Source 199.68.201.236 offline
Tue 2023-11-14 23:39:00 PST angua chronyd[1711]: Source 5.161.213.25 offline
Tue 2023-11-14 23:39:00 PST angua chronyd[1711]: Can't synchronise: no selectable sources
Tue 2023-11-14 23:39:00 PST angua chronyd[1711]: Source 172.233.153.85 offline
Tue 2023-11-14 23:39:05 PST angua chronyd[1711]: Source 172.233.153.85 online
Tue 2023-11-14 23:39:05 PST angua chronyd[1711]: Source 199.68.201.236 online
Tue 2023-11-14 23:39:05 PST angua chronyd[1711]: Source 5.161.213.25 online
Tue 2023-11-14 23:39:06 PST angua chronyd[1711]: Selected source 172.233.153.85 (2.fedora.pool.ntp.org)
Tue 2023-11-14 23:39:09 PST angua chronyd[1711]: Source 2001:470:6f:483::1 online
Tue 2023-11-14 23:41:49 PST angua chronyd[1711]: Source 2001:470:6f:483::1 offline
Tue 2023-11-14 23:41:49 PST angua chronyd[1711]: Source 199.68.201.236 offline
Tue 2023-11-14 23:41:49 PST angua chronyd[1711]: Source 5.161.213.25 offline
Tue 2023-11-14 23:41:49 PST angua chronyd[1711]: Can't synchronise: no selectable sources
Tue 2023-11-14 23:41:49 PST angua chronyd[1711]: Source 172.233.153.85 offline
Tue 2023-11-14 23:41:55 PST angua chronyd[1711]: Source 172.233.153.85 online
Tue 2023-11-14 23:41:55 PST angua chronyd[1711]: Source 199.68.201.236 online
Tue 2023-11-14 23:41:55 PST angua chronyd[1711]: Source 5.161.213.25 online
Tue 2023-11-14 23:41:55 PST angua chronyd[1711]: Selected source 172.233.153.85 (2.fedora.pool.ntp.org)
Tue 2023-11-14 23:41:58 PST angua chronyd[1711]: Source 2001:470:6f:483::1 online
Tue 2023-11-14 23:43:04 PST angua chronyd[1711]: Source 2001:470:6f:483::1 offline
Tue 2023-11-14 23:43:04 PST angua chronyd[1711]: Source 199.68.201.236 offline
Tue 2023-11-14 23:43:04 PST angua chronyd[1711]: Source 5.161.213.25 offline
Tue 2023-11-14 23:43:04 PST angua chronyd[1711]: Can't synchronise: no selectable sources
Tue 2023-11-14 23:43:04 PST angua chronyd[1711]: Source 172.233.153.85 offline
Tue 2023-11-14 23:43:05 PST angua chronyd[1711]: Source 172.233.153.85 online
Tue 2023-11-14 23:43:05 PST angua chronyd[1711]: Source 199.68.201.236 online
Tue 2023-11-14 23:43:05 PST angua chronyd[1711]: Source 5.161.213.25 online
Tue 2023-11-14 23:43:05 PST angua chronyd[1711]: Selected source 172.233.153.85 (2.fedora.pool.ntp.org)
Tue 2023-11-14 23:43:05 PST angua chronyd[1711]: Source 2001:470:6f:483::1 online
Tue 2077-09-28 18:41:15 PDT angua chronyd[1711]: Forward time jump detected!
Tue 2077-09-28 18:41:15 PDT angua chronyd[1711]: Can't synchronise: no selectable sources
Tue 2077-09-28 18:41:15 PDT angua chronyd[1711]: Source 2001:470:6f:483::1 offline
Tue 2077-09-28 18:41:15 PDT angua chronyd[1711]: Source 172.233.153.85 offline
Tue 2077-09-28 18:41:15 PDT angua chronyd[1711]: Source 199.68.201.236 offline
Tue 2077-09-28 18:41:15 PDT angua chronyd[1711]: Source 5.161.213.25 offline
Tue 2077-09-28 18:41:20 PDT angua chronyd[1711]: Source 172.233.153.85 online
Tue 2077-09-28 18:41:20 PDT angua chronyd[1711]: Source 199.68.201.236 online
Tue 2077-09-28 18:41:20 PDT angua chronyd[1711]: Source 5.161.213.25 online
Tue 2077-09-28 18:41:21 PDT angua chronyd[1711]: Source 172.233.153.85 replaced with 45.79.214.107 (2.fedora.pool.ntp.org)
Tue 2077-09-28 18:41:24 PDT angua chronyd[1711]: Source 2001:470:6f:483::1 online
Tue 2077-09-28 18:41:27 PDT angua chronyd[1711]: Selected source 199.68.201.236 (2.fedora.pool.ntp.org)
Tue 2077-09-28 18:41:27 PDT angua chronyd[1711]: System clock wrong by -1700034393.694561 seconds
Tue 2077-09-28 18:42:21 PDT angua chronyd[1711]: Source 5.161.213.25 offline
Tue 2077-09-28 18:42:21 PDT angua chronyd[1711]: Source 2001:470:6f:483::1 offline
Tue 2077-09-28 18:42:21 PDT angua chronyd[1711]: Source 45.79.214.107 offline
Tue 2077-09-28 18:42:21 PDT angua chronyd[1711]: Can't synchronise: no selectable sources
Tue 2077-09-28 18:42:21 PDT angua chronyd[1711]: Source 199.68.201.236 offline
Tue 2077-09-28 18:42:33 PDT angua chronyd[1711]: Source 5.161.213.25 online
Tue 2077-09-28 18:42:33 PDT angua chronyd[1711]: Source 199.68.201.236 online
Tue 2077-09-28 18:42:33 PDT angua chronyd[1711]: Source 45.79.214.107 online
Tue 2077-09-28 18:42:33 PDT angua chronyd[1711]: Selected source 5.161.213.25 (2.fedora.pool.ntp.org)
Tue 2077-09-28 18:42:36 PDT angua chronyd[1711]: Source 2001:470:6f:483::1 online
Tue 2077-09-28 18:42:50 PDT angua chronyd[1711]: Source 2001:470:6f:483::1 offline
Tue 2077-09-28 18:42:50 PDT angua chronyd[1711]: Source 199.68.201.236 offline
Tue 2077-09-28 18:42:50 PDT angua chronyd[1711]: Source 45.79.214.107 offline
Tue 2077-09-28 18:42:50 PDT angua chronyd[1711]: Can't synchronise: no selectable sources
Tue 2077-09-28 18:42:50 PDT angua chronyd[1711]: Source 5.161.213.25 offline
Tue 2077-09-28 18:42:58 PDT angua chronyd[1711]: Source 5.161.213.25 online
Tue 2077-09-28 18:42:58 PDT angua chronyd[1711]: Source 199.68.201.236 online
Tue 2077-09-28 18:42:58 PDT angua chronyd[1711]: Source 45.79.214.107 online
Tue 2077-09-28 18:42:58 PDT angua chronyd[1711]: Selected source 199.68.201.236 (2.fedora.pool.ntp.org)
Tue 2077-09-28 18:43:01 PDT angua chronyd[1711]: Source 2001:470:6f:483::1 online
Tue 2077-09-28 18:43:12 PDT angua chronyd[1711]: Source 5.161.213.25 offline
Tue 2077-09-28 18:43:12 PDT angua chronyd[1711]: Source 2001:470:6f:483::1 offline
Tue 2077-09-28 18:43:12 PDT angua chronyd[1711]: Source 45.79.214.107 offline
Tue 2077-09-28 18:43:12 PDT angua chronyd[1711]: Can't synchronise: no selectable sources
Tue 2077-09-28 18:43:12 PDT angua chronyd[1711]: Source 199.68.201.236 offline
Tue 2077-09-28 18:43:21 PDT angua chronyd[1711]: Source 5.161.213.25 online
Tue 2077-09-28 18:43:21 PDT angua chronyd[1711]: Source 199.68.201.236 online
Tue 2077-09-28 18:43:21 PDT angua chronyd[1711]: Source 45.79.214.107 online
Tue 2077-09-28 18:43:21 PDT angua chronyd[1711]: Selected source 199.68.201.236 (2.fedora.pool.ntp.org)
Tue 2077-09-28 18:43:25 PDT angua chronyd[1711]: Source 2001:470:6f:483::1 online
Tue 2077-09-28 18:43:53 PDT angua chronyd[1711]: chronyd exiting
Tue 2077-09-28 18:43:53 PDT angua systemd[1]: Stopping chronyd.service - NTP client/server...
Tue 2077-09-28 18:43:53 PDT angua systemd[1]: chronyd.service: Deactivated successfully.
Tue 2077-09-28 18:43:53 PDT angua systemd[1]: Stopped chronyd.service - NTP client/server.
Tue 2077-09-28 18:43:53 PDT angua systemd[1]: Starting chronyd.service - NTP client/server...
Tue 2077-09-28 18:43:53 PDT angua chronyd[32747]: chronyd version 4.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 +DEBUG)
Tue 2077-09-28 18:43:53 PDT angua chronyd[32747]: Frequency -5.544 +/- 11.442 ppm read from /var/lib/chrony/drift
Tue 2077-09-28 18:43:53 PDT angua chronyd[32747]: Using right/UTC timezone to obtain leap second data
Tue 2077-09-28 18:43:53 PDT angua chronyd[32747]: Loaded seccomp filter (level 2)
Tue 2077-09-28 18:43:53 PDT angua systemd[1]: Started chronyd.service - NTP client/server.
Tue 2077-09-28 18:43:58 PDT angua chronyd[32747]: Selected source 2001:418:3ff::53 (2.fedora.pool.ntp.org)
Tue 2077-09-28 18:43:58 PDT angua chronyd[32747]: System clock wrong by -1700034380.433333 seconds
Wed 2023-11-15 09:57:37 PST angua chronyd[32747]: System clock was stepped by -1700034380.433333 seconds
Wed 2023-11-15 09:57:37 PST angua chronyd[32747]: System clock TAI offset set to 37 seconds
1 Like
3

Quite the glitch… I have my AMD FW13 (Ryzen 5 7640U, 32GB RAM, Kernel 6.5.6-300) plugged in to an HP TB dock, and have not run in to issues with it yet.
Not sure if my response onto this post is of any help, but here it is:

Summary

Hope that you are able to resolve that soon.

4

Thanks! I do have auto date/time enabled in settings.

I haven’t explicitly (command line systemctl) changed anything from defaults for systemd-timedated.service. It’s currently showing as running but only started very recently?

$ systemctl status systemd-timedated.service 
â—Ź systemd-timedated.service - Time & Date Service
     Loaded: loaded (/usr/lib/systemd/system/systemd-timedated.service; static)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Wed 2023-11-15 11:25:30 PST; 46s ago
       Docs: man:systemd-timedated.service(8)
             man:localtime(5)
             man:org.freedesktop.timedate1(5)
   Main PID: 12372 (systemd-timedat)
      Tasks: 1 (limit: 71856)
     Memory: 1.2M
        CPU: 29ms
     CGroup: /system.slice/systemd-timedated.service
             └─12372 /usr/lib/systemd/systemd-timedated

Nov 15 11:25:30 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:25:30 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.

ok, looks like it starts/stop periodically:

$ journalctl --output=short-full --unit systemd-timedated.service --boot
Wed 2023-11-15 10:45:40 PST angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Wed 2023-11-15 10:45:40 PST angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Wed 2023-11-15 10:46:32 PST angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Wed 2023-11-15 10:55:19 PST angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Wed 2023-11-15 10:55:19 PST angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Wed 2023-11-15 10:56:52 PST angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Wed 2023-11-15 11:19:23 PST angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Wed 2023-11-15 11:19:23 PST angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Wed 2023-11-15 11:19:53 PST angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Wed 2023-11-15 11:19:53 PST angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Wed 2023-11-15 11:19:53 PST angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Wed 2023-11-15 11:20:30 PST angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Wed 2023-11-15 11:20:30 PST angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Wed 2023-11-15 11:20:30 PST angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Wed 2023-11-15 11:21:30 PST angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Wed 2023-11-15 11:21:30 PST angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Wed 2023-11-15 11:21:30 PST angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Wed 2023-11-15 11:22:30 PST angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Wed 2023-11-15 11:22:30 PST angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Wed 2023-11-15 11:22:30 PST angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Wed 2023-11-15 11:23:30 PST angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Wed 2023-11-15 11:23:30 PST angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Wed 2023-11-15 11:23:30 PST angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Wed 2023-11-15 11:24:30 PST angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Wed 2023-11-15 11:24:30 PST angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Wed 2023-11-15 11:24:30 PST angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Wed 2023-11-15 11:25:30 PST angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Wed 2023-11-15 11:25:30 PST angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Wed 2023-11-15 11:25:30 PST angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Wed 2023-11-15 11:26:30 PST angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Wed 2023-11-15 11:26:30 PST angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Wed 2023-11-15 11:26:30 PST angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
5

For completeness, from the other thread referenced above, my /proc/driver/rtc status (with AC plugged in via the TB dock):

$ cat /proc/driver/rtc 
rtc_time	: 19:22:26
rtc_date	: 2023-11-15
alrm_time	: 00:05:54
alrm_date	: 2023-11-16
alarm_IRQ	: no
alrm_pending	: no
update IRQ enabled	: no
periodic IRQ enabled	: no
periodic IRQ frequency	: 1024
max user IRQ frequency	: 64
24hr		: yes
periodic_IRQ	: no
update_IRQ	: no
HPET_emulated	: no
BCD		: yes
DST_enable	: no
periodic_freq	: 1024
batt_status	: okay
6

Hi @dimitris ,

can we check the status of timesyncd?

systemctl status systemd-timesyncd
1 Like
7

Interesting…

$ systemctl status systemd-timesyncd.service 
â—‹ systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; disabled; preset: disabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)
       Docs: man:systemd-timesyncd.service(8)

However it has run every minute until earlier this boot:

$ journalctl --unit systemd-timedated.service --boot
Nov 15 10:45:40 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 10:45:40 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 10:46:32 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 10:55:19 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 10:55:19 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 10:56:52 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 11:19:23 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:19:23 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 11:19:53 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 11:19:53 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:19:53 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 11:20:30 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 11:20:30 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:20:30 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 11:21:30 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 11:21:30 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:21:30 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 11:22:30 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 11:22:30 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:22:30 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 11:23:30 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 11:23:30 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:23:30 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 11:24:30 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 11:24:30 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:24:30 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 11:25:30 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 11:25:30 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:25:30 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 11:26:30 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 11:26:30 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:26:30 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 11:27:30 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 11:27:30 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:27:30 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 11:28:30 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 11:28:30 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:28:30 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 11:29:30 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 11:29:30 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:29:30 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 11:30:30 angua systemd[1]: systemd-timedated.service: Deactivated successfully.
Nov 15 11:30:30 angua systemd[1]: Starting systemd-timedated.service - Time & Date Service...
Nov 15 11:30:30 angua systemd[1]: Started systemd-timedated.service - Time & Date Service.
Nov 15 11:31:30 angua systemd[1]: systemd-timedated.service: Deactivated successfully.

and

image
image1325Ă—758 76.8 KB

Edit: chronyd is running. The only config I have touched so far is the GNOME settings UI to turn Automatic Date & Time on.

$ systemctl status chrony*
â—Ź chronyd.service - NTP client/server
     Loaded: loaded (/usr/lib/systemd/system/chronyd.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Wed 2023-11-15 10:45:30 PST; 6h ago
       Docs: man:chronyd(8)
             man:chrony.conf(5)
    Process: 1719 ExecStart=/usr/sbin/chronyd $OPTIONS (code=exited, status=0/SUCCESS)
   Main PID: 1765 (chronyd)
      Tasks: 1 (limit: 71856)
     Memory: 6.6M
        CPU: 205ms
     CGroup: /system.slice/chronyd.service
             └─1765 /usr/sbin/chronyd -F 2

Nov 15 16:53:12 angua chronyd[1765]: Source 5.161.213.25 offline
Nov 15 16:53:12 angua chronyd[1765]: Source 198.30.92.2 offline
Nov 15 16:53:12 angua chronyd[1765]: Source 104.236.167.15 offline
Nov 15 16:53:12 angua chronyd[1765]: Can't synchronise: no selectable sources
Nov 15 16:53:12 angua chronyd[1765]: Source 216.229.4.69 offline
Nov 15 16:53:17 angua chronyd[1765]: Source 5.161.213.25 online
Nov 15 16:53:17 angua chronyd[1765]: Source 198.30.92.2 online
Nov 15 16:53:17 angua chronyd[1765]: Source 216.229.4.69 online
Nov 15 16:53:17 angua chronyd[1765]: Source 104.236.167.15 online
Nov 15 16:53:17 angua chronyd[1765]: Selected source 104.236.167.15 (2.fedora.pool.ntp.org)
8

Sorry, before going to ntp sync route, can we try adding in kernel params, it is suggested on the thread you linked.

rtc_cmos.use_acpi_alarm=1

see if it resolves the issue?

9

Yup, already there :slight_smile:

10

Somewhat wild thought: When I first powered the machine on (before installing Fedora), I immediately went into the BIOS to make sure settings (AMDGPU memory window, charge threshold) were as I wanted them to be.

I did not set the RTC at that time. It might have been set at some default that’s far into the future.

I assume that when the OS eventually completed its NTP time sync during/after installation, it would have actually caused the RTC clock to also sync up. Could that not be the case on this board?

11

Oh right, missed that.

12

Btw have you tried the official 39 release yet? is this beta?

13

Official release, installed from an ISO image downloaded yesterday. dnf updated earlier today.

1 Like
14

By the way, a little background on why I noticed and how this could bite users if it wasn’t a random fluke: NetworkManager is configured to automatically connect/require a VPN when connecting to my usual WLAN. So when I resumed the machine this morning, the VPN certificates had “expired”.

If it hadn’t been for that, it’s quite possible that chrony and/or systemd-timesyncd would have rather quickly fixed the clock before I would notice anything.

Even if so, if that’s not a one-off and the RTC can accelerate at relativistic speeds while suspended it could be an issue worth fixing. Similar certificate “expiration” can cause problems e.g. with enterprise login/screen unlock when resuming (Linux and/or Windows).

15

I had the same problem, at the exact same point during suspend.

It looks like the new timestamp is suspiciously close to 2 * epoch(old_timestamp). (Both in OPs logs and mine)

Directly after the jump I have a bunch these in the logs:

kernel: Unable to read current time from RTC .

And after the resume:

kernel: mach_set_cmos_time: RTC write failed with error -22

16

There is a very similar kernel report for this issue on some other products. AFAIK AMD has never reproduced it, and only seen by the two reports there previously.

There is a debugging patch specifically attached to that bug report. Any of you guys that can reproduce this issue, would you mind rebuilding your kernel with that patch? If you can reproduce the issue it will add a lot more context about the situation that lead to it which could be helpful at finding what is actually wrong in the kernel when this happens.

17

@Thomas_Weissschuh I also had a bunch of unable to read current time from RTC:

Tue 2023-11-14 23:46:33 PST angua kernel: PM: suspend entry (s2idle)
Tue 2023-11-14 23:46:34 PST angua rtkit-daemon[1675]: Successfully made thread 8887 of process 8852 (/usr/bin/gnome-shell) owned by '1000' high priority at nice level 0.
Tue 2023-11-14 23:46:34 PST angua kernel: Filesystems sync: 0.021 seconds
Tue 2023-11-14 23:46:34 PST angua rtkit-daemon[1675]: Successfully made thread 8887 of process 8852 (/usr/bin/gnome-shell) owned by '1000' RT at priority 20.
Tue 2077-09-28 18:41:15 PDT angua kernel: Freezing user space processes
Tue 2077-09-28 18:41:16 PDT angua kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Tue 2077-09-28 18:41:16 PDT angua kernel: OOM killer disabled.
Tue 2077-09-28 18:41:16 PDT angua kernel: Freezing remaining freezable tasks
Tue 2077-09-28 18:41:16 PDT angua kernel: Freezing remaining freezable tasks completed (elapsed 0.058 seconds)
Tue 2077-09-28 18:41:16 PDT angua kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Tue 2077-09-28 18:41:16 PDT angua kernel: queueing ieee80211 work while going to suspend
Tue 2077-09-28 18:41:16 PDT angua kernel: PM: suspend devices took 0.179 seconds
Tue 2077-09-28 18:41:16 PDT angua kernel: ACPI: EC: interrupt blocked
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC
Tue 2077-09-28 18:41:16 PDT angua kernel: Unable to read current time from RTC

but no mach_set_cmos_time in the journal at all.

@Mario_Limonciello I can’t promise I’ll succeed in building a patched kernel, haven’t done this since literally the last millennium. I think I’ll follow the Fedora guide.

@Loell_Framework something to run by you and/or Kieran (trying to limit tagging to people already in the thread): The kernel bug entry that Mario mentioned indicates that the EC can, in general, have an indirect effect on RTC behavior/use during s2idle. I have a couple of spare rechargeable cells available on a just-in-case basis for the two 11 gen machines in the household. Would it hurt/be worth a try to install one in this AMD machine’s empty holder to see if it has any effect? Also any EC thoughts about this clock issue in general?

18

that the EC can, in general, have an indirect effect on RTC behavior/use during s2idle .

IIRC the Framework EC is connected over eSPI, which it’s possible to read RTC time values through. Given all these failures are happening around the s2idle sequence is it plausible that it’s requesting RTC time values at the same time as Linux is?

1 Like
19

Maybe it’s relevant:

The probing of cros_ec_lpc fails.
The ID read via MEC is “0x00 0x00” and via non-MEC it’s “0xff 0xff”.

I applied the provided patch, maybe I can reproduce it.

20

Johnny ?