From: Thomas Gleixner <tglx@linutronix.de>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: rc5+tip/master: Marking clocksource 'tsc' as unstable because the skew is too large:
Date: Thu, 30 Jun 2016 12:24:26 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1606301215410.3707@nanos> (raw)
In-Reply-To: <1467280185.9949.19.camel@gmail.com>
On Thu, 30 Jun 2016, Mike Galbraith wrote:
> On Thu, 2016-06-30 at 11:42 +0200, Thomas Gleixner wrote:
>
> > So there was no watchdog firing for 525 seconds ????
>
> Yup, seems so.
if that's fully reproducible can you please enable the timer and softirq
tracepoints along with your trace printks and stop the trace when that
watchdog triggers?
extra trace printk below.
thanks
tglx
diff --git a/kernel/time/timer.c b/kernel/time/timer.c
index 3e0c4e60bf6a..418c45ab5ad5 100644
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
@@ -1438,6 +1438,7 @@ static unsigned long __next_timer_interrupt(struct timer_base *base)
clk >>= LVL_CLK_SHIFT;
clk += adj;
}
+ trace_printk("next %lu\n", next);
return next;
}
next prev parent reply other threads:[~2016-06-30 11:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 20:06 Borislav Petkov
2016-06-29 17:16 ` Borislav Petkov
2016-06-30 7:57 ` Mike Galbraith
2016-06-30 8:41 ` Thomas Gleixner
2016-06-30 9:15 ` Mike Galbraith
2016-06-30 9:42 ` Thomas Gleixner
2016-06-30 9:49 ` Mike Galbraith
2016-06-30 10:24 ` Thomas Gleixner [this message]
2016-06-30 13:39 ` Mike Galbraith
2016-06-30 13:43 ` Thomas Gleixner
2016-06-30 14:27 ` Borislav Petkov
2016-06-30 14:29 ` Mike Galbraith
2016-06-30 20:11 ` Richard Cochran
2016-06-30 10:29 ` Mike Galbraith
2016-06-30 10:31 ` Thomas Gleixner
2016-06-30 8:40 ` Thomas Gleixner
2016-06-30 9:49 ` Borislav Petkov
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=alpine.DEB.2.11.1606301215410.3707@nanos \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=umgwanakikbuti@gmail.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®