From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
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:29:44 +0200 [thread overview]
Message-ID: <1467282584.9949.25.camel@gmail.com> (raw)
In-Reply-To: <1467280185.9949.19.camel@gmail.com>
On Thu, 2016-06-30 at 11:49 +0200, 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.
"fired" at the top, the other above if (atomic_read(&watchdog_reset...
vogelweide:/sys/kernel/debug/tracing/:[0]# tail trace
<idle>-0 [055] ..s. 324.428369: clocksource_watchdog: fired
<idle>-0 [055] ..s. 324.428374: clocksource_watchdog: cs_nsec: 16032486 wd_nsec: 16032765 delta: 279 wdnow: 351147182 wdlast: 350917622 watchdog->mask: ffffffff
nis-5876 [056] ..s. 324.428403: clocksource_watchdog: fired
nis-5876 [056] ..s. 324.428412: clocksource_watchdog: cs_nsec: 37227 wd_nsec: 37574 delta: 347 wdnow: 351147720 wdlast: 351147182 watchdog->mask: ffffffff
<idle>-0 [057] ..s. 324.428428: clocksource_watchdog: fired
<idle>-0 [057] ..s. 324.428433: clocksource_watchdog: cs_nsec: 21938 wd_nsec: 21301 delta: 637 wdnow: 351148025 wdlast: 351147720 watchdog->mask: ffffffff
automount-5406 [059] ..s. 394.446498: clocksource_watchdog: fired
automount-5406 [059] ..s. 394.446503: clocksource_watchdog: cs_nsec: 26670906785 wd_nsec: 26670888107 delta: 18678 wdnow: 1353664854 wdlast: 971786304 watchdog->mask: ffffffff
ypbind-5385 [060] ..s. 561.325932: clocksource_watchdog: fired
ypbind-5385 [060] ..s. 561.325937: clocksource_watchdog: cs_nsec: 166877142176 wd_nsec: 0 delta: 166877142176 wdnow: 3743040056 wdlast: 1353664854 watchdog->mask: ffffffff
vogelweide:/sys/kernel/debug/tracing/:[0]#
next prev parent reply other threads:[~2016-06-30 10:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 20:06 rc5+tip/master: Marking clocksource 'tsc' as unstable because the skew is too large: 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
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 [this message]
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=1467282584.9949.25.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).