Arch Linux

linux 3.18.6-1, but now fixed in linux 3.19.1-1.

Please see Red Hat Bug, reported 2015-02-01 19:31 EST:
"Bug 1188074 - adjtimex fails with kernel-3.18.5 when ca"
https://bugzilla.redhat.com/show_bug.cgi?id=1188074

Uniquely effects 32bit systems, i686 and ARM builds, but not x86_64. The symptom is that chronyd will report something like:

chronyd[722]: Frequency -35.554 +/- 1.838 ppm read from /var/lib/chrony/drift
chronyd[722]: Fatal error : adjtimex failed for set_frequency, freq_ppm=-3.5554e+01 required_freq=3.5554e+01 required_tick=10000

There is a patch from Red Hat against kernel commit 5e5aeb4367b450a28f447f6d5ab57d8f2ab16a5f, from CommitDate: Wed Jan 7 09:50:32 2015 -0800,

http://git.kernel.org/linus/;a=commit;h=5e5aeb4367b450a28f447f6d5ab57d8f2ab16a5f

--- a/kernel/time/ntp.c
+++ b/kernel/time/ntp.c
@@ -634,9 +634,9 @@ int ntp_validate_timex(struct timex *txc)
return -EPERM;

if (txc->modes & ADJ_FREQUENCY) {
- if (LONG_MIN / PPM_SCALE > txc->freq)
+ if (-MAXFREQ_SCALED / PPM_SCALE > txc->freq)
return -EINVAL;
- if (LONG_MAX / PPM_SCALE < txc->freq)
+ if (MAXFREQ_SCALED / PPM_SCALE < txc->freq)
return -EINVAL;
}

This is similar to  FS#43689 , for kernel 3.18.5, but the kernel is still broken, at linux 3.18.6-1.
Chrony still fails to start.

This issue was reported to lkml on 2015 Feb 02,
https://lkml.org/lkml/2015/2/2/536

I confirm that this issue has been fixed in linux 3.19.1-1.

Should we continue to wait on upstream for 3.18.6? Or just go with 3.19.1?