Messages in this thread | | | Subject | RE: ACPI broken... again! | Date | Tue, 17 Jun 2003 10:10:06 -0700 | From | "Grover, Andrew" <> |
| |
> From: Felix von Leitner [mailto:felix-kernel@fefe.de] > 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.
"Again." Are you saying it used to work on these machines and then it stopped? If so I think we have a fix to try in the next ACPI release (which may or may not make it into the next kernel release.)
> 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?
Do I hear violins playing? Poor, poor you! :)
The ACPI PCI routing code still isn't 100% correct. Have you tried pci=noacpi? Have you diagnosed exactly what is going wrong on your system? Have you checked bugzilla for similar bugs? Have you sent a patch fixing the problem on your system?
> 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.
So don't compile it in for now. When you buy a system in a few years that won't work properly without ACPI, and it *works* because of the work everyone on acpi-devel is doing, then you'll change your tune.
Regards -- Andy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |