| 1 |
On Friday 20 November 2015 11:03:55 Mick wrote: |
| 2 |
> On Friday 20 Nov 2015 10:22:00 Peter Humphrey wrote: |
| 3 |
> > As I said, chronyd works on this four-core i5 box, just not on the |
| 4 |
> > two-core Atom. |
| 5 |
> |
| 6 |
> Have a look in the kernel of the Atom box and compare the RTC settings |
| 7 |
> between the two boxen. |
| 8 |
|
| 9 |
Well, that was instructive - thanks Mick. I found a couple of settings I'm |
| 10 |
sure I'd never have set knowingly, one of them a debug. After removing them |
| 11 |
I still get the caught-an-interrupt and failed-to-start errors, but now I |
| 12 |
find that chrony is apparently running well despite the errors. At any rate, |
| 13 |
it logs the selection of a source five seconds after it's started and the |
| 14 |
process is still running: |
| 15 |
|
| 16 |
2051 ? S 0:00 /usr/sbin/chronyd -f /etc/chrony/chrony.conf -s -r |
| 17 |
|
| 18 |
I've had another check through the kernel config, comparing it with the i5 |
| 19 |
config, and I've removed several more things that I think shouldn't be |
| 20 |
there, but it's made no further difference. |
| 21 |
|
| 22 |
-- |
| 23 |
Rgds |
| 24 |
Peter |
Archives