On Wed, 3 Dec 2014, Dave Jones wrote:
> On Thu, Dec 04, 2014 at 12:49:29AM +0100, Thomas Gleixner wrote:
>
> > > I just got
> > >
> > > [ 1472.614433] Clocksource tsc unstable (delta = -26373048906 ns)
> > >
> > > without any sign of the pr_err above.
> >
> > Bah. Would have been too simple ....
> >
> > Could you please run Ingos time-warp test on that machine for a while?
> >
> > http://people.redhat.com/mingo/time-warp-test/time-warp-test.c
> >
> > Please change:
> >
> > - #define TEST_CLOCK 0
> > + #define TEST_CLOCK 1
>
> Seems to be 32-bit only, so I built it with -m32. I assume that's ok?
I has some _x86_64 ifdeffery, but I'm too tired to stare at that
now. 32bit should show the issue as well.
> Also, should I run it in isolation, with nothing else going on,
> or under load where I see problems ?
isolated is usually the best thing as it has the highest density of
reads.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
