From: Robert Hancock <hancockr@shaw.ca>
To: Christian Kujau <christian@g-house.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Cc: Len Brown <lenb@kernel.org>
Subject: Re: 2.6.20.4: NETDEV WATCHDOG and lockups
Date: Tue, 03 Apr 2007 08:28:29 -0600 [thread overview]
Message-ID: <4612648D.4090904@shaw.ca> (raw)
In-Reply-To: <fa.G7qJfhdvOynxlffny+Xc1kIaqBY@ifi.uio.no>
Christian Kujau wrote:
> Len et al., do you even suggest to use ACPI on a server system at all? I
> myself always thought of ACPI being evil and to avoid when possible
> (thus switching it off completely on a serversystem).
These days I think it's usually best to have ACPI on with current
systems. Although it's not as bad with servers, many machines are
designed to run only Windows (which normally always uses ACPI) and
simply aren't tested well or at all with ACPI disabled so you can run
into a lot of problems which are just bugs in the BIOS, etc.
Also, on the server side, if ACPI is disabled you can't take advantage
of CPU clock frequency scaling to save power.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-04-03 14:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.P3upyx4QAcXHtp/c/s+b4/cKk5w@ifi.uio.no>
[not found] ` <fa.u/RjoL2ybMMaAY+GDfTzm7jO5d0@ifi.uio.no>
[not found] ` <fa.G7qJfhdvOynxlffny+Xc1kIaqBY@ifi.uio.no>
2007-04-03 14:28 ` Robert Hancock [this message]
2007-04-03 15:26 ` 2.6.20.4: NETDEV WATCHDOG and lockups Christian Kujau
2007-04-03 15:41 ` Lee Revell
2007-04-02 19:41 Christian Kujau
2007-04-02 20:20 ` Chuck Ebbert
2007-04-02 21:15 ` Christian Kujau
2007-04-03 5:34 ` Christian Kujau
2007-04-03 15:17 ` Christian Kujau
2007-04-03 5:20 ` Len Brown
2007-04-03 5:46 ` Christian Kujau
2007-04-03 6:58 ` Jarek Poplawski
2007-04-03 9:47 ` Christian Kujau
2007-04-03 15:19 ` Christian Kujau
2007-04-03 20:34 ` Francois Romieu
2007-04-04 11:21 ` Jarek Poplawski
2007-04-04 13:20 ` Christian Kujau
2007-04-05 6:20 ` Jarek Poplawski
2007-04-06 18:19 ` Christian Kujau
2007-04-06 18:27 ` Christian Kujau
2007-04-17 12:36 ` Jarek Poplawski
2007-04-04 13:53 ` Denys
2007-04-04 17:34 ` Christian Kujau
2007-04-03 20:57 ` Francois Romieu
2007-04-04 13:12 ` Christian Kujau
2007-04-04 18:10 ` Francois Romieu
2007-04-04 18:57 ` Christian Kujau
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=4612648D.4090904@shaw.ca \
--to=hancockr@shaw.ca \
--cc=christian@g-house.de \
--cc=lenb@kernel.org \
--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