From: Rich West <Rich.West@wesmo.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
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 00:36:16 -0400 [thread overview]
Message-ID: <48018DC0.6080407@wesmo.com> (raw)
In-Reply-To: <480189DB.9050900@wesmo.com>
Rich West wrote:
> Tejun Heo wrote:
>> 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".
>
> I've had bad luck in the past (with other machiens) when adding
> "irqpoll" in that it had locked up the entire machine (not this one,
> but others) after a very short period of time. My only attempt at
> using it, though, was to try to address an X server related issue, but
> this is a non-user machine, so X isn't necessary, and, hence, it's at
> runlevel 3 all of the time.
>
> So far, noapic and acpi=off seem to be working.. The system has been
> up 8 days without any problems.. previously, a problem with the SATA
> drive (details of which were part of the first few messages in this
> thread) would surface anywhere between 15 minutes and 5-7 days after a
> reboot.
>
> However, since I started this email, I tried firing up X (with noapci
> and acpi=off both set), the machine locks up entirely.
Although a reboot with irqpoll set managed to fix that X problem. :)
-Rich
next prev parent reply other threads:[~2008-04-13 5:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47F694C8.8020507@wesmo.com>
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 ` sata_via Tejun Heo
2008-04-13 4:19 ` sata_via Rich West
2008-04-13 4:36 ` Rich West [this message]
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
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=48018DC0.6080407@wesmo.com \
--to=rich.west@wesmo.com \
--cc=htejun@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).