Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1295815 > unrolled thread

Re: Skylake (XPS 13 9350) TSC is way off

Started byJon Masters <jonathan@jonmasters.org>
First post2015-12-21 09:20 +0100
Last post2015-12-21 23:00 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Skylake (XPS 13 9350) TSC is way off Jon Masters <jonathan@jonmasters.org> - 2015-12-21 09:20 +0100
    Re: Skylake (XPS 13 9350) TSC is way off John Stultz <john.stultz@linaro.org> - 2015-12-21 23:00 +0100

#1295815 — Re: Skylake (XPS 13 9350) TSC is way off

FromJon Masters <jonathan@jonmasters.org>
Date2015-12-21 09:20 +0100
SubjectRe: Skylake (XPS 13 9350) TSC is way off
Message-ID<qI3Rg-40k-7@gated-at.bofh.it>
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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1296240

FromJohn Stultz <john.stultz@linaro.org>
Date2015-12-21 23:00 +0100
Message-ID<qIgEP-3vy-45@gated-at.bofh.it>
In reply to#1295815
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web