linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zwane Mwaikambo <zwane@arm.linux.org.uk>
To: Paul Rolland <rol@witbe.net>
Cc: linux-smp@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: WARNING: MP table in the EBDA can be UNSAFE
Date: Fri, 5 Dec 2003 11:00:11 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0312051053481.10913@montezuma.fsmlabs.com> (raw)
In-Reply-To: <200312051518.hB5FIQD29335@tag.witbe.net>

On Fri, 5 Dec 2003, Paul Rolland wrote:

> Our Linux, running on an IBM X-Series 445, says :
> (excerpt from dmesg) :
>
> found SMP MP-table at 0009dd40
> hm, page 0009d000 reserved twice.
> hm, page 0009e000 reserved twice.
> hm, page 0009e000 reserved twice.
> hm, page 0009f000 reserved twice.
> WARNING: MP table in the EBDA can be UNSAFE, contact linux-smp@vger.kernel.org if you experience SMP problems!

This bit is ok and can be safely ignored.

> LAPIC (acpi_id[0x0000] id[0x0] enabled[1])
> CPU 0 (0x0000) enabledProcessor #0 Pentium 4(tm) XEON(tm) APIC version 16
>
> LAPIC (acpi_id[0x0001] id[0x12] enabled[1])
> CPU 1 (0x1200) enabled<4>Processor #18 INVALID - (Max ID: 16).
> LAPIC (acpi_id[0x0002] id[0x20] enabled[1])
> CPU 1 (0x2000) enabled<4>Processor #32 INVALID - (Max ID: 16).
> LAPIC (acpi_id[0x0003] id[0x32] enabled[1])
> CPU 1 (0x3200) enabled<4>Processor #50 INVALID - (Max ID: 16).
>
> Is there any known solution to re-enable the CPU 1, CPU 2 and CPU 3 ?
>
> Is this an IBM bug ?

Did you compile your kernel with the following option?
IBM x440 Summit/EXA support

CONFIG_X86_SUMMIT

  reply	other threads:[~2003-12-05 16:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05 15:18 WARNING: MP table in the EBDA can be UNSAFE Paul Rolland
2003-12-05 16:00 ` Zwane Mwaikambo [this message]
2003-12-05 16:10   ` Paul Rolland
2003-12-05 16:16     ` Zwane Mwaikambo
2003-12-05 16:59       ` Paul Rolland
2003-12-08 10:23       ` Paul Rolland
2003-12-08 14:15         ` Zwane Mwaikambo

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=Pine.LNX.4.58.0312051053481.10913@montezuma.fsmlabs.com \
    --to=zwane@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-smp@vger.kernel.org \
    --cc=rol@witbe.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).