From: Borislav Petkov <bp@alien8.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>, x86-ml <x86@kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: rc5+tip/master: Marking clocksource 'tsc' as unstable because the skew is too large:
Date: Mon, 27 Jun 2016 22:06:31 +0200 [thread overview]
Message-ID: <20160627200631.GA3678@pd.tnic> (raw)
Hey Thomas,
Just started seeing this now during testing of Rafael's s/r fix:
[ 24.973955] clocksource: timekeeping watchdog on CPU3: Marking clocksource 'tsc' as unstable because the skew is too large:
[ 24.987744] clocksource: 'acpi_pm' wd_now: 2df835 wd_last: a6bb64 mask: ffffff
[ 24.999587] clocksource: 'tsc' cs_now: 2bbe793d1e cs_last: 296e28763c mask: ffffffffffffffff
[ 25.013400] clocksource: Switched to clocksource acpi_pm
In the previous boot it was CPU1.
And kernel is rc5+tip/master.
Any suggestions are always welcome.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next reply other threads:[~2016-06-27 20:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 20:06 Borislav Petkov [this message]
2016-06-29 17:16 ` rc5+tip/master: Marking clocksource 'tsc' as unstable because the skew is too large: 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
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=20160627200631.GA3678@pd.tnic \
--to=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 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.