From: "Manfred Spraul" <manfred@colorfullife.com>
To: <pf-kernel@mirkwood.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Kernel 2.4.2 - kernel BUG at apic.c:220!
Date: Sat, 24 Feb 2001 19:45:43 +0100 [thread overview]
Message-ID: <000c01c09e92$25dd2e40$5517fea9@local> (raw)
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
> kernel BUG at apic.c:220!
>From apic.c:
<<<<<<<<<<<
/*
* Double-check wether this APIC is really registered.
*/
if (!test_bit(GET_APIC_ID(apic_read(APIC_ID)),
&phys_cpu_present_map))
BUG();
>>>>>>>>>>>
Really odd. That's usually a sign of a bad MP table.
Could you check your BIOS settings for an entry MP, or MPS, or
Multiprocessor Table?
Usually the options are 1.1 and 1.4 - just try the other one.
or try the attached patch - it prints 2 additional debug lines.
--
Manfred
[-- Attachment #2: patch.out --]
[-- Type: application/octet-stream, Size: 622 bytes --]
--- linux/arch/i386/kernel/apic.c.old Tue Dec 05 21:43:48 2000
+++ linux/arch/i386/kernel/apic.c Sat Feb 24 19:39:44 2001
@@ -216,8 +216,13 @@
/*
* Double-check wether this APIC is really registered.
*/
- if (!test_bit(GET_APIC_ID(apic_read(APIC_ID)), &phys_cpu_present_map))
+ if (!test_bit(GET_APIC_ID(apic_read(APIC_ID)), &phys_cpu_present_map)) {
+ printk(KERN_ERR "phys_cpu_present_map is %lxh.\n",
+ phys_cpu_present_map);
+ printk(KERN_ERR "Apic id is %ldh.\n",
+ GET_APIC_ID(apic_read(APIC_ID)));
BUG();
+ }
/*
* Intel recommends to set DFR, LDR and TPR before enabling
next reply other threads:[~2001-02-24 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-24 18:45 Manfred Spraul [this message]
2001-02-25 3:51 ` Kernel 2.4.2 - kernel BUG at apic.c:220! pf-kernel
-- strict thread matches above, loose matches on Subject: below --
2001-02-23 23:28 pf-kernel
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='000c01c09e92$25dd2e40$5517fea9@local' \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pf-kernel@mirkwood.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 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.