From: Marco Wertejuk <wertejuk@mwcis.com>
To: linux-smp@vger.kernel.org
Subject: unknown problem report
Date: Fri, 27 Jun 2003 21:18:14 +0200 [thread overview]
Message-ID: <20030627191814.GA27575@maeko> (raw)
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
reply other threads:[~2003-06-27 19:18 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=20030627191814.GA27575@maeko \
--to=wertejuk@mwcis.com \
--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