From: Ricky McInnes <rick420@high-on-linux.net>
To: linux-smp@vger.kernel.org
Subject: Kernel Message
Date: Sat, 7 Jun 2003 22:21:39 -0400 [thread overview]
Message-ID: <200306072221.39006.rick420@high-on-linux.net> (raw)
Hello,
Not sure what info to give ya, just noticed this in my /var/log/messages:
Jun 7 21:16:10 blazin kernel: Intel machine check reporting enabled on CPU#1.
Jun 7 21:16:10 blazin kernel: CPU1: Intel(R) Pentium(R) 4 CPU 2.40GHz
stepping 09
Jun 7 21:16:10 blazin kernel: Total of 2 processors activated (9555.14
BogoMIPS).
Jun 7 21:16:10 blazin kernel: cpu_sibling_map[0] = 1
Jun 7 21:16:10 blazin kernel: cpu_sibling_map[1] = 0
Jun 7 21:16:10 blazin kernel: ENABLING IO-APIC IRQs
Jun 7 21:16:10 blazin kernel: Setting 2 in the phys_id_present_map
Jun 7 21:16:10 blazin kernel: ...changing IO-APIC physical APIC ID to 2 ...
ok.
Jun 7 21:16:10 blazin kernel: ..TIMER: vector=0x31 pin1=2 pin2=0
Jun 7 21:16:10 blazin kernel: testing the IO APIC.......................
Jun 7 21:16:10 blazin kernel:
Jun 7 21:16:10 blazin kernel: An unexpected IO-APIC was found. If this kernel
release is less than
Jun 7 21:16:10 blazin kernel: three months old please report this to
linux-smp@vger.kernel.org
Jun 7 21:16:10 blazin kernel: .................................... done.
Jun 7 21:16:10 blazin kernel: Using local APIC timer interrupts.
Jun 7 21:16:10 blazin kernel: calibrating APIC timer ...
Jun 7 21:16:10 blazin kernel: ..... CPU clock speed is 2394.0362 MHz.
Jun 7 21:16:10 blazin kernel: ..... host bus clock speed is 199.2528 MHz.
Jun 7 21:16:10 blazin kernel: cpu: 0, clocks: 997528, slice: 332509
Jun 7 21:16:10 blazin kernel: CPU0<T0:997520,T1:665008,D:3,S:332509,C:997528>
Jun 7 21:16:10 blazin kernel: cpu: 1, clocks: 997528, slice: 332509
Jun 7 21:16:10 blazin kernel: CPU1<T0:997520,T1:332496,D:6,S:332509,C:997528>
Jun 7 21:16:10 blazin kernel: checking TSC synchronization across CPUs:
passed.
Jun 7 21:16:10 blazin kernel: migration_task 0 on cpu=0
Jun 7 21:16:10 blazin kernel: migration_task 1 on cpu=1
Its Kernel 2.4.21 patched with the CK patchset.
Ricky McInnes
next reply other threads:[~2003-06-08 2:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-08 2:21 Ricky McInnes [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-02 9:19 Kernel message umesh
2007-06-02 9:39 ` Robert P. J. Day
2003-07-21 2:40 kernel message azalel
2003-07-21 2:46 ` Randy.Dunlap
1999-02-08 10:53 Kernel message Kostas Gewrgiou
1999-02-08 19:07 ` Marcus H. Mendenhall
1999-02-18 15:04 ` Kostas Gewrgiou
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=200306072221.39006.rick420@high-on-linux.net \
--to=rick420@high-on-linux.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.