From: mikpe@csd.uu.se
To: linux-kernel@vger.kernel.org, lkml@sigkill.net
Cc: Valdis.Kletnieks@vt.edu
Subject: Re: [RFC] Fix NMI watchdog documentation
Date: Mon, 26 May 2003 11:21:38 +0200 (MEST) [thread overview]
Message-ID: <200305260921.h4Q9LcNr022536@harpo.it.uu.se> (raw)
On 26 May 2003 01:31:41 -0400, Disconnect <lkml@sigkill.net> wrote:
>> OK, I put together a kernel that had the Latitude blacklist commented out,
>> and it comes up with:
>>
>> No local APIC present or hardware disabled
>> Initializing CPU#0
>>
>> So add the Latitude C840 to the "known b0rken" list.
>
>Ditto the Inspiron 8500 - no apic at all (which is different from
>known-broken, since nothing bad happened.)
...
>Perhaps just a comment above those entries:
>/* Latitude C840 and Inspiron 8500 have no APIC support in hardware */
If these machines are P4-based, then I bet they do have local APICs.
However, if the BIOS boots the kernel with the local APIC disabled
on a P4, we (apic.c) don't try to enable it. The logic behind that
is that "modern" BIOSen _should_ boot with it enabled, unless they're
horribly broken.
So apply the patch below and try the "can we get the machine to hang"
checklist again.
/Mikael
--- linux-2.5.69/arch/i386/kernel/apic.c.~1~ 2003-04-20 13:08:15.000000000 +0200
+++ linux-2.5.69/arch/i386/kernel/apic.c 2003-05-26 11:11:19.000000000 +0200
@@ -617,7 +617,7 @@
goto no_apic;
case X86_VENDOR_INTEL:
if (boot_cpu_data.x86 == 6 ||
- (boot_cpu_data.x86 == 15 && cpu_has_apic) ||
+ (boot_cpu_data.x86 == 15) ||
(boot_cpu_data.x86 == 5 && cpu_has_apic))
break;
goto no_apic;
next reply other threads:[~2003-05-26 9:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 9:21 mikpe [this message]
2003-05-26 16:40 ` APIC on Dell Laptops - WAS: Re: [RFC] Fix NMI watchdog documentation Disconnect
2003-05-26 18:38 ` mikpe
2003-05-26 19:44 ` Disconnect
2003-05-27 20:25 ` Disconnect
2003-05-27 3:19 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2003-05-25 10:50 mikpe
2003-05-26 2:36 ` Valdis.Kletnieks
2003-05-26 5:31 ` Disconnect
2003-05-25 10:49 mikpe
2003-05-24 19:07 Carl-Daniel Hailfinger
2003-05-24 19:08 ` Zwane Mwaikambo
2003-05-24 19:11 ` Zwane Mwaikambo
2003-05-24 19:43 ` Carl-Daniel Hailfinger
2003-05-25 3:29 ` Valdis.Kletnieks
2003-05-25 3:36 ` Zwane Mwaikambo
2003-05-25 4:48 ` Valdis.Kletnieks
2003-05-25 5:03 ` Zwane Mwaikambo
2003-05-25 5:52 ` Disconnect
2003-05-24 19:12 ` Marc-Christian Petersen
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=200305260921.h4Q9LcNr022536@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@sigkill.net \
/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 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).