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

List:       linux-smp
Subject:    unknown problem report
From:       Marco Wertejuk <wertejuk () mwcis ! com>
Date:       2003-06-27 19:18:14
[Download RAW message or body]

Hi there,

while reading my logfiles I found this note:

Jun 27 21:06:41 split kernel: An unexpected IO-APIC was found. If this kernel release is less than
Jun 27 21:06:41 split kernel: three months old please report this to linux-smp@vger.kernel.org

I'm running RedHat 9.0 with 2.4.20-18.9smp on a 
Intel P4 with Hyperthreading enabled.

Here is some more output from the logfile: 
Jun 27 21:06:41 split kernel: ENABLING IO-APIC IRQs
Jun 27 21:06:41 split kernel: Setting 2 in the phys_id_present_map
Jun 27 21:06:41 split kernel: ...changing IO-APIC physical APIC ID to 2 ... ok.
Jun 27 21:06:41 split kernel: ..TIMER: vector=0x31 pin1=2 pin2=0
Jun 27 21:06:41 split kernel: testing the IO APIC.......................
Jun 27 21:06:41 split kernel: 
Jun 27 21:06:41 split kernel: An unexpected IO-APIC was found. If this kernel release is less than
Jun 27 21:06:41 split kernel: three months old please report this to linux-smp@vger.kernel.org
Jun 27 21:06:41 split kernel: .................................... done.
Jun 27 21:06:41 split kernel: Using local APIC timer interrupts.
Jun 27 21:06:41 split kernel: calibrating APIC timer ...
Jun 27 21:06:41 split kernel: ..... CPU clock speed is 3065.1845 MHz.
Jun 27 21:06:41 split kernel: ..... host bus clock speed is 133.2688 MHz.
Jun 27 21:06:41 split kernel: cpu: 0, clocks: 1332688, slice: 444229
Jun 27 21:06:41 split kernel: CPU0<T0:1332688,T1:888448,D:11,S:444229,C:1332688>
Jun 27 21:06:41 split kernel: cpu: 1, clocks: 1332688, slice: 444229
Jun 27 21:06:41 split kernel: CPU1<T0:1332688,T1:444224,D:6,S:444229,C:1332688>
Jun 27 21:06:41 split kernel: checking TSC synchronization across CPUs: passed.
Jun 27 21:06:41 split kernel: Starting migration thread for cpu 0
Jun 27 21:06:41 split kernel: smp_num_cpus: 2.
Jun 27 21:06:41 split kernel: Starting migration thread for cpu 1

Actually I could not notice any change in the systems
behaviour when this message appeared :)

-- 
Mit freundlichen Gruessen,
Marco Wertejuk - mwcis.com
Consulting & Internet Solutions
-
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]