From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: proski@gnu.org (Pavel Roskin)
Cc: linux-kernel@vger.kernel.org
Subject: Re: ACPI + Promise IDE = disk corruption :-(((
Date: Fri, 22 Jun 2001 23:16:01 +0100 (BST) [thread overview]
Message-ID: <E15DZDd-0004Fq-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.33.0106221635230.1575-100000@vesta.nine.com> from "Pavel Roskin" at Jun 22, 2001 05:07:02 PM
> I enabled ACPI in 2.4.5-ac17 (2.4.5-ac16 works fine with the same config
> except ACPI). When I booted I saw a message
> I hit reset hoping to boot the system with "acpi=no-idle", but GRUB
> couldn't load stage2, which resides on the root partition (reiserfs).
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
ACPI is over complex, new technology. The BIOS stuff is new (and frequently
wrong), the kernel stuff is new (and has plenty of known bugs) and the
combination is a recipe for disaster.
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
Alan
next prev parent reply other threads:[~2001-06-22 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 21:07 Pavel Roskin
2001-06-22 22:16 ` Alan Cox [this message]
2001-06-23 10:54 ` Chris Wedgwood
2001-06-22 21:18 Grover, Andrew
2001-06-23 0:30 Grover, Andrew
2001-06-23 8:20 ` Alan Cox
2001-06-23 10:56 ` Chris Wedgwood
2001-06-25 17:38 Grover, Andrew
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=E15DZDd-0004Fq-00@the-village.bc.nu \
--to=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®