All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Mike Galbraith <efault@gmx.de>, "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>
Subject: Re: x86-tip tsc/tick gripage
Date: Wed, 26 Apr 2017 10:21:37 +0200	[thread overview]
Message-ID: <20170426082137.koj7q3ftfqw3o22u@gmail.com> (raw)
In-Reply-To: <1493194602.21594.4.camel@gmx.de>


* Mike Galbraith <efault@gmx.de> wrote:

> On Wed, 2017-04-26 at 10:02 +0200, Mike Galbraith wrote:
> 
> > tip v4.11-rc8-893-g8ec9e12aff06, trusty ole 8 socket (X7560) DL980 G7
> 
> Ew, DL980 then turned into unhappy RCU camper.
> 
> [  316.980923] basemono: 316956000000 ts->next_tick: 316380000000 dev->next_event: 316956005002
> [  689.893122] INFO: rcu_sched detected stalls on CPUs/tasks:

Probably RCU unrelated.

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?

Thanks,

	Ingo

  reply	other threads:[~2017-04-26  8:23 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 [this message]
2017-04-26  8:31     ` Mike Galbraith
2017-04-26  8:57       ` Mike Galbraith
2017-04-26  9:18         ` Mike Galbraith
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=20170426082137.koj7q3ftfqw3o22u@gmail.com \
    --to=mingo@kernel.org \
    --cc=efault@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 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.