From: Felix von Leitner <felix-kernel@fefe.de>
To: linux-kernel@vger.kernel.org
Subject: ACPI broken... again!
Date: Tue, 17 Jun 2003 16:44:43 +0200 [thread overview]
Message-ID: <20030617144443.GA27558@codeblau.de> (raw)
Linux 2.5.70 and above have broken ACPI. Again. This is my fifth
machine on which I try ACPI, two notebooks and three desktops, chipsets
from Intel, VIA and SiS, no matter, ACPI still breaks 'em all.
The symptom is that eth0 does not see the others. /proc/interrupts has
the correct interrupt listed, so it took me a while to suspect ACPI.
agpgart also crashes, and firewire and USB didn't find any devices.
Why oh why is ACPI so horrendously broken?
And more to the point: if it _is_ this broken, why ship it at all? I
don't recall a single moment where ACPI did anything good for me, only
crashes, data loss and general brokenness. This may be a technology
fitting Microsoft and Intel PCs, but why give it even more leverage by
supporting it in Linux? I say rip this abomination right out of the
kernel and be done with it.
Felix
next reply other threads:[~2003-06-17 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 14:44 Felix von Leitner [this message]
2003-06-17 15:12 ` ACPI broken... again! Disconnect
2003-06-17 16:03 ` Ducrot Bruno
-- strict thread matches above, loose matches on Subject: below --
2003-06-17 17:10 Grover, Andrew
2003-06-17 18:02 ` Yaroslav Rastrigin
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=20030617144443.GA27558@codeblau.de \
--to=felix-kernel@fefe.de \
--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 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.