| Re: [chrony-users] Fwd: Chrony malfunctioning at beaglebones |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Fwd: Chrony malfunctioning at beaglebones
- From: Nuno Gonçalves <nunojpg@xxxxxxxxx>
- Date: Fri, 21 Aug 2015 19:05:38 +0100
- Cc: dl4mea@xxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=XLdK0Hvw6VL0PUV8mr5RafCUMT4QbqCDgpPlK2rTWDs=; b=CoutJL4RFMfEaglRj5/UrWI+sSiIxeJY8UnspisGrcrE6ja110G6iNLYXhPklqQe/D puWnxw//sk9Lc9AXhONNQIrHZKwGXBFMf1TDTn1kPCXN7KHZuwhh8mBbJp/IRZ8oXraN xqrW2e/8w0dFamM0aWIsYFudc/5JhN927TC55PnWA2i1Cd/M9cTMN/cOk2+E/EPw8L9s DCLUFvHq8BE4QT2pG6BnQZilvN1G3JpEsUZ2Zlu/COnPXRe3M9KDtSqzg7FTcwQCi8zl IfM0NICfV9xw4Du0EedHr26dSL/T4CEPR6Rjx/ncUV4X+vTePlE61z4wq6XF5LgRBq5D 3ZQA==
Thank you so much. I've sent you the hostnames of a beaglebone white
and a beaglebone black that are set with your public key.
I took a few days while I confirmed what I could. In fact I've tried
several kernel versions and I see that up to 3.15.10-bone8 the clock
is working properly. After 3.16 and until the most recent 4.2 RC, it
is malfunctioning.
If you have a minute to login at the machines and are able to narrow
in any way which part of the kernel clocks is at fault it might be
easier have it fixed at the Linux level.
Otherwise you already diagnosed that this is not a Chrony issue and
I've confirmed that, so in that regard I couldn't ask for more chrony
support.
Thanks,
Nuno
On Tue, Aug 18, 2015 at 10:07 AM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> On Mon, Aug 17, 2015 at 09:02:53PM +0100, Nuno Gonçalves wrote:
>> After over 30 minutes the machine that have is not adjusting the clock
>> (servers with noselect), don't have any unreasonable estimate, but the
>> one adjusting the clock still have very large errors:
>
> If adding noselect made the sourcestats frequency and skew better,
> there is definitely something wrong in the clock control, my guess
> would be a kernel bug.
>
>> Note this machine have the clock so long in the past because the
>> default debian config does not enable steps, and the power on date is
>> Jan 1 2000. This doesn't make any difference.
>
> The -s option can be useful for that. When there is no RTC, it will
> set the time from the modification time of the driftfile so the time
> at least will stay monotonic across reboot.
>
>> Would you like remote access to the machine? I have a clean install of
>> debian, so you can hack it at will. If so please send me your public
>> key.
>
> Ok. I can try few tests and see if it's indeed a kernel problem. I'll
> send you a key.
>
> --
> Miroslav Lichvar
>
> --
> To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "unsubscribe" in the subject.
> For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
> with "help" in the subject.
> Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.
>
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.