From: Jochen Voss <voss@seehuhn.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: invalid SMP mptable on Toshiba Satellite 2430-301
Date: Thu, 13 Nov 2003 18:45:06 +0000 [thread overview]
Message-ID: <20031113184506.GA602@seehuhn.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0311131009450.8093-100000@home.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]
Hello,
On Thu, Nov 13, 2003 at 10:13:08AM -0800, Linus Torvalds wrote:
> Hmm.. Do you have ACPI enabled? We really shouldn't need the MP table if
> the information is elsewhere, but the mptable assumptions might be a bit
> entrenched.
With SMP and ACPI enabled I get the following kernel
boot messages
Intel MultiProcessor Specification v1.4
Virtual Wire compatibility mode.
SMP mptable: bad signature [0x0]!
BIOS bug, MP table errors detected!...
... disabling SMP support. (tell your hw vendor)
The last message is generated by the following code
in arch/i386/kernel/mpparse.c:
if (!smp_read_mpc((void *)mpf->mpf_physptr)) {
smp_found_config = 0;
printk(KERN_ERR "BIOS bug, MP table errors detected!...\n");
printk(KERN_ERR "... disabling SMP support. (tell your hw vendor)\n");
return;
}
I don't know what effects are caused by the 'smp_found_config = 0',
but later-on the following messages appear:
No local APIC present or hardware disabled
...
CPU: After generic identify, caps: bfebf9ff 00000000 00000000 00000000
CPU: After vendor identify, caps: bfebf9ff 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Hyper-Threading is disabled
CPU: After all inits, caps: bfebf9ff 00000000 00000000 00000080
...
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Starting migration thread for cpu 0
CPUS done 4
I hope this helps,
Jochen
--
http://seehuhn.de/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-11-13 18:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 11:27 Jochen Voss
2003-11-13 16:40 ` Linus Torvalds
2003-11-13 18:04 ` Jochen Voss
2003-11-13 18:13 ` Linus Torvalds
2003-11-13 18:45 ` Jochen Voss [this message]
2003-11-16 16:31 ` Kai Henningsen
2003-11-16 19:28 ` Jochen Voss
2003-11-13 18:56 Nakajima, Jun
2003-11-13 19:30 ` Jochen Voss
2003-11-13 22:21 ` Linus Torvalds
2003-11-13 22:44 ` Jochen Voss
2003-11-13 22:51 ` Linus Torvalds
2003-11-14 8:43 ` Herbert Xu
2003-11-14 5:31 Nakajima, Jun
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=20031113184506.GA602@seehuhn.de \
--to=voss@seehuhn.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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: 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
Powered by JetHome