archive mirror
 help / color / mirror / Atom feed
From: Eric Valette <>
To: "Grover, Andrew" <>,,,
Subject: [PATCH] Linux 2.6-pre-mm2 Fix crash on boot on ASUS L3800C if enabing APIC => add this machine to DMI black list
Date: Sun, 20 Jul 2003 21:48:24 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 702 bytes --]

The following patch integrated in 2.5.74,


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....

-- eric

[-- Attachment #2: dmi_scan_black_list --]
[-- Type: text/plain, Size: 485 bytes --]

--- linux-2.6.0-test1/arch/i386/kernel/dmi_scan.c.orig	2003-07-20 17:09:10.000000000 +0200
+++ linux-2.6.0-test1/arch/i386/kernel/dmi_scan.c	2003-07-20 21:25:02.000000000 +0200
@@ -706,6 +706,12 @@
 			} },
+	{ local_apic_kills_bios, "ASUS L3C", {
+			} },
 	/* Problem Intel 440GX bioses */
 	{ broken_pirq, "SABR1 Bios", {			/* Bad $PIR */

  parent reply	other threads:[~2003-07-20 19:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 18:56 Linux 2.6-pre1 Does not boot on ASUS L3800C: lock up in acpi while "Executing all Devices _STA and_INIT methods" Grover, Andrew
2003-07-20 13:18 ` Eric Valette
2003-07-20 18:00   ` Karol Kozimor
2003-07-20 19:48   ` Eric Valette [this message]
2003-07-21  1:14 [PATCH] Linux 2.6-pre-mm2 Fix crash on boot on ASUS L3800C if enabing APIC => add this machine to DMI black list Mikael Pettersson
2003-07-21  8:07 ` Eric Valette
2003-07-25 20:52 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).