mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Re: rc5+tip/master: Marking clocksource 'tsc' as unstable because the skew is too large:
Date: Wed, 29 Jun 2016 19:16:19 +0200	[thread overview]
Message-ID: <20160629171619.GA3691@pd.tnic> (raw)
In-Reply-To: <20160627200631.GA3678@pd.tnic>

On Mon, Jun 27, 2016 at 10:06:31PM +0200, Borislav Petkov wrote:
> 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 here it is again:

...
[   15.720833] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   32.883077] clocksource: timekeeping watchdog on CPU1: Marking clocksource 'tsc' as unstable because the skew is too large:
[   32.896986] clocksource:                       'acpi_pm' wd_now: 8e147 wd_last: 531b43 mask: ffffff
[   32.908834] clocksource:                       'tsc' cs_now: 385f4b6d1e cs_last: 354328bcea mask: ffffffffffffffff
[   32.922293] clocksource: Switched to clocksource acpi_pm

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.

  reply	other threads:[~2016-06-29 17:16 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 [this message]
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=20160629171619.GA3691@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 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®