clock skewed after laptop standby mode

[dcasota]

Windows Version

Microsoft Windows [Version 10.0.22631.3007]

WSL Version

5.15.137.3

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.137.3-microsoft-standard-WSL2+

Distro Version

Photon OS 5.0

Other Software

No response

Repro Steps

• Fresh Photon OS on WSL2 setup on laptop
• synched time
• leave terminal session open on laptop (no wsl --shutdown). leave laptop to go in standby over the night.
• check time and date

localuser [ /mnt/c/Users/user ]$ timedatectl
               Local time: Tue 2024-01-16 04:36:53 CET
           Universal time: Tue 2024-01-16 03:36:53 UTC
                 RTC time: Tue 2024-01-16 03:31:28
                Time zone: Europe/Zurich (CET, +0100)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no
localuser [ /mnt/c/Users/user ]$ sudo ntpdate -u pool.ntp.org
[sudo] password for localuser
16 Jan 09:12:02 ntpdate[14807]: step time server 46.140.15.108 offset +16461.141509 sec
localuser [ /mnt/c/Users/user ]$ timedatectl
               Local time: Tue 2024-01-16 09:12:09 CET
           Universal time: Tue 2024-01-16 08:12:09 UTC
                 RTC time: Tue 2024-01-16 03:32:19
                Time zone: Europe/Zurich (CET, +0100)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no
localuser [ /mnt/c/Users/user ]$ sudo hwclock --systohc
localuser [ /mnt/c/Users/user ]$ timedatectl
               Local time: Tue 2024-01-16 09:12:32 CET
           Universal time: Tue 2024-01-16 08:12:32 UTC
                 RTC time: Tue 2024-01-16 09:12:32
                Time zone: Europe/Zurich (CET, +0100)
System clock synchronized: yes
              NTP service: inactive
          RTC in local TZ: no
localuser [ /mnt/c/Users/user ]$

Expected Behavior

docs about time sync in wsl, respecting standby situations as well.

Actual Behavior

clock skewed.

In Eventlog, only a McAfee activity is protocolled during the standby time window.

Seems to be a known issue, but unsure if it correlates with the clock skewed issue.

Diagnostic Logs

No response

[ghost]

/dupe #10006

[microsoft-github-policy-service]

Hi! We've identified this issue as a duplicate of another one that already exists in this repository. This specific instance is being closed in favor of tracking the concern over on the referenced thread.

Thanks for your report!

[dcasota]

@pmartincic Spotted your patch https://lore.kernel.org/linux-hyperv/[email protected]/T/#u . Good to know. Thanks!