[Bug 1564951] Re: systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument

[Mikko Pesari]

This seems to be a kernel issue. On my both laptops, with the current
4.4.0-17 kernel systemd-timesyncd fails to adjust time or does it only
once, which is interesting. With the previous kernel 4.4.0-16 it works
just fine.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1564951

Title:
  systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading systemd from 229-3ubuntu1 to 229-3ubuntu2, I noticed
  this on one of my VM:

    systemd-timesyncd: Failed to call clock_adjtime(): Invalid argument

  systemd-timesyncd says it was able to sync the clock but also report
  failures:

  # systemctl status systemd-timesyncd
  ● systemd-timesyncd.service - Network Time Synchronization
     Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled)
    Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
             └─disable-with-time-daemon.conf
     Active: active (running) since Fri 2016-04-01 10:55:09 EDT; 3s ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 2523 (systemd-timesyn)
     Status: "Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com)."
      Tasks: 2 (limit: 512)
     CGroup: /system.slice/systemd-timesyncd.service
             └─2523 /lib/systemd/systemd-timesyncd

  Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Starting Network Time Synchronization...
  Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd[1]: Started Network Time Synchronization.
  Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Failed to call clock_adjtime(): Invalid argument
  Apr 01 10:55:09 ipsec.p2p.sdeziel.info systemd-timesyncd[2523]: Synchronized to time server 172.24.21.1:123 (ntp.ubuntu.com).

  The clock_adjtime error repeats every ~30 seconds after that.

  Oddly, I cannot reproduce this on my physical machine, only on this
  VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Fri Apr  1 10:50:35 2016
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: root=UUID=ce88e7e4-836f-42d6-8e39-4bc8abd23541 ro console=hvc0 kaslr
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Bochs
  dmi.bios.version: Bochs
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-2.0:cvnBochs:ct1:cvr:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-2.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1564951/+subscriptions