[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090323154137.GA1259@elte.hu>
Date: Mon, 23 Mar 2009 16:41:37 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Michael Tokarev <mjt@....msk.ru>
Cc: Avi Kivity <avi@...hat.com>, John Stultz <johnstul@...ibm.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux-kernel <linux-kernel@...r.kernel.org>,
KVM list <kvm@...r.kernel.org>
Subject: Re: phenom, amd780g, tsc, hpet, kvm, kernel -- who's at fault?
* Michael Tokarev <mjt@....msk.ru> wrote:
> Now, after quite some googling around, I tried to disable hpet,
> booting with hpet=disable parameter. And that one fixed all the
> problems at once. 7 days uptime, I stress-tested it several times,
> it works with TSC as timesource (still a problem within guests as
> those shows unstable TSC anyway) since boot, no issues logged.
> Even cpufreq works as expected...
>
> Note that i tried to disable hpet as clocksource several times but
> without any noticeable effect - kernel still used hpet and hpet2
> for something, and printed that scary "increasing min_delay"
> message on a semi-regular basis usually after the next 'stuck'
> state....
It could again go bad like it did before - those messages are signs
of HPET weirdnesses.
Probably your box's hpet needs to be blacklisted, so that it gets
disabled automatically on bootup.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists