Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#44044 - [chrony] Crashes on i686 with 'adjtimex failed for set_frequency...'
Attached to Project:
Community Packages
Opened by Mark (fiddlinmacx) - Wednesday, 04 March 2015, 14:31 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 04 March 2015, 14:44 GMT
Opened by Mark (fiddlinmacx) - Wednesday, 04 March 2015, 14:31 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 04 March 2015, 14:44 GMT
|
DetailsDescription: Chrony crashes with 'adjtimex failed for set_frequency, freq_ppm=-1.3203e+01 required_freq=1.3203e+01 required_tick=10000' immediately after starting
Additional info: * my system is completely up-to-date and this has been happening for a couple of weeks * http://chrony.tuxfamily.org/FAQ.html#question_7.1 talks about a mismatched HZ value in the kernel header files at compile time. Could this be the cause? * The only change from the default conf file is a line pointing chrony to my in-house time server. Steps to reproduce: - Start chrony via systemctl - 'systemctl status chrony' shows that it has crashed |
This task depends upon
Closed by Doug Newgard (Scimmia)
Wednesday, 04 March 2015, 14:44 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#44042
Wednesday, 04 March 2015, 14:44 GMT
Reason for closing: Duplicate
Additional comments about closing: