[prev in list] [next in list] [prev in thread] [next in thread]
List: linux-smp
Subject: Re: WARNING: unexpected IO-APIC; all interrupts to one CPU on smp
From: "Randy.Dunlap" <rddunlap () osdl ! org>
Date: 2002-05-23 15:06:18
[Download RAW message or body]
Hi,
This particular IO APIC version and flag are handled
(recognized) in 2.4.16 IIRC (maybe 2.4.17).
We are seeing lots of these reports with VIA KT266 or KT333
chipsets (and their IO APICs) with IO APIC version 0x02.
Since VIA doesn't release their chipset specs, we don't know
how correct these are.
And since these are fairly new, code to recognize these hasn't
been added to the kernel yet.
~Randy
On Thu, 23 May 2002, Earle Nietzel wrote:
| Dave,
|
| This message has nothing to do with the your performance problems or why
| all interrupts go to one CPU.
|
| This message is for the ACPI (IO-APIC included) maintainers to keep an eye
| on when there is new hardware.
|
| You should make sure that your MPS setting is set to 1.1 not 1.4 (BIOS option).
|
| Also boot without passing the noapic option to the kernel. This option
| causes all interrupts go to CPU0 (bypassing the new 2.4 ACPI stuff).
|
| I have not seen posts related to the Supermicro boards so I don't have a
| lot of faith in the above suggestions. But if it doesn't work you should
| try disabling everything in the BIOS except for what is needed and try
| testing from there.
|
| Anyone else have experience with these boards that can give Dave a hand?
|
| Good Luck,
| Earle
|
| At 02:24 AM 5/23/2002, you wrote:
| >Hello,
| >
| >I received the following boot message on several Supermicro motherboards
| >(P4DC6+, P4DCE+, P4DP6) which have among them two Intel chipsets
| >(860, E7500) when using both RedHat 7.1 and RedHat 7.2.
| >
| ><<<
| > WARNING: unexpected IO-APIC, please mail
| > to linux-smp@vger.kernel.org
| > >>>
| >
| >Results for RedHat 7.2 are attached for four of the PCs.
| >
| >Would this be related to the observation that on all machines
| >all interrupts go to CPU0 and none go to CPU1?
| >(We do a "cat /proc/interrupts" to see this.)
| >My colleagues using dual-CPU Tyan motherboards (Athlon?)
| >do not see this, and for slightly slower machines they
| >get slightly faster performance.
| >
| >
| >Five dmesg logs for four machines are attached.
| >All four have:
| > dual Pentium IV Xeon 1.8GHz processors
| > Supermicro motherboards
| > RedHat Linux 7.2 with the included 2.4.7-10smp kernel.
| >except as noted below.
| > Intel SuperMicro
| >Machine Chipset Motherboard
| >"dfd01" 860 P4DC6+ (SCSI on-board but not used)
| >"dfe01" 860 P4DC6+ (SCSI on-board but not used)
| >"dfe02" 860 P4DCE+ (no SCSI on-board; else same as P4DC6+)
| >"dfd02" E7500 P4DP6 (SCSI on-board but not used)
| >
| >The dmesg log for the enterprise kernel is included for dfd02.
| >
| >
| >Thank you,
| >Dave Schmitz
| >StorageTek
| >Louisville, Colorado
| >
| >
| >Here's an extract from one dmesg log, with my emphasis (>>>) added.
| >The full logs are attached.
| >
| >
| >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
| >Kernel command line: ro root=/dev/hda3 mem=700M
| >Initializing CPU#0
| >Detected 1784.330 MHz processor.
| >Console: colour VGA+ 80x25
| >Calibrating delay loop... 3552.05 BogoMIPS
| >Memory: 699480k/716800k available (1396k kernel code, 14860k reserved, 102k
| >data, 240k init, 0k highmem)
| >Dentry-cache hash table entries: 131072 (order: 8, 1048576 bytes)
| >Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
| >Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
| >Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes)
| >Page-cache hash table entries: 262144 (order: 9, 2097152 bytes)
| >CPU: Before vendor init, caps: 3febfbff 00000000 00000000, vendor = 0
| >CPU: L1 I cache: 12K, L1 D cache: 8K
| >CPU: L2 cache: 512K
| >Intel machine check architecture supported.
| >Intel machine check reporting enabled on CPU#0.
| >CPU: After vendor init, caps: 3febfbff 00000000 00000000 00000000
| >CPU: After generic, caps: 3febfbff 00000000 00000000 00000000
| >CPU: Common caps: 3febfbff 00000000 00000000 00000000
| >Enabling fast FPU save and restore... done.
| >Enabling unmasked SIMD FPU exception support... done.
| >Checking 'hlt' instruction... OK.
| >POSIX conformance testing by UNIFIX
| >mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
| >mtrr: detected mtrr type: Intel
| >CPU: Before vendor init, caps: 3febfbff 00000000 00000000, vendor = 0
| >CPU: L1 I cache: 12K, L1 D cache: 8K
| >CPU: L2 cache: 512K
| >Intel machine check reporting enabled on CPU#0.
| >CPU: After vendor init, caps: 3febfbff 00000000 00000000 00000000
| >CPU: After generic, caps: 3febfbff 00000000 00000000 00000000
| >CPU: Common caps: 3febfbff 00000000 00000000 00000000
| >CPU0: Intel(R) XEON(TM) CPU 1.80GHz stepping 04
| >per-CPU timeslice cutoff: 1462.69 usecs.
| >enabled ExtINT on CPU#0
| >ESR value before enabling vector: 00000000
| >ESR value after enabling vector: 00000000
| >Booting processor 1/1 eip 2000
| >Initializing CPU#1
| >masked ExtINT on CPU#1
| >ESR value before enabling vector: 00000000
| >ESR value after enabling vector: 00000000
| >Calibrating delay loop... 3565.15 BogoMIPS
| >CPU: Before vendor init, caps: 3febfbff 00000000 00000000, vendor = 0
| >CPU: L1 I cache: 12K, L1 D cache: 8K
| >CPU: L2 cache: 512K
| >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 1.80GHz stepping 04
| >Total of 2 processors activated (7117.20 BogoMIPS).
| >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-20, 2-21, 2-22 not
| >connected.
| >..TIMER: vector=0x31 pin1=2 pin2=0
| >number of MP IRQ sources: 22.
| >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 003 03 0 0 0 0 0 1 1 69
| > 0d 003 03 0 0 0 0 0 1 1 71
| > 0e 003 03 0 0 0 0 0 1 1 79
| > 0f 003 03 0 0 0 0 0 1 1 81
| > 10 003 03 1 1 0 1 0 1 1 89
| > 11 003 03 1 1 0 1 0 1 1 91
| > 12 003 03 1 1 0 1 0 1 1 99
| > 13 003 03 1 1 0 1 0 1 1 A1
| > 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 A9
| >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
| >IRQ12 -> 0:12
| >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 ...
| >
| > <<dmesg.dfd02.enterprise.log>> <<dmesg.dfd02.smp.log>>
| ><<dmesg.dfd01.smp.log>> <<dmesg.dfe01.smp.log>> <<dmesg.dfe02.smp.log>>
| -
--
~Randy
-
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic