Leap Day phenomenon: Time Stops Passing when laptop is asleep

johnnynyquist · 2024-02-29 18:45:41

This is the strangest thing I've seen. Mature arch install, been using the laptop for years. Starting yesterday evening, I come out of suspend and the system clock is stuck at the time that the laptop was suspended. The skew is too great for `ntpd` to overcome. The computer doesn't seem to know the time is wrong:

b@glyph:foreground$ timedatectl
               Local time: Thu 2024-02-29 01:53:23 PST
           Universal time: Thu 2024-02-29 09:53:23 UTC
                 RTC time: Sat 2021-11-20 01:03:55
                Time zone: America/Los_Angeles (PST, -0800)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

(the current time is 10:39 AM in PST)

b@glyph:foreground$ ntpq -c sysinfo
associd=0 status=c028 leap_alarm, sync_unspec, 2 events, no_sys_peer,
system peer:        0.0.0.0:0
system peer mode:   unspec
leap indicator:     11
stratum:            16
log2 precision:     -24
root delay:         0.000
root dispersion:    0.000
reference ID:       .
reference time:     e98ad132.39f75fcf  Thu, Feb 29 2024  1:47:30.226
system jitter:      2.410422
clock jitter:       3.496
clock wander:       1.054
broadcast delay:    -50.000
symm. auth. delay:  0.000

`ntpd` is running:

b@glyph:foreground$ systemctl status ntpd
● ntpd.service - Network Time Service
     Loaded: loaded (/usr/lib/systemd/system/ntpd.service; enabled; preset: disabled)
     Active: active (running) since Wed 2024-02-28 17:38:29 PST; 8h ago
    Process: 469 ExecStart=/usr/bin/ntpd -g -u ntp:ntp (code=exited, status=0/SUCCESS)
   Main PID: 473 (ntpd)
      Tasks: 2 (limit: 38311)
     Memory: 2.9M (peak: 4.1M)
        CPU: 469ms
     CGroup: /system.slice/ntpd.service
             └─473 /usr/bin/ntpd -g -u ntp:ntp

Feb 29 01:49:27 glyph ntpd[473]: Deleting interface #6 wlan0, 192.168.0.225#123, interface stats: received=280, sent=288, dropped=0, act>
Feb 29 01:49:27 glyph ntpd[473]: 66.85.78.80 local addr 192.168.0.225 -> <null>
Feb 29 01:49:27 glyph ntpd[473]: 72.30.35.89 local addr 192.168.0.225 -> <null>
Feb 29 01:49:27 glyph ntpd[473]: 205.233.73.201 local addr 192.168.0.225 -> <null>
Feb 29 01:49:27 glyph ntpd[473]: 23.131.160.7 local addr 192.168.0.225 -> <null>
Feb 29 01:49:27 glyph ntpd[473]: Deleting interface #7 wlan0, fe80::1ac7:7a74:d5a5:f2ca%2#123, interface stats: received=0, sent=0, drop>
Feb 29 01:49:38 glyph ntpd[473]: Listen normally on 15 wlan0 192.168.0.225:123
Feb 29 01:49:38 glyph ntpd[473]: Listen normally on 16 wlan0 [fe80::1ac7:7a74:d5a5:f2ca%2]:123
Feb 29 01:49:38 glyph ntpd[473]: new interface(s) found: waking up resolver
Feb 29 01:55:11 glyph ntpd[473]: no peer for too long, server running free now

(01:49:27 last night is the time I last put the laptop to sleep)

I can solve the problem using the following routine:

b@glyph:foreground$ sudo systemctl stop ntpd
b@glyph:foreground$ sudo systemctl start ntpdate
b@glyph:foreground$ sudo systemctl start ntpd
b@glyph:foreground$ date
Thu Feb 29 10:42:56 AM PST 2024

Nothing changed on the system to brring this about (though it did coincide with the onset of leap day in UTC). I did a full `pacman -Syu` last night but the problem persists today. Any suggestions as to what is going on?

seth · 2024-02-29 20:39:49

been using the laptop for years

Does this happen on battery, external power or both?
Does the system sleep in S2idle, S3 or S4 (hibernation)?
Does it maintain the time while not sleeping, but being fully powered down?
Did you run any updates before this (and what was updated)?
Does it happen w/ the previous kernel (safe to downgrade in isolation, but don't forget OOT modules like nvidia or virtualbox)?

Edit: https://bbs.archlinux.org/viewtopic.php?id=283620

Last edited by seth (2024-02-29 21:56:13)

johnnynyquist · 2024-03-01 17:35:08

Thanks for your reply. I was using the laptop all day (it is my work machine) and now the bug is no longer repeating. This further implicates the leap day circumstance as a factor (though I would have expected to see other chatter about it if it was a systematic problem).
FYI, the sleep state is S3, and I did not have the chance to test whether the problem occurred when the machine was completely powered off.
No updates had been installed (for weeks actually) prior to noticing the bug.
Anyway, if I observe it again I will test the other items.

Arch Linux

#1 2024-02-29 18:45:41

Leap Day phenomenon: Time Stops Passing when laptop is asleep

#2 2024-02-29 20:39:49

Re: Leap Day phenomenon: Time Stops Passing when laptop is asleep

#3 2024-03-01 17:35:08

Re: Leap Day phenomenon: Time Stops Passing when laptop is asleep

Board footer