FS#43689 - [linux] Chrony fails to start with kernel 3.18.5 in i686
Attached to Project:
Arch Linux
Opened by Mike Cloaked (mcloaked) - Tuesday, 03 February 2015, 16:16 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 09 April 2015, 09:22 GMT
Opened by Mike Cloaked (mcloaked) - Tuesday, 03 February 2015, 16:16 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 09 April 2015, 09:22 GMT
|
Details
Description: After updating kernel to 3.18.5-1-ARCH in i686
netbook chrony fails to start at boot
Additional info: * package version(s) linux 3.18.5-1 chrony 1.31-1 * config and/or log files etc. msung2w.mdc.sapience.com sddm[392]: Socket server starting... [root@samsung2w ~]# systemctl status chrony ● chrony.service - Chrony Network Time Daemon Loaded: loaded (/usr/lib/systemd/system/chrony.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2015-02-03 16:00:51 GMT; 12min ago Process: 386 ExecStart=/usr/bin/chronyd -u chrony (code=exited, status=1/FAILURE) Feb 03 16:00:51 samsung2w.mdc.sapience.com chronyd[394]: chronyd version 1.31 starting Feb 03 16:00:51 samsung2w.mdc.sapience.com chronyd[394]: Frequency 27.160 +/- 1.973 ppm read ...t Feb 03 16:00:51 samsung2w.mdc.sapience.com systemd[1]: chrony.service: control process exite...=1 Feb 03 16:00:51 samsung2w.mdc.sapience.com systemd[1]: Failed to start Chrony Network Time D...n. Feb 03 16:00:51 samsung2w.mdc.sapience.com systemd[1]: Unit chrony.service entered failed state. Feb 03 16:00:51 samsung2w.mdc.sapience.com systemd[1]: chrony.service failed. Feb 03 16:00:51 samsung2w.mdc.sapience.com chronyd[386]: adjtimex failed for set_frequency, f Steps to reproduce: On an i686 system where chrony normally started at boot without issue update kernel to 3.18.5-1 and reboot - then check status of chrony This is the same issue as reported by other distributions and in LKML with the same adjtimex failure: https://lkml.org/lkml/2015/2/2/536 This will likely be fixed upstream but reporting here for tracking in the arch bug list also. |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Thursday, 09 April 2015, 09:22 GMT
Reason for closing: Fixed
Additional comments about closing: 3.19.1
Thursday, 09 April 2015, 09:22 GMT
Reason for closing: Fixed
Additional comments about closing: 3.19.1
I will test chrony on my i686 machine in the next few days to confirm if fixed or not, and then report back here.