All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Masters <jonathan@jonmasters.org>
To: John Stultz <john.stultz@linaro.org>, Andy Lutomirski <luto@kernel.org>
Cc: "Brown, Len" <len.brown@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	X86 ML <x86@kernel.org>,
	"Hunter, Adrian" <adrian.hunter@intel.com>
Subject: Re: Skylake (XPS 13 9350) TSC is way off
Date: Mon, 21 Dec 2015 03:10:19 -0500	[thread overview]
Message-ID: <5677B3EB.9030908@jonmasters.org> (raw)
In-Reply-To: <CALAqxLUdnvkHP9qKFmAkHfLy=5vz-GOTz9dJx2bDQMj9TqzZbA@mail.gmail.com>

On 12/2/15, 6:55 PM, John Stultz wrote:
> On Wed, Dec 2, 2015 at 3:42 PM, Andy Lutomirski <luto@kernel.org> wrote:

>>> On a hunch, are you running chrony instead of ntpd?
>>
>> Yes, this is indeed chrony.
>
> Ok. I'll have to look closer. The last time that message came up it
> was in a report of a bug that chrony uncovered with the internal
> correction being too slow. I know chrony is much more aggressive
> compared to ntpd in tweaking the freq value for the initial converging
> correction at startup, so maybe that along with something else is
> causing us to get out of spec.

Can you copy me on followup? I'm seeing similar behavior with chrony on 
recent kernels on a couple of different ARM server prototype systems.

Jon.


  reply	other threads:[~2015-12-21  8:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 20:06 Skylake (XPS 13 9350) TSC is way off Andy Lutomirski
2015-12-02 22:52 ` Brown, Len
2015-12-02 23:25   ` Andy Lutomirski
2015-12-02 23:38     ` John Stultz
2015-12-02 23:42       ` Andy Lutomirski
2015-12-02 23:55         ` John Stultz
2015-12-21  8:10           ` Jon Masters [this message]
2015-12-21 21:56             ` John Stultz
2015-12-02 23:42       ` John Stultz
2015-12-02 23:59         ` Andy Lutomirski
2015-12-03  3:25     ` Brown, Len

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=5677B3EB.9030908@jonmasters.org \
    --to=jonathan@jonmasters.org \
    --cc=adrian.hunter@intel.com \
    --cc=john.stultz@linaro.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.