public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Ingo Molnar <mingo@kernel.org>, "Paul E. McKenney" <paulmck@us.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: x86-tip tsc/tick gripage
Date: Wed, 26 Apr 2017 11:18:15 +0200	[thread overview]
Message-ID: <1493198295.21594.11.camel@gmx.de> (raw)
In-Reply-To: <1493197062.21594.8.camel@gmx.de>

On Wed, 2017-04-26 at 10:57 +0200, Mike Galbraith wrote:
> On Wed, 2017-04-26 at 10:31 +0200, Mike Galbraith wrote:
> > On Wed, 2017-04-26 at 10:21 +0200, Ingo Molnar wrote:
> > 
> > > I have temporarily removed the current timers/urgent lineup from -tip:
> > > 
> > >  098991fccfc7: nohz: Print more debug info in tick_nohz_stop_sched_tick()
> > >  22aa2ad45fd8: tick: Make sure tick timer is active when bypassing reprogramming
> > >  d58bd60c773d: nohz: Fix again collision between tick and other hrtimers
> > > 
> > > ... and have reintegrated tip:master, so it should be back to working I think.
> > > 
> > > Does this solve the warning and the RCU stalls on your boxes?
> > 
> > (both boxen building)
> 
> (oh come on, boot already... zzz)
> 
> Both still lose their TSC.

Aw crap, and the DL980 RCU stalled while idling again.

> [   11.982468] tsc: Refined TSC clocksource calibration: 2260.999 MHz
> [   11.994275] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x20974a4d8bb, max_idle_ns: 440795246623 ns
> [   13.064172] clocksource: Switched to clocksource tsc
> [  240.247851] clocksource: timekeeping watchdog on CPU23: Marking clocksource 'tsc' as unstable because the skew is too large:
> [  240.462501] clocksource:                       'tsc' cs_now: 108fe5be09f cs_last: b90a6a0676 mask: ffffffffffffffff
> [  240.675057] tsc: Marking TSC unstable due to clocksource watchdog
> 
> [  349.192460] clocksource: timekeeping watchdog on CPU63: Marking clocksource 'tsc' as unstable because the skew is too large:
> [  349.217756] clocksource:                       'hpet' wd_now: 2bb0dad7 wd_last: 5d9ac241 mask: ffffffff
> [  349.239021] clocksource:                       'tsc' cs_now: d2413ebfc1c28 cs_last: d2387b328a38c mask: ffffffffffffffff
> [  349.263525] sched_clock: Marking unstable (349228856508, 34664619)<-(351146178141, -1882657014)
> [  349.283245] tsc: Marking TSC unstable due to clocksource watchdog
> [  349.298075] clocksource: Switched to clocksource hpet

  reply	other threads:[~2017-04-26  9:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26  8:02 x86-tip tsc/tick gripage Mike Galbraith
2017-04-26  8:16 ` Mike Galbraith
2017-04-26  8:21   ` Ingo Molnar
2017-04-26  8:31     ` Mike Galbraith
2017-04-26  8:57       ` Mike Galbraith
2017-04-26  9:18         ` Mike Galbraith [this message]
2017-04-26 10:26         ` Peter Zijlstra
2017-04-26 11:39           ` Mike Galbraith
2017-04-26 12:30             ` Mike Galbraith
2017-04-26 18:13               ` Mike Galbraith
2017-04-27  5:26               ` Mike Galbraith
2017-04-29 16:06               ` [patch] timer: Fix timers_update_migration(), and call it in tmigr_init() Mike Galbraith
2017-04-29 18:06                 ` Paul E. McKenney
2017-04-29 18:20                   ` Mike Galbraith
2017-04-29 21:45                     ` Paul E. McKenney
2017-04-30  1:21                       ` Mike Galbraith
2017-04-30  3:43                         ` Paul E. McKenney
2017-04-30  4:20                           ` Mike Galbraith
2017-04-30  4:36                             ` Paul E. McKenney
2017-04-30 22:41                               ` Paul E. McKenney
2017-05-01  7:54                                 ` Thomas Gleixner
2017-05-01 19:33                                   ` Paul E. McKenney
2017-04-30  5:07                             ` Mike Galbraith
2017-04-28  7:35             ` [patch] Re: x86-tip tsc/tick gripage Mike Galbraith
2017-04-28  8:45               ` Mike Galbraith
2017-04-28 14:17                 ` Mike Galbraith

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=1493198295.21594.11.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=paulmck@us.ibm.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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