From: Eric Valette <eric.valette-GANU6spQydw@public.gmane.org> To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>, sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org, akpm-3NddpPZAyC0@public.gmane.org, mikpe-gJWeRRR3xd2zQB+pC5nmwQ@public.gmane.org Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org 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: <3F1AF208.3030409@free.fr> (raw) In-Reply-To: <3F1A969C.6060606-GANU6spQydw@public.gmane.org> [-- Attachment #1: Type: text/plain, Size: 702 bytes --] 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.... -- 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 @@ NO_MATCH, NO_MATCH } }, + { local_apic_kills_bios, "ASUS L3C", { + MATCH(DMI_BOARD_VENDOR, "ASUSTeK Computer INC."), + MATCH(DMI_BOARD_NAME, "P4_L3C"), + NO_MATCH, NO_MATCH + } }, + /* Problem Intel 440GX bioses */ { broken_pirq, "SABR1 Bios", { /* Bad $PIR */
WARNING: multiple messages have this Message-ID (diff)
From: Eric Valette <eric.valette@free.fr> To: "Grover, Andrew" <andrew.grover@intel.com>, sziwan@hell.org.pl, akpm@osdl.org, mikpe@csd.uu.se Cc: linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net 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: <3F1AF208.3030409@free.fr> (raw) In-Reply-To: <3F1A969C.6060606@free.fr> [-- Attachment #1: Type: text/plain, Size: 702 bytes --] 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.... -- 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 @@ NO_MATCH, NO_MATCH } }, + { local_apic_kills_bios, "ASUS L3C", { + MATCH(DMI_BOARD_VENDOR, "ASUSTeK Computer INC."), + MATCH(DMI_BOARD_NAME, "P4_L3C"), + NO_MATCH, NO_MATCH + } }, + /* Problem Intel 440GX bioses */ { broken_pirq, "SABR1 Bios", { /* Bad $PIR */
next prev parent reply other threads:[~2003-07-20 19:48 UTC|newest] Thread overview: 18+ 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-14 18:56 ` Grover, Andrew [not found] ` <F760B14C9561B941B89469F59BA3A847E9702C-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org> 2003-07-15 20:43 ` Eric Valette [not found] ` <3F146770.8020603-GANU6spQydw@public.gmane.org> 2003-07-15 21:20 ` Karol Kozimor [not found] ` <20030715212054.GA10046-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org> 2003-07-16 8:43 ` Nils Faerber [not found] ` <1058345036.8960.82.camel-65LrUGLyukAb1SvskN2V4Q@public.gmane.org> 2003-07-16 9:09 ` Eric Valette 2003-07-20 13:18 ` Eric Valette 2003-07-20 13:18 ` Eric Valette [not found] ` <3F1A969C.6060606-GANU6spQydw@public.gmane.org> 2003-07-20 18:00 ` Karol Kozimor 2003-07-20 18:00 ` Karol Kozimor 2003-07-20 19:48 ` Eric Valette [this message] 2003-07-20 19:48 ` [PATCH] Linux 2.6-pre-mm2 Fix crash on boot on ASUS L3800C if enabing APIC => add this machine to DMI black list Eric Valette 2003-07-21 1:14 Mikael Pettersson 2003-07-21 1:14 ` Mikael Pettersson [not found] ` <200307210114.h6L1El7M018996-gq7oiAaKCbRt3AgVzhmPzw@public.gmane.org> 2003-07-21 8:07 ` Eric Valette 2003-07-21 8:07 ` Eric Valette 2003-07-25 20:52 Grover, Andrew 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: 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=3F1AF208.3030409@free.fr \ --to=eric.valette-ganu6spqydw@public.gmane.org \ --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \ --cc=akpm-3NddpPZAyC0@public.gmane.org \ --cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \ --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=mikpe-gJWeRRR3xd2zQB+pC5nmwQ@public.gmane.org \ --cc=sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.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: linkBe 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.