LKML Archive on
help / color / mirror / Atom feed
From: Thomas Gleixner <>
To: Nicholas Piggin <>
Cc: Linux Kernel Mailing List <>,
	Alexey Kardashevskiy <>,,,
	Frederic Weisbecker <>
Subject: Re: Occasionally losing the tick_sched_timer
Date: Tue, 10 Apr 2018 11:07:03 +0200 (CEST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, 10 Apr 2018, Nicholas Piggin wrote:
> On Tue, 10 Apr 2018 09:42:29 +0200 (CEST)
> Thomas Gleixner <> wrote:
> > > Thomas do you have any ideas on what we might look for, or if we can add
> > > some BUG_ON()s to catch this at its source?  
> > 
> > Not really. Tracing might be a more efficient tool that random BUG_ONs.
> Sure, we could try that. Any suggestions? timer events?

timer, hrtimer and the tick-sched stuff should be a good start. And make
sure to freeze the trace once you hit the fault case. tracing_off() is your



      reply	other threads:[~2018-04-10  9:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10  2:16 Occasionally losing the tick_sched_timer Nicholas Piggin
2018-04-10  7:42 ` Thomas Gleixner
2018-04-10  8:26   ` Nicholas Piggin
2018-04-10  9:07     ` Thomas Gleixner [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).