kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #170610
[Bug 1566465] [NEW] [regression]: Failed to call clock_adjtime(): Invalid argument
Public bug reported:
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() failed.
# 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
└─disable-with-time-daemon.conf
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 172.24.21.1:123 (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 172.24.21.1:123 (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
AudioDevicesInUse:
USER PID ACCESS COMMAND
/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
RelatedPackageVersions:
linux-restricted-modules-4.4.0-17-generic N/A
linux-backports-modules-4.4.0-17-generic N/A
linux-firmware 1.157
RfKill:
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
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug package-from-proposed regression-proposed xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1566465
Title:
[regression]: Failed to call clock_adjtime(): Invalid argument
Status in linux package in Ubuntu:
Confirmed
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()
failed.
# 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
└─disable-with-time-daemon.conf
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 172.24.21.1:123 (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 172.24.21.1:123 (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
AudioDevicesInUse:
USER PID ACCESS COMMAND
/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
RelatedPackageVersions:
linux-restricted-modules-4.4.0-17-generic N/A
linux-backports-modules-4.4.0-17-generic N/A
linux-firmware 1.157
RfKill:
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:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566465/+subscriptions
Follow ups
-
[Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument
From: Ales Kvapil, 2016-04-24
-
[Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument
From: Launchpad Bug Tracker, 2016-04-19
-
[Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument
From: Simon Déziel, 2016-04-17
-
[Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument
From: Tim Gardner, 2016-04-15
-
[Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument
From: Tim Gardner, 2016-04-14
-
[Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument
From: Fabian Grünbichler, 2016-04-14
-
[Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument
From: Dimitri John Ledkov, 2016-04-12
-
[Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument
From: Dimitri John Ledkov, 2016-04-12
-
[Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument
From: Mikko Pesari, 2016-04-07
-
[Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument
From: Joseph Salisbury, 2016-04-05
-
[Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument
From: Joseph Salisbury, 2016-04-05
-
[Bug 1566465] Re: [regression]: Failed to call clock_adjtime(): Invalid argument
From: Launchpad Bug Tracker, 2016-04-05