From: Ingo Molnar <mingo@elte.hu>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Avi Kivity <avi@redhat.com>, John Stultz <johnstul@us.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-kernel <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>
Subject: Re: phenom, amd780g, tsc, hpet, kvm, kernel -- who's at fault?
Date: Mon, 23 Mar 2009 16:41:37 +0100 [thread overview]
Message-ID: <20090323154137.GA1259@elte.hu> (raw)
In-Reply-To: <49C748EA.6040809@msgid.tls.msk.ru>
* Michael Tokarev <mjt@tls.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
next prev parent reply other threads:[~2009-03-23 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 21:06 phenom, amd780g, tsc, hpet, kvm, kernel -- who's at fault? Michael Tokarev
2009-03-23 8:04 ` Ingo Molnar
2009-03-23 8:31 ` Michael Tokarev
2009-03-23 15:41 ` Ingo Molnar [this message]
2009-03-23 16:04 ` Michael Tokarev
2009-03-23 16:13 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090323154137.GA1259@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=johnstul@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox