Re: [bisected] Clocksource tsc unstable git

[Borislav Petkov]

On Fri, Oct 29, 2010 at 04:30:13AM -0400, Markus Trippelsdorf wrote:
> > Well, what do you know, the temporary "slowdown" triggered on my setup
> > too. After waiting a minute maybe, the machine recovered and guess what
> > appeared in dmesg:
> > 
> > [44729.650859] Clocksource tsc unstable (delta = -8615263009 ns)
> > [44729.656229] Switching to clocksource hpet
> > 
> > I've reverted the changeset above and will run without it to check
> > whether it makes any difference.
> 
> After further testing I've found out that the tsc- and the kvm-issue are
> unrelated. IOW I get these "slowdowns" even with 34f971f6f7988be4
> reverted.

hmm, I'll run with 34f971f6f798 reverted for a while just to confirm
your observations...

> I guess John was right when he wrote:
> > From your dmesg, I'd guess the hpet is the watchdog clocksource, so I
> > be on the lookout for hpet related changes.
> >
> > Maybe does reverting 995bd3bb5c78f3ff71339803c0b8337ed36d64fb hide the
> > issue?  
> 
> Because with 995bd3bb5c78f reverted I never had a single "slowdown" here.

That's strange, when we tested this one everything seemed fine so I
guess this is one of those bugs which appear later, just as if out of
nowhere.

Thomas, could it be that SMI fires in between the HPET write and
subsequent read:

	hpet_writel(cnt, HPET_Tn_CMP(timer));

	...

	res = (s32)(cnt - hpet_readl(HPET_COUNTER));

causing the -ETIME and thus a wait for HPET wraparound? My machine at
least does SMI-initiated C1E so it could very well be the problem.

Markus, can you verify this on your system by compiling x86info from
git://git.choralone.org/git/x86info and doing

./lsmsr Int

as root?

Thanks.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/