From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752205AbcF3IoI (ORCPT ); Thu, 30 Jun 2016 04:44:08 -0400 Received: from www.linutronix.de ([62.245.132.108]:45734 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751782AbcF3IoF (ORCPT ); Thu, 30 Jun 2016 04:44:05 -0400 Date: Thu, 30 Jun 2016 10:41:43 +0200 (CEST) From: Thomas Gleixner To: Mike Galbraith cc: Borislav Petkov , Peter Zijlstra , x86-ml , lkml Subject: Re: rc5+tip/master: Marking clocksource 'tsc' as unstable because the skew is too large: In-Reply-To: <1467273448.9949.7.camel@gmail.com> Message-ID: References: <20160627200631.GA3678@pd.tnic> <20160629171619.GA3691@pd.tnic> <1467273448.9949.7.camel@gmail.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 30 Jun 2016, Mike Galbraith wrote: > On Wed, 2016-06-29 at 19:16 +0200, Borislav Petkov wrote: > > > And here it is again: > > > > ... > > [ 15.720833] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready > > [ 32.883077] clocksource: timekeeping watchdog on CPU1: Marking clocksource 'tsc' as unstable because the skew is too large: > > [ 32.896986] clocksource: 'acpi_pm' wd_now: 8e147 wd_last: 531b43 mask: ffffff > > [ 32.908834] clocksource: 'tsc' cs_now: 385f4b6d1e cs_last: 354328bcea mask: ffffffffffffffff > > [ 32.922293] clocksource: Switched to clocksource acpi_pm > > I met that too when testing, but only on my 8 socket box for whatever > reason. Putting tip back on the box and poking a bit while I beat up > rt kernels elsewhere, cs_nsec: 167001172874 wd_nsec: 0. (poke++) can i get the full data please including tsc frequency?