Ubuntu
systemd package

systemd-timesyncd doesn't sync time after resume from hibernate

Bug #1740666 reported by Pavel on 2017-12-31

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Confirmed	Undecided	Unassigned
	systemd (Ubuntu)	New	Undecided	Unassigned

Bug Description

When resuming, the clock remains at the time when the hibernate happened, even if timedatectl claims that it is being synced:

$ timedatectl status
      Local time: Вс 2017-12-31 13:46:16 +05
  Universal time: Вс 2017-12-31 08:46:16 UTC
        RTC time: Вс 2017-12-31 08:46:16
       Time zone: Asia/Yekaterinburg (+05, +0500)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no

I've tried waiting a bit, but this persisted for some minutes, so I forced an update with

systemctl restart systemd-timesyncd.service

And afterwards the time was (apparently) correctly synced.

Please, let me know what further informations are needed to debug the
issue, and I would be happy to do some other test.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Dec 31 13:41:51 2017
InstallationDate: Installed on 2017-06-05 (208 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: Gigabyte Technology Co., Ltd. P35-DS3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago)
dmi.bios.date: 06/18/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F14
dmi.board.name: P35-DS3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-DS3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Tags:

Revision history for this message

Pavel (spvkgn) wrote on 2017-12-31:

CurrentDmesg.txt Edit (215.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.9 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (136.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (16.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (757 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (796 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (326 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.5 KiB, text/plain; charset="utf-8")
SystemdDelta.txt Edit (794 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (161.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2018-01-02:

Does this system have hardware clock?

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2018-01-02: Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Pavel (spvkgn) wrote on 2018-01-02:

I can read hw clock:

$ sudo hwclock --show
2018-01-02 13:54:07.249593+0500

Revision history for this message

Pavel (spvkgn) wrote on 2018-01-07:

journalctl output after resume: https://paste.ubuntu.com/26337345/

Revision history for this message

Kai-Heng Feng (kaihengfeng) wrote on 2018-02-01:

I think LP: #1744988 is the same bug as this one.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2018-03-05:

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status:	New → Confirmed

Revision history for this message

Pavel (spvkgn) wrote on 2018-04-05:

#1744988 bug not resolved this for me.

Revision history for this message

Dan Streetman (ddstreet) wrote on 2021-06-30:

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status:	Confirmed → Invalid

Norbert (nrbrtx) on 2021-07-31

tags:

removed: artful

Anti Mailer (antimailer) on 2023-01-05

Changed in systemd (Ubuntu):
status:	Invalid → Confirmed

Revision history for this message

Anti Mailer (antimailer) wrote on 2023-01-05 (last edit on 2023-01-05):

#10

Confirmed on Ubuntu 20.04 - kernel 5.4.0-135
The behaviour exits for about the last 5 kernel updates - but also a weak bios battery (wrong hw clock after resume) can be the reason for the problem.
The time sync happens only after several minutes.

Active/Running Service: systemd-timesyncd.service
(Disabled Service: systemd-networkd.service - netplan deactivated due to network problems)

Output of timedatectl immediately after resume:
               Local time: Mi 2023-01-04 04:46:17 CET
           Universal time: Mi 2023-01-04 03:46:17 UTC
                 RTC time: Mi 2023-01-04 03:46:18
                Time zone: Europe/Vienna (CET, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

Suggested solution:
Forcing an immediate time sync after resuming from hibernation.

Anti Mailer (antimailer) on 2023-01-09

Changed in systemd (Ubuntu):
status:	Confirmed → New

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntusystemd package

systemd-timesyncd doesn't sync time after resume from hibernate

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
systemd package