From: John Stultz <john.stultz@linaro.org>
To: Jon Masters <jonathan@jonmasters.org>
Cc: Andy Lutomirski <luto@kernel.org>,
"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 13:56:24 -0800 [thread overview]
Message-ID: <CALAqxLXjH09M87nO5HOBLzLZ5qnb_-oQ0D17PpQWW4Z6L57ohg@mail.gmail.com> (raw)
In-Reply-To: <5677B3EB.9030908@jonmasters.org>
On Mon, Dec 21, 2015 at 12:10 AM, Jon Masters <jonathan@jonmasters.org> wrote:
> 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.
A patch for this just landed in tip/timers/core and is pending for 4.5
http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=ec02b076ceab63f99e5b3d80fd223d777266c236
thanks
-john
next prev parent reply other threads:[~2015-12-21 21:56 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
2015-12-21 21:56 ` John Stultz [this message]
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=CALAqxLXjH09M87nO5HOBLzLZ5qnb_-oQ0D17PpQWW4Z6L57ohg@mail.gmail.com \
--to=john.stultz@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=jonathan@jonmasters.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).