Re: WARNING: Adjusting tsc more then 11%

[John Stultz]

On Mon, 2012-03-05 at 10:44 -0500, Dave Jones wrote:
> John,
> We've had a number of reports the last few weeks triggering
> this warning that you added back in October.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=798600
> https://bugzilla.redhat.com/show_bug.cgi?id=799215
> https://bugzilla.redhat.com/show_bug.cgi?id=799745
> https://bugzilla.redhat.com/show_bug.cgi?id=799872
> 
> any idea what could have changed to start tripping that up ?
> 
> The reports seem to have started around 3.3-rc4.

Huh. No I don't know what would have started causing such a warning. I
had expected that there would be some edge hardware that might trip that
warning, but I'd expect the noise to start there w/ 3.2 after it was
introduced. There's only been spelling & comment changes to the
timekeeping core in the 3.3-rc series.

Looking at the logs, I'm curious if maybe some of the nohz changes have
tweaked us here. If we're hitting longer idle times, it might be
possible the ntp error could accumulate to be larger, and then the
kernel's frequency adjustments might end up trying to adjust for more
then 11%. 

Its also interesting its only popping up on hardware using the TSC.
acpi_pm can only do short idle times, so it wouldn't show up here, but
hpet could do reasonably long idles, so I'd think we'd also see some
similar hpet warnings.

Do you know if this is an occasional thing on any of the affected
hardware, or if it happens after every reboot?

Are any of the reported boxes systems you have access to in order to
reproduce?

thanks
-john


--
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/