From: Bill Davidsen <davidsen@tmr.com>
To: Len Brown <len.brown@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Hyper-threaded pickle
Date: Tue, 09 Mar 2004 15:14:06 -0500 [thread overview]
Message-ID: <404E258E.1030600@tmr.com> (raw)
In-Reply-To: <1xlbI-6Rl-5@gated-at.bofh.it>
Len Brown wrote:
>>>Re: old systems -- we use dmi_scan to disable ACPI on systems by default
>>>on systems older than 1/1/2001.
>>
>>What happens for the no-DMI case?
>
>
> When DMI is not present, dmi_scan is a no-op -- so ACPI will run in
> whatever default the system is set to -- eg. "off" for FC1, and "on" for
> FC2-test1.
>
> We've found in practice that dmi_scan has been pretty effective at
> identifying the set of systems new enough to have an ACPI enabled BIOS
> but old enough that the ACPI implementation is hopeless. Though we've
> had many reports of 1/1/2001 being a bit *too* conservative -- disabling
> ACPI on systems where ACPI works fine. Indeed, there is a bugzilla
> requesting a "white-list" to enable exceptions to this date. I'm not
> enthusiastic about that plan, however. I figure there are more 3-year
> old boxes that have been running Linux w/o ACPI than there are those
> which have; and I'd rather spend my ergs on the current and upcoming
> boxes where vendors are more willing to update a broken BIOS...
Even though I have some boxes which are hurt by this, I have to agree,
although I wouldn't be unhappy if there were a few more options to
enable just parts of ACPI. There are more important things, however, and
since I can live with ACPI=force or no acpi at all it's an annoyance
rather than an issue.
I have a few machines which are never going to 2.6 because their ACPI is
totally broken and 2.6 APC no longer functions to turn the machine off.
Since I expect 2.4 to be viable longer than the machines, I have no
issues with that, either. If I don't have time to look at it why should
I ask anyone else?
next parent reply other threads:[~2004-03-09 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1wfBD-6GI-9@gated-at.bofh.it>
[not found] ` <1whjQ-8sH-25@gated-at.bofh.it>
[not found] ` <1wMeo-Sr-3@gated-at.bofh.it>
[not found] ` <1xlbI-6Rl-5@gated-at.bofh.it>
2004-03-09 20:14 ` Bill Davidsen [this message]
2004-03-14 3:35 ` Hyper-threaded pickle Andi Kleen
2004-03-05 4:52 Jeff Garzik
2004-03-05 6:44 ` Len Brown
2004-03-06 15:40 ` Jeff Garzik
2004-03-08 5:02 ` Len Brown
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=404E258E.1030600@tmr.com \
--to=davidsen@tmr.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.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