From: Benny Sjostrand <gorm@cucumelo.org>
To: linux-smp@vger.kernel.org
Subject: [STRANGE] got "unexpected IO-APIC" message in log
Date: Tue, 25 Mar 2003 00:39:14 +0100 [thread overview]
Message-ID: <3E7F9722.1080804@cucumelo.org> (raw)
got this message in log:
Mar 25 00:23:53 cactus kernel: testing the IO APIC.......................
Mar 25 00:23:53 cactus kernel:
Mar 25 00:23:53 cactus kernel: WARNING: unexpected IO-APIC, please mail
Mar 25 00:23:53 cactus kernel: to linux-smp@vger.kernel.org
Mar 25 00:23:53 cactus kernel: .................................... done.
What could it be ??
So as it says mail to linux-smp@vger.kernel.org, that's what I'm doing,
running linux-2.4.20, on a Dual Pentium III, HW is something like a ~
MSI-PRO266 with Promise IDE-RAID (dont remember exactly....)
Full log:
Mar 25 00:23:53 cactus kernel: CPU0: Intel Pentium III (Coppermine)
stepping 06
Mar 25 00:23:53 cactus kernel: per-CPU timeslice cutoff: 730.95 usecs.
Mar 25 00:23:53 cactus kernel: enabled ExtINT on CPU#0
Mar 25 00:23:53 cactus kernel: ESR value before enabling vector: 00000000
Mar 25 00:23:53 cactus kernel: ESR value after enabling vector: 00000000
Mar 25 00:23:53 cactus kernel: Booting processor 1/1 eip 2000
Mar 25 00:23:53 cactus kernel: Initializing CPU#1
Mar 25 00:23:53 cactus kernel: masked ExtINT on CPU#1
Mar 25 00:23:53 cactus kernel: ESR value before enabling vector: 00000000
Mar 25 00:23:53 cactus kernel: ESR value after enabling vector: 00000000
Mar 25 00:23:53 cactus kernel: Calibrating delay loop... 1992.29 BogoMIPS
Mar 25 00:23:53 cactus kernel: CPU: L1 I cache: 16K, L1 D cache: 16K
Mar 25 00:23:53 cactus kernel: CPU: L2 cache: 256K
Mar 25 00:23:53 cactus kernel: Intel machine check reporting enabled on
CPU#1.
Mar 25 00:23:53 cactus kernel: CPU1: Intel Pentium III (Coppermine)
stepping 06
Mar 25 00:23:53 cactus kernel: Total of 2 processors activated (3978.03
BogoMIPS).
Mar 25 00:23:53 cactus kernel: ENABLING IO-APIC IRQs
Mar 25 00:23:53 cactus kernel: Setting 2 in the phys_id_present_map
Mar 25 00:23:53 cactus kernel: ...changing IO-APIC physical APIC ID to 2
... ok.
Mar 25 00:23:53 cactus kernel: ..TIMER: vector=0x31 pin1=2 pin2=0
Mar 25 00:23:53 cactus kernel: testing the IO APIC.......................
Mar 25 00:23:53 cactus kernel:
Mar 25 00:23:53 cactus kernel: WARNING: unexpected IO-APIC, please mail
Mar 25 00:23:53 cactus kernel: to linux-smp@vger.kernel.org
Mar 25 00:23:53 cactus kernel: .................................... done.
Mar 25 00:23:53 cactus kernel: Using local APIC timer interrupts.
Mar 25 00:23:53 cactus kernel: calibrating APIC timer ...
Mar 25 00:23:53 cactus kernel: ..... CPU clock speed is 997.2124 MHz.
Mar 25 00:23:53 cactus kernel: ..... host bus clock speed is 132.9612 MHz.
Mar 25 00:23:53 cactus kernel: cpu: 0, clocks: 1329612, slice: 443204
Mar 25 00:23:53 cactus kernel:
CPU0<T0:1329600,T1:886384,D:12,S:443204,C:1329612>
Mar 25 00:23:53 cactus kernel: cpu: 1, clocks: 1329612, slice: 443204
Mar 25 00:23:53 cactus kernel:
CPU1<T0:1329600,T1:443184,D:8,S:443204,C:1329612>
Mar 25 00:23:53 cactus kernel: checking TSC synchronization across CPUs:
passed.
Mar 25 00:23:53 cactus kernel: Waiting on wait_init_idle (map = 0x2)
Mar 25 00:23:53 cactus kernel: All processors have done init_idle
Mar 25 00:23:53 cactus kernel: mtrr: your CPUs had inconsistent variable
MTRR settings
Mar 25 00:23:53 cactus kernel: mtrr: probably your BIOS does not setup
all CPUs
Mar 25 00:23:53 cactus kernel: PCI: PCI BIOS revision 2.10 entry at
0xfb170, last bus=1
Mar 25 00:23:53 cactus kernel: PCI: Using configuration type 1
Mar 25 00:23:53 cactus kernel: PCI: Probing PCI hardware
Mar 25 00:23:53 cactus kernel: PCI: Using IRQ router default [1106/3101]
at 00:00.0
Mar 25 00:23:53 cactus kernel: PCI->APIC IRQ transform: (B0,I8,P0) -> 11
Mar 25 00:23:53 cactus kernel: PCI->APIC IRQ transform: (B0,I9,P0) -> 10
Mar 25 00:23:53 cactus kernel: PCI->APIC IRQ transform: (B0,I11,P0) -> 5
Mar 25 00:23:53 cactus kernel: PCI->APIC IRQ transform: (B0,I12,P0) -> 11
Mar 25 00:23:53 cactus kernel: PCI->APIC IRQ transform: (B0,I15,P0) -> 5
Mar 25 00:23:53 cactus kernel: PCI->APIC IRQ transform: (B0,I17,P0) -> 11
Mar 25 00:23:53 cactus kernel: PCI->APIC IRQ transform: (B0,I17,P3) -> 5
Mar 25 00:23:53 cactus last message repeated 2 times
Mar 25 00:23:53 cactus kernel: PCI->APIC IRQ transform: (B1,I0,P0) -> 11
Mar 25 00:23:53 cactus kernel: isapnp: Scanning for PnP cards...
Mar 25 00:23:53 cactus kernel: isapnp: No Plug & Play device found
/Benny
reply other threads:[~2003-03-24 23:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3E7F9722.1080804@cucumelo.org \
--to=gorm@cucumelo.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox