From: "Nick Bartos" <spam99-1EIjRwF9Gc5s5w19saIqfg@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: acpi=force safe?
Date: Thu, 5 Feb 2004 23:14:15 -0600 (CST) [thread overview]
Message-ID: <40678.65.28.18.238.1076044455.squirrel@mail.diamondcpu.com> (raw)
In-Reply-To:
I manage a little router distro that uses acpi to do a clean shutdown when
the power button is tapped. So really I am only using the powerdown &
button event features.
The problem I am having is that a lot of the boards I use are older, and
acpi does not get enabled by default. In the distro I want to keep
everything consistent, so if I fix this problem by forcing acpi on, I will
want to do it globally (for all systems).
I can do acpi=force, but I worry about causing stability issues.
I posted this question on the kernel devel list, and it was suggested to
me that I compile in basic acpi support button support, and nothing else.
Then I could do a acpi=force and just force on those features.
I am wondering if this will be safe, or if I could run into problems. I
don't want to sacrifice stability to have these features, but I would like
all my boxes to be consistent.
At least one of the systems is an asus p4b266 (most boards are asus),
which is on the blacklist for acpi=ht. I tried to force acpi on for this
board which did work, but it gave me a warning about overriding acpi=ht
(which I really don't know what that is supposed to do).
If this is OK, then what other features can I enable and safely force acpi
on? I would like to eventually implement fan speed and processor temp
monitoring (possibly other health monitoring). For some router only boxes
it may be good to reduce power consumption, but I don't want to push my
luck if it may not be safe.
I am using the latest 2.4.x pre at the moment.
Comments?
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next reply other threads:[~2004-02-06 5:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 5:14 Nick Bartos [this message]
[not found] ` <40678.65.28.18.238.1076044455.squirrel-gjzqEhKAtSBis2HOlLKa7kEOCMrvLtNR@public.gmane.org>
2004-02-06 5:40 ` acpi=force safe? Andi Kleen
[not found] ` <20040206064023.2a80a4dd.ak-l3A5Bk7waGM@public.gmane.org>
2004-02-06 12:54 ` Nick Bartos
-- strict thread matches above, loose matches on Subject: below --
2004-02-06 16:17 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB685-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org >
2004-02-06 17:16 ` Nick Bartos
[not found] ` <16644.65.164.3.3.1076087775.squirrel-gjzqEhKAtSBis2HOlLKa7kEOCMrvLtNR@public.gmane.org>
2004-02-06 21:13 ` Bruno Ducrot
[not found] ` <20040206211334.GH13262-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-02-06 21:49 ` Nick Bartos
[not found] ` <40747.65.164.3.3.1076104152.squirrel-gjzqEhKAtSBis2HOlLKa7kEOCMrvLtNR@public.gmane.org>
2004-02-07 3:31 ` Bruno Ducrot
2004-02-06 22:46 ` Nick Bartos
[not found] ` <24294.65.164.3.3.1076107609.squirrel-gjzqEhKAtSBis2HOlLKa7kEOCMrvLtNR@public.gmane.org>
2004-02-06 23:06 ` Bruno Ducrot
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=40678.65.28.18.238.1076044455.squirrel@mail.diamondcpu.com \
--to=spam99-1eijrwf9gc5s5w19saiqfg@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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