From: "Grover, Andrew" <andrew.grover@intel.com>
To: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>, proski@gnu.org
Cc: linux-kernel@vger.kernel.org
Subject: RE: ACPI + Promise IDE = disk corruption :-(((
Date: Fri, 22 Jun 2001 17:30:19 -0700 [thread overview]
Message-ID: <4148FEAAD879D311AC5700A0C969E89006CDDEEF@orsmsx35.jf.intel.com> (raw)
> From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
> I've seen several people report ACPI eats disks. ACPI is
> incredibly complex
> badly designed crud. My advice is never use ACPI. This
> incidentally appears
> to be the advice Microsoft give people too - they tell people
> to disable
> ACPI as one of the first steps to diagnosing strange crashes
> in machines
They're just bugs. That's why it's marked experimental, and unlike the rest
of the "experimental" drivers, we aren't kidding.
It's just *one* issue that has generated all the disk corruption reports.
Putting the processor into the C3 power state, in combination with bus
mastering. This is disabled in the most recent release. I'd love to fix this
one, but if it were easy, it'd be fixed by now. Maybe you can shed some
light - if you're willing, let me know and I'll describe the problem in
greater detail.
> I've been discussing with a few folk about doing an
> alternative mini acpi
> subset so that Linux can be booted on most 'ACPI only'
> hardware without
> using all the ACPI junk
Could these discussions be opened up to a wider readership? Perhaps you
could use linux-pm-devel@sourceforge.net, or
acpi@phobos.fachschaften.tu-muenchen.de?
Regards -- Andy
next reply other threads:[~2001-06-23 0:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-23 0:30 Grover, Andrew [this message]
2001-06-23 8:20 ` Alan Cox
2001-06-23 10:56 ` Chris Wedgwood
-- strict thread matches above, loose matches on Subject: below --
2001-06-25 17:38 Grover, Andrew
2001-06-22 21:18 Grover, Andrew
2001-06-22 21:07 Pavel Roskin
2001-06-22 22:16 ` Alan Cox
2001-06-23 10:54 ` Chris Wedgwood
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=4148FEAAD879D311AC5700A0C969E89006CDDEEF@orsmsx35.jf.intel.com \
--to=andrew.grover@intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=proski@gnu.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
all inboxes | Powered by JetHome®