From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: phenom, amd780g, tsc, hpet, kvm, kernel -- who's at fault? Date: Mon, 23 Mar 2009 16:41:37 +0100 Message-ID: <20090323154137.GA1259@elte.hu> References: <49BACABE.7060003@msgid.tls.msk.ru> <20090323080441.GA27170@elte.hu> <49C748EA.6040809@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , John Stultz , Thomas Gleixner , Andrew Morton , Linux-kernel , KVM list To: Michael Tokarev Return-path: Received: from mx3.mail.elte.hu ([157.181.1.138]:36890 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754941AbZCWPmJ (ORCPT ); Mon, 23 Mar 2009 11:42:09 -0400 Content-Disposition: inline In-Reply-To: <49C748EA.6040809@msgid.tls.msk.ru> Sender: kvm-owner@vger.kernel.org List-ID: * Michael Tokarev 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