On Sun, 20 Jul 2003 21:48:24 +0200, Eric Valette wrote:
>The following patch integrated in 2.5.74,
>
><http://lists.insecure.org/lists/linux-kernel/2003/Jun/5840.html>
>
>really enables the APIC even if BIOS disabled it. Unfortunately,
>enabling APIC really does not seem to work on this ASUS laptop and ACPI
>(which is mandatory) crash the kernel in ACPI code at boot time while
>"Executing all Devices _STA and_INIT methods"
>
>Unless someones find a bug in ACPI code related to APIC management, It
>is safer to add this machine in the DMI black list (along with DELL,
>IBM, ...).
>
>So, as suggested by the author of the problematic change, I added and
>entry in the DMI black list. But my guess is that most laptop will soon
>be present in this list....
At least two P4 laptops are known to require the 2.5.74 patch, and
they do work with the local APIC.
While I don't dispute your machine has some problem, please
do the following first before we completely blacklist it:
- ensure you have the latest BIOS (ftp.asuscom.de has the ones for
their desktop mainboards, presumably the laptop BIOSen are also there)
- in what way is ACPI mandatory? does it fail to boot, or does it
just lose some specific feature? If you just want suspend support,
try APM if the machine has it
A question for the ACPI people:
- Does the Linux kernel ACPI code ever transfer control to BIOS,
explicitly or implicitly via SMIs triggered by the interpreter?
If you do transfer control, do you disable interrupts and/or
the interrupt controllers before transferring control?
Entering BIOS with the local APIC live, in particular the timer,
is a known hang-generator with APM.
/Mikael
(. again in "I hate BIOS writers" mode, grr .)
-
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/
This archive was generated by hypermail 2b29 : Wed Jul 23 2003 - 22:00:41 EST