Re: unexpected IO-APIC

Randy.Dunlap
2003-04-17T20:28:34Z

On Thu, 17 Apr 2003 11:46:49 -0700 (PDT) <lk@trolloc.com> wrote:

| > > Supermicro X5DPE-G2 motherboard with Intel 7502 chipset
| > > kernel 2.4.21-pre7
| > > kernel message: An unexpected IO-APIC was found. If this kernel release
| > > is less than three months old please report this to linux-smp@vger.kernel.org
|
| > This looks like the output from syslog and not dmesg, in any event it is
| > in complete.
| > > Apr 16 08:08:17 nfs2 kernel: An unexpected IO-APIC was found. If this kernel release is less than
| > > Apr 16 08:08:17 nfs2 kernel: three months old please report this to linux-smp@vger.kernel.org
| > > Apr 16 08:08:17 nfs2 kernel:
| >
| > THE MOST IMPORTANT PART SHOULD BE HERE, please resubmit thanks!
|
| Sorry about that. This is the _exact_ dmesg output, captured from the serial
| console. There's still no additional information where you're looking for it
| though. Also, thanks for posting the unknown IO-APIC FAQ. I looked for
| something like that before posting, but couldn't find it.
|
|
| Linux version 2.4.21-pre7-ac1 (root@nfs2) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #2 SMP Mon Apr 14 04:20:09 PDT 2003
| BIOS-provided physical RAM map:
...
| ENABLING IO-APIC IRQs
| Setting 2 in the phys_id_present_map
| ...changing IO-APIC physical APIC ID to 2 ... ok.
| Setting 3 in the phys_id_present_map
| ...changing IO-APIC physical APIC ID to 3 ... ok.
| Setting 4 in the phys_id_present_map
| ...changing IO-APIC physical APIC ID to 4 ... ok.
| Setting 5 in the phys_id_present_map
| ...changing IO-APIC physical APIC ID to 5 ... ok.
| Setting 8 in the phys_id_present_map
| ...changing IO-APIC physical APIC ID to 8 ... ok.
| ..TIMER: vector=0x31 pin1=2 pin2=0
| testing the IO APIC.......................
|
| An unexpected IO-APIC was found. If this kernel release is less than
| three months old please report this to linux-smp@vger.kernel.org
|
|
|
|
| .................................... done.
| Using local APIC timer interrupts.
| calibrating APIC timer ...
| ..... CPU clock speed is 2399.4086 MHz.
| ..... host bus clock speed is 133.3003 MHz.
| cpu: 0, clocks: 1333003, slice: 444334
| CPU0<T0:1332992,T1:888656,D:2,S:444334,C:1333003>
| cpu: 1, clocks: 1333003, slice: 444334
| CPU1<T0:1332992,T1:444320,D:4,S:444334,C:1333003>
| migration_task 0 on cpu=0
| migration_task 1 on cpu=1
| PCI: PCI BIOS revision 2.10 entry at 0xfd875, last bus=7
| PCI: Using configuration type 1
| PCI: Probing PCI hardware
| PCI: Ignoring BAR0-3 of IDE controller 00:1f.1
| Transparent bridge - Intel Corp. 82801BA/CA/DB PCI Bridge
| PCI: Discovered primary peer bus 10 [IRQ]
| PCI: Discovered primary peer bus 11 [IRQ]
| PCI: Discovered primary peer bus 12 [IRQ]
| PCI: Using IRQ router PIIX [8086/2480] at 00:1f.0

Hm, well, the lines with the good info are still missing.
Instead of 'dmesg', could you look at /var/log/messages (kernel
message log) for that info? If it's also missing there,
you'll probably need to edit /etc/syslog.conf and in the
# Kernel logging
section (if there is one, otherwise just add this anyway), add:

kern.* -/var/log/kern.log

then reboot and get the info from the /var/log/kern.log file.

Or maybe there's a better way to do this, but I don't know it.

--
~Randy