Re: rc5+tip/master: Marking clocksource 'tsc' as unstable because the skew is too large:

[Thomas Gleixner]

On Thu, 30 Jun 2016, Mike Galbraith wrote:

> On Wed, 2016-06-29 at 19:16 +0200, Borislav Petkov wrote:
> 
> > 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
> 
> I met that too when testing, but only on my 8 socket box for whatever
> reason.  Putting tip back on the box and poking a bit while I beat up
> rt kernels elsewhere, cs_nsec: 167001172874 wd_nsec: 0.  (poke++)

can i get the full data please including tsc frequency?