From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 65C181384B4 for ; Fri, 20 Nov 2015 17:02:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C1BB321C011; Fri, 20 Nov 2015 17:02:12 +0000 (UTC) Received: from smarthost01d.mail.zen.net.uk (smarthost01d.mail.zen.net.uk [212.23.1.7]) by pigeon.gentoo.org (Postfix) with ESMTP id A165821C011 for ; Fri, 20 Nov 2015 17:02:09 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost01d.mail.zen.net.uk with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Zzp4a-0005jh-Jg for gentoo-user@lists.gentoo.org; Fri, 20 Nov 2015 17:02:08 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Chrony-2.2 failing Date: Fri, 20 Nov 2015 17:02:07 +0000 Message-ID: <6525596.3DnbJ0jJH8@wstn> User-Agent: KMail/4.14.8 (Linux/4.1.12-gentoo; KDE/4.14.8; x86_64; ; ) In-Reply-To: <201511201104.04477.michaelkintzios@gmail.com> References: <2068412.puBuVpJXRl@wstn> <1688590.CMN6j3byKX@wstn> <201511201104.04477.michaelkintzios@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost01d-IP: [82.69.80.10] X-Archives-Salt: 0cea72e9-5424-43b3-becd-ea085f9f04ae X-Archives-Hash: 23b6cc9d503daf99956b10bb87f2fb5c On Friday 20 November 2015 11:03:55 Mick wrote: > On Friday 20 Nov 2015 10:22:00 Peter Humphrey wrote: > > As I said, chronyd works on this four-core i5 box, just not on the > > two-core Atom. > > Have a look in the kernel of the Atom box and compare the RTC settings > between the two boxen. Well, that was instructive - thanks Mick. I found a couple of settings I'm sure I'd never have set knowingly, one of them a debug. After removing them I still get the caught-an-interrupt and failed-to-start errors, but now I find that chrony is apparently running well despite the errors. At any rate, it logs the selection of a source five seconds after it's started and the process is still running: 2051 ? S 0:00 /usr/sbin/chronyd -f /etc/chrony/chrony.conf -s -r I've had another check through the kernel config, comparing it with the i5 config, and I've removed several more things that I think shouldn't be there, but it's made no further difference. -- Rgds Peter