Kernel logs times are off by a bit more than one day #33293
Description
systemd version the issue has been seen with
256-rc4
Used distribution
Debian Trixie
Linux kernel version used
6.7.12-amd64
CPU architectures issue was seen on
None
Component
systemd-journald
Expected behaviour you didn't see
I expected "monotonic" times while reading logs from journalctl -f (at least with -o short-monotonic).
Unexpected behaviour you saw
I saw logs from the future here, like from tomorrow, a tad more than 24h. From 24h 36m and a few seconds in the future, or 88563 seconds but I bet this number is not a constant.
Steps to reproduce the problem
I don't know yet, I only have a few hints.
Additional program output to the terminal or log subsystem illustrating the issue
Boot happened with: Jun 10 18:33:27 kalir systemd-journald[1318]: Journal started
First occurence of time travel a few hours later, related to hibernation:
Jun 10 21:57:50 kalir NetworkManager[1742]: <info> [1718049470.7180] dhcp4 (wlp1s0): state changed no lease
Jun 11 00:12:24 kalir kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Jun 10 21:57:50 kalir dbus-daemon[1682]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.14' (uid=0 pid=1742 comm="/usr/sbin/NetworkManager --no-daemon")
Now, at the time of writing, we're at Jun 12 13:39:15, but I already see events from the future by searching Jun 13 in the logs:
Jun 12 13:29:15 kalir rtkit-daemon[2213]: Supervising 0 threads of 0 processes of 0 users.
Jun 12 13:29:15 kalir rtkit-daemon[2213]: Supervising 0 threads of 0 processes of 0 users.
Jun 12 13:29:31 kalir gdm-password][104683]: gkr-pam: unlocked login keyring
Jun 12 13:29:32 kalir NetworkManager[1742]: <info> [1718191772.0770] agent-manager: agent[4117da6764403ca4,:1.78/org.gnome.Shell.NetworkAgent/1000]: a
gent registered
Jun 13 15:05:49 kalir kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Jun 13 15:05:49 kalir kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Jun 13 15:05:49 kalir kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=14
Jun 13 15:05:49 kalir kernel: [drm:amdgpu_mes_reg_write_reg_wait [amdgpu]] *ERROR* failed to reg_write_reg_wait
Jun 12 13:29:50 kalir rtkit-daemon[2213]: Supervising 0 threads of 0 processes of 0 users.
Jun 12 13:29:50 kalir rtkit-daemon[2213]: Supervising 0 threads of 0 processes of 0 users.
I notice that the kernel lines are in the future while the not kernel ones are good.
Running journalctl with -o short-monotonic does not help, I see the same jumps:
[ 4258.534832] kalir dbus-daemon[1682]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dis
patcher.service' requested by ':1.14' (uid=0 pid=1742 comm="/usr/sbin/NetworkManager --no-daemon")
[ 4258.535896] kalir avahi-daemon[1679]: Withdrawing address record for 192.168.1.34 on wlp1s0.
[12332.553347] kalir kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[ 4258.535939] kalir avahi-daemon[1679]: Leaving mDNS multicast group on interface wlp1s0.IPv4 with address 192.168.1.34.
[12332.557761] kalir kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[12332.561601] kalir kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[12332.564929] kalir kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
[ 4258.548293] kalir avahi-daemon[1679]: Interface wlp1s0.IPv4 no longer relevant for mDNS.