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
