From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-pm@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Venki Pallipadi <venkatesh.pallipadi@intel.com>,
Len Brown <lenb@kernel.org>,
Arjan van de Ven <arjan@infradead.org>
Subject: What's the right value for idle= (was: Re: [linux-pm] regression on P-II SMP)
Date: Sun, 21 Feb 2010 21:36:03 +0100 [thread overview]
Message-ID: <201002212136.03783.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.64.1002212117540.9624@axis700.grange>
On Sunday 21 February 2010, Guennadi Liakhovetski wrote:
> Hi
>
> my 2xP-II@400MHz locks up with 2.6.32(.X) unless I specify "idle=*" on the
> kernel command-line, where "*" is one of "poll," "mwait," "halt," and only
> "nomwait" indeed locks it up. Last kernel known to work was 2.6.25. So, it
> doesn't bother me all that much - I have a way to boot it, but maybe
> someone would be interested to fix this (this system already has a few
> quirks on the kernel command line, so, one more doesn't really hurt;)).
> What interests me more - which of those shall I be using? From
> Documentation/kernel-parameters.txt it looks like "mwait" should be best
> for me? Or should I be using "halt?" "Poll" does indeed fry CPUs - raises
> sys temperatures to 50 / 60 degrees C. Power-saving is not that much of a
> concern for me - I only run that system occasionally, but it shouldn't
> produce more heat than it must;) And since this system does have a broken
> ACPI (Compaq AP400), I wouldn't try to be too smart with it.
I guess "mwait" is the right one, but let's try to ask experts.
Rafael
next parent reply other threads:[~2010-02-21 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.1002212117540.9624@axis700.grange>
2010-02-21 20:36 ` Rafael J. Wysocki [this message]
2010-02-21 21:02 ` Pallipadi, Venkatesh
2010-02-22 21:52 ` Guennadi Liakhovetski
2010-02-21 21:11 ` Arjan van de Ven
2010-02-22 21:50 ` Guennadi Liakhovetski
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=201002212136.03783.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=arjan@infradead.org \
--cc=g.liakhovetski@gmx.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=venkatesh.pallipadi@intel.com \
/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
all inboxes | Powered by JetHome®