From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Rich West <Rich.West@wesmo.com>,
Wander Winkelhorst <w.winkelhorst@gmail.com>,
linux-kernel@vger.kernel.org,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: sata_via
Date: Sun, 13 Apr 2008 11:45:31 +0900 [thread overview]
Message-ID: <480173CB.5070805@gmail.com> (raw)
In-Reply-To: <47F7F463.2060402@garzik.org>
Jeff Garzik wrote:
> Rich West wrote:
>> I was only curious as to what turning off power management support
>> would buy with regard to the sata timeout issue.
>
>
> ACPI is not only power management. It is all the information your
> hardware conveys to your OS, about the setup and workings of your hardware.
>
> Without ACPI, non-PM things like SMP, laptop dock/undock, and many other
> gadgets fail to function (or are configured sub-optimally).
>
> ACPI sets up interrupt routing, and Linux history is _loaded_ with
> _years_ of problem reports that appear as timeouts, only to be resolved
> as ACPI interrupt bugs (aka BIOS bugs, since ACPI tables come from BIOS).
Also, please give a shot at the sacred "irqpoll".
--
tejun
next prev parent reply other threads:[~2008-04-13 2:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 20:51 sata_via Rich West
2008-04-04 22:04 ` sata_via Jeff Garzik
2008-04-04 23:44 ` sata_via Rich West
2008-04-05 7:15 ` sata_via Wander Winkelhorst
[not found] ` <47F7982E.5080701@wesmo.com>
2008-04-05 21:51 ` sata_via Jeff Garzik
2008-04-13 2:45 ` Tejun Heo [this message]
2008-04-13 4:19 ` sata_via Rich West
2008-04-13 4:36 ` sata_via Rich West
2008-04-14 0:39 ` sata_via Tejun Heo
2008-04-14 8:13 ` sata_via Thomas Renninger
2008-04-14 8:32 ` sata_via Peter Gervai
2008-04-15 2:40 ` sata_via Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2008-04-05 16:08 sata_via Marin Mitov
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=480173CB.5070805@gmail.com \
--to=htejun@gmail.com \
--cc=Rich.West@wesmo.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=w.winkelhorst@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.