From: brettrsears@gmail.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Chrony-2.2 failing
Date: Fri, 20 Nov 2015 19:39:03 +0000 [thread overview]
Message-ID: <874353563-1448048285-cardhu_decombobulator_blackberry.rim.net-691461868-@b18.c1.bise6.blackberry> (raw)
In-Reply-To: <564F5363.9000200@gmail.com>
B
Sent from my Verizon Wireless BlackBerry
-----Original Message-----
From: Alan McKinnon <alan.mckinnon@gmail.com>
Date: Fri, 20 Nov 2015 19:07:47
To: <gentoo-user@lists.gentoo.org>
Reply-to: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Chrony-2.2 failing
On 20/11/2015 19:02, Peter Humphrey wrote:
> 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.
>
Well that's interesting. I suggest at this point you ask at chrony's
support list - they'd know better than others what RTC settings their
software needs.
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2015-11-20 19:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 10:49 [gentoo-user] Chrony-2.2 failing Peter Humphrey
2015-11-19 17:06 ` Alexander Kapshuk
2015-11-19 17:17 ` Alan McKinnon
2015-11-20 10:22 ` Peter Humphrey
2015-11-20 11:03 ` Mick
2015-11-20 17:02 ` Peter Humphrey
2015-11-20 17:07 ` Alan McKinnon
2015-11-20 17:30 ` Mick
2015-11-21 9:59 ` Peter Humphrey
2015-11-24 15:24 ` Peter Humphrey
2015-11-25 17:05 ` Alan McKinnon
2015-11-26 10:39 ` Peter Humphrey
2015-11-26 13:00 ` Neil Bothwick
2015-11-26 14:00 ` Peter Humphrey
2015-11-26 15:04 ` Neil Bothwick
2015-11-26 15:12 ` Alan McKinnon
2015-11-27 9:33 ` Peter Humphrey
2015-11-20 19:39 ` brettrsears [this message]
2015-11-19 21:15 ` Marc Joliet
2015-11-20 9:24 ` Peter Humphrey
2015-12-07 18:41 ` Mick
2015-11-20 17:02 ` Dale
2015-11-20 17:06 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874353563-1448048285-cardhu_decombobulator_blackberry.rim.net-691461868-@b18.c1.bise6.blackberry \
--to=brettrsears@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox