From: Michael Arndt <M.Arndt@science-computing.de>
To: linux-smp@vger.kernel.org
Subject: WARNING: unexpected IO-APIC
Date: Mon, 8 Jul 2002 15:35:59 +0200 [thread overview]
Message-ID: <20020708153559.B5641@det.science-computing.de> (raw)
Hello
a Dual CPU Board gets the following error messages
with respect to MTR / APIC (below in detail)
IO APIC #2......
.... register #00: 02000000
....... : physical APIC id: 02
.... register #01: 00178020
....... : max redirection entries: 0017
....... : IO APIC version: 0020
WARNING: unexpected IO-APIC, please mail
to linux-smp@vger.kernel.org
mtrr: your CPUs had inconsistent fixed MTRR settings
mtrr: probably your BIOS does not setup all CPUs
CPU: 2 x Intel XEON 2.2 GHZ
Kernel: 2.4.9-21smp #1 SMP Thu Jan 17 14:01:48 EST 2002 i686 unknown
If there is any Feedback, please pm, i am not on the list.
Complete Output:
Intel MultiProcessor Specification v1.4
Virtual Wire compatibility mode.
OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
Processor #0 Unknown CPU [15:2] APIC version 17
Processor #1 Unknown CPU [15:2] APIC version 17
I/O APIC #2 Version 17 at 0xFEC00000.
Processors: 2
CPU: Physical Processor ID: 3
Intel machine check reporting enabled on CPU#1.
CPU: After vendor init, caps: 3febfbff 00000000 00000000 00000000
CPU: After generic, caps: 3febfbff 00000000 00000000 00000000
CPU: Common caps: 3febfbff 00000000 00000000 00000000
CPU1: Intel(R) XEON(TM) CPU 2.20GHz stepping 04
Total of 2 processors activated (8703.18 BogoMIPS).
WARNING: No sibling found for CPU 0.
WARNING: No sibling found for CPU 1.
ENABLING IO-APIC IRQs
...changing IO-APIC physical APIC ID to 2 ... ok.
init IO_APIC IRQs
IO-APIC (apicid-pin) 2-0, 2-5, 2-9, 2-10, 2-11, 2-12, 2-20, 2-21, 2-22 not connected.
..TIMER: vector=0x31 pin1=2 pin2=0
number of MP IRQ sources: 18.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................
IO APIC #2......
.... register #00: 02000000
....... : physical APIC id: 02
.... register #01: 00178020
....... : max redirection entries: 0017
....... : IO APIC version: 0020
WARNING: unexpected IO-APIC, please mail
to linux-smp@vger.kernel.org
WARNING: unexpected IO-APIC, please mail
to linux-smp@vger.kernel.org
.... register #02: 00000000
....... : arbitration: 00
.... IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 000 00 1 0 0 0 0 0 0 00
01 003 03 0 0 0 0 0 1 1 39
02 003 03 0 0 0 0 0 1 1 31
03 003 03 0 0 0 0 0 1 1 41
04 003 03 0 0 0 0 0 1 1 49
05 000 00 1 0 0 0 0 0 0 00
06 003 03 0 0 0 0 0 1 1 51
07 003 03 0 0 0 0 0 1 1 59
08 003 03 0 0 0 0 0 1 1 61
09 000 00 1 0 0 0 0 0 0 00
0a 000 00 1 0 0 0 0 0 0 00
0b 000 00 1 0 0 0 0 0 0 00
0c 000 00 1 0 0 0 0 0 0 00
0d 003 03 0 0 0 0 0 1 1 69
0e 003 03 0 0 0 0 0 1 1 71
0f 003 03 0 0 0 0 0 1 1 79
10 003 03 1 1 0 1 0 1 1 81
11 003 03 1 1 0 1 0 1 1 89
12 003 03 1 1 0 1 0 1 1 91
13 003 03 1 1 0 1 0 1 1 99
14 000 00 1 0 0 0 0 0 0 00
15 000 00 1 0 0 0 0 0 0 00
16 000 00 1 0 0 0 0 0 0 00
17 003 03 1 1 0 1 0 1 1 A1
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
IRQ16 -> 0:16
IRQ17 -> 0:17
IRQ18 -> 0:18
IRQ19 -> 0:19
IRQ23 -> 0:23
.................................... done.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2180.7314 MHz.
..... host bus clock speed is 99.1240 MHz.
cpu: 0, clocks: 991240, slice: 330413
CPU0<T0:991232,T1:660816,D:3,S:330413,C:991240>
cpu: 1, clocks: 991240, slice: 330413
CPU1<T0:991232,T1:330400,D:6,S:330413,C:991240>
checking TSC synchronization across CPUs: passed.
mtrr: your CPUs had inconsistent fixed MTRR settings
mtrr: probably your BIOS does not setup all CPUs
with regards
Michael Arndt
M.Arndt@science-computing.de
next reply other threads:[~2002-07-08 13:35 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 13:35 Michael Arndt [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-26 7:50 WARNING: unexpected IO-APIC BURKHARD JOCHEN
2004-08-11 14:39 Deepak Dogra
2004-08-06 10:19 Chris Kant
2004-06-06 19:18 Graham Wilson
2004-06-05 11:53 Philipp Walderdorff
2004-05-25 5:52 Amedeo Minutolo
2004-02-09 21:07 ,,,
2003-12-22 3:32 Scott Weber
2003-11-12 15:38 Nick Starai
2003-07-28 0:25 Albert Sodyl
2003-06-03 21:51 idiot [James Green]
2003-05-08 15:05 bl8n8r
2003-04-19 21:45 Daniel Bergman
2003-03-10 17:10 Bob Schuknecht
2003-02-28 15:10 Bernard and Jennifer Cohen
2003-02-27 16:51 DR Aldrich
2003-02-21 19:17 Radek Aster
2003-02-16 1:23 rod
2003-02-03 19:35 Matt King
2003-02-04 12:26 ` Alan Cox
2003-01-12 9:24 Sakari Aaltonen
2003-01-09 20:04 Anderson Oliveira da Silva
2003-01-03 20:16 Jeff Frost
2002-12-22 11:53 John Rye
2002-12-25 21:35 ` Alan Cox
2002-12-18 19:48 Kazik
2002-12-04 19:02 Christian Birchinger
2002-11-26 22:23 Warning " Rafal Cichosz
2002-11-16 2:50 WARNING: " Chia-Hsing Yu
2002-11-09 3:42 PASTOR Michel
2002-11-09 3:41 PASTOR Michel
2002-10-24 14:58 warning " Thomas Björnell
2002-10-25 9:56 ` Maciej W. Rozycki
2002-10-03 13:33 WARNING: " Brian Jonnes
2002-10-03 13:43 ` David McIlwraith
2002-10-04 6:52 ` Brian Jonnes
2002-10-03 15:02 ` Randy.Dunlap
2002-10-04 6:54 ` Brian Jonnes
2002-10-08 0:40 ` Randy.Dunlap
2002-10-16 13:19 ` Maciej W. Rozycki
2002-10-18 0:59 ` Randy.Dunlap
2002-10-01 22:00 Avinesh Bangar
2002-08-29 16:06 brian
2002-08-14 20:04 james.oden
2002-08-15 1:14 ` Alan Cox
2002-07-17 13:06 countdown
2002-07-12 17:22 dwh
2002-07-12 18:07 ` Alan Cox
2002-07-08 16:31 Enkh Tumenbayar
2002-07-08 18:43 ` WARNING: " Vladimir G. Ivanovic
2002-07-08 20:22 ` E. Robert Bogusta
2002-07-09 16:44 ` Vladimir G. Ivanovic
2002-06-23 23:29 Josh Wilcox
2002-06-11 10:06 Philipp Schulte
2002-05-15 14:48 Melissa Vandenbrink
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=20020708153559.B5641@det.science-computing.de \
--to=m.arndt@science-computing.de \
--cc=linux-smp@vger.kernel.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 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.