From: Mike Galbraith <efault@gmx.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: x86-tip tsc/tick gripage
Date: Thu, 27 Apr 2017 07:26:55 +0200 [thread overview]
Message-ID: <1493270815.4154.18.camel@gmx.de> (raw)
In-Reply-To: <1493209836.21594.29.camel@gmx.de>
On Wed, 2017-04-26 at 14:30 +0200, Mike Galbraith wrote:
> On Wed, 2017-04-26 at 13:39 +0200, Mike Galbraith wrote:
> > On Wed, 2017-04-26 at 12:26 +0200, Peter Zijlstra wrote:
> > > On Wed, Apr 26, 2017 at 10:57:42AM +0200, Mike Galbraith wrote:
> > >
> > > > Both still lose their TSC.
> > > >
> > > > [ 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
> > >
> > >
> > > And they didn't use to? We don't typically write to TSC or TSC_ADJUST
> > > and thus would not cause such behaviour.
> >
> > Nope.
>
> DL980 seems perfectly happy with master.today.. so off we go.
hm, this bit of huge trace looks less than wonderful.
<idle>-0 [041] ..s2 317.304657: timer_expire_entry: timer=ffffffff820d6600 function=clocksource_watchdog now=4294971392
<idle>-0 [041] d.s4 317.304660: timer_start: timer=ffffffff820d6600 function=clocksource_watchdog expires=4294916631 [timeout=-54761] cpu=42 idx=19 flags=
<idle>-0 [041] ..s2 317.304660: timer_expire_exit: timer=ffffffff820d6600 ^^^^^^^^^^^^^^
1.1 megalines later, we finally meet function=clocksource_watchdog
again, and have a cow.
<idle>-0 [043] d.s3 489.511620: timer_cancel: timer=ffffffff820d6600
<idle>-0 [043] ..s2 489.511621: timer_expire_entry: timer=ffffffff820d6600 function=clocksource_watchdog now=4295014443
<idle>-0 [043] ..s2 489.511628: clocksource_watchdog: timekeeping watchdog on CPU43: Marking clocksource 'tsc' as unstable because the skew is too large:
<idle>-0 [043] ..s2 489.511630: clocksource_watchdog: 'hpet' wd_now: a1cbfa1a wd_last: ed7acfe mask: ffffffff
<idle>-0 [043] ..s2 489.511630: clocksource_watchdog: 'tsc' cs_now: 1c24ee60f22 cs_last: 167a92e836f mask: ffffffffffffffff
next prev parent reply other threads:[~2017-04-27 5:27 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
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 [this message]
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=1493270815.4154.18.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@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