[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-smp
Subject:    MP table in the EBDA can be UNSAFE
From:       Maris Drukalskis <maris () zl ! lv>
Date:       2001-12-13 9:48:21
[Download RAW message or body]

Dear Sirs!

On my RedHar6.2(kernel2.2.19) in the /var/log/messages I see:

Linux version 2.2.19-6.2.7smp (root@porky.devel.redhat.com) (gcc version
egcs-2.
BIOS-provided physical RAM map:
 BIOS-e820: 0009d000 @ 00000000 (usable)
 BIOS-e820: 27eed140 @ 00100000 (usable)
Intel MultiProcessor Specification v1.4
    Virtual Wire compatibility mode.
OEM ID: IBM ENSW Product ID: xSeries 220  APIC at: 0xFEE00000
Processor #3 Pentium(tm) Pro APIC version 17
Processor #0 Pentium(tm) Pro APIC version 17
I/O APIC #14 Version 17 at 0xFEC00000.
I/O APIC #13 Version 17 at 0xFEC01000.
Processors: 2
WARNING: MP table in the EBDA can be UNSAFE, contact
linux-smp@vger.kernel.org i
mapped APIC to ffffe000 (fee00000)
mapped IOAPIC to ffffd000 (fec00000)
mapped IOAPIC to ffffc000 (fec01000)
identd startup succeeded

Why Processor #3 and Processor #0 ? Is it Ok? Why no #0 and #1 ?
And what's wrong with "MP table in the EBDA"?

-- 
Regards: Maris Drukalskis
-
To unsubscribe from this list: send the line "unsubscribe linux-smp" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]