← Back to team overview

kernel-packages team mailing list archive

[Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument


I have set get time from internet in the indicator datetime.
timedatectl says:
$ timedatectl 
      Local time: Tue 2016-04-12 10:54:21 BST
  Universal time: Tue 2016-04-12 09:54:21 UTC
        RTC time: Tue 2016-04-12 10:54:20
       Time zone: Europe/London (BST, +0100)
 Network time on: yes
NTP synchronized: no
 RTC in local TZ: yes

Warning: The system is configured to read the RTC time in the local time zone.
         This mode can not be fully supported. It will create various problems
         with time zone changes and daylight saving time adjustments. The RTC
         time is never updated, it relies on external facilities to maintain it.
         If at all possible, use RTC in UTC by calling
         'timedatectl set-local-rtc 0'.

Which is consistent, but I'm not sure if that's right. My /etc/adjtime
says LOCAL, and I do have WIndows 10 installed. I should check if
WIndows 10 can handle UTC hardware clock.

The journal has many errors about failing to call adjtime.

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  [regression]: Failed to call clock_adjtime(): Invalid argument

Status in linux package in Ubuntu:
Status in linux source package in Xenial:

Bug description:
  Steps to reproduce:

  1) Force a time delta
  date -s "now - 1 hour"
  2) Restart systemd-timesyncd to have it fix the time
  systemctl restart systemd-timesyncd

  Expected behavior:

  The clock should be back in sync.

  Actual (problematic) behavior:

  The clock stays out of sync because the call to clock_adjtime()

  # systemctl status systemd-timesyncd.service 
  ● 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
     Active: active (running) since Tue 2016-04-05 14:26:25 EDT; 1s ago
       Docs: man:systemd-timesyncd.service(8)
   Main PID: 11567 (systemd-timesyn)
     Status: "Synchronized to time server (ntp.ubuntu.com)."
      Tasks: 2 (limit: 512)
     Memory: 260.0K
        CPU: 15ms
     CGroup: /system.slice/systemd-timesyncd.service
             └─11567 /lib/systemd/systemd-timesyncd

  Apr 05 14:26:25 simon-laptop systemd[1]: Starting Network Time Synchronization...
  Apr 05 14:26:25 simon-laptop systemd[1]: Started Network Time Synchronization.
  Apr 05 14:26:25 simon-laptop systemd-timesyncd[11567]: Failed to call clock_adjtime(): Invalid argument
  Apr 05 14:26:25 simon-laptop systemd-timesyncd[11567]: Synchronized to time server (ntp.ubuntu.com).

  This problem doesn't happen when running kernel 4.4.0-16.32. Looking at the changelog of 4.4.0-17.33 it could be because of the new feature introduced in LP: #1519625.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-17-generic 4.4.0-17.33
  ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
  Uname: Linux 4.4.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
   /dev/snd/controlC0:  simon      5198 F.... pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
  Date: Tue Apr  5 14:21:22 2016
  HibernationDevice: RESUME=/dev/mapper/crypt-swap
  MachineType: LENOVO 2516CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-17-generic root=/dev/mapper/crypt-xroot ro quiet splash cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-xroot possible_cpus=4 nmi_watchdog=0 kaslr quiet splash cryptopts=target=crypt,source=/dev/sda1,lvm=crypt-xroot possible_cpus=4 nmi_watchdog=0 kaslr vt.handoff=7
   linux-restricted-modules-4.4.0-17-generic N/A
   linux-backports-modules-4.4.0-17-generic  N/A
   linux-firmware                            1.157
   0: phy0: Wireless LAN
   	Soft blocked: no
   	Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to: