From: Ricky McInnes <rick420@high-on-linux.net>
To: linux-smp@vger.kernel.org
Subject: Kernel 2.4.21 APIC error
Date: Tue, 17 Jun 2003 23:32:30 -0400 [thread overview]
Message-ID: <200306172332.30531.rick420@high-on-linux.net> (raw)
Hello,
Emailing this because of the message via syslog.
Heres the output:
Jun 17 23:23:45 blazin kernel: IO APIC #2......
Jun 17 23:23:45 blazin kernel: .... register #00: 02000000
Jun 17 23:23:45 blazin kernel: ....... : physical APIC id: 02
Jun 17 23:23:45 blazin kernel: ....... : Delivery Type: 0
Jun 17 23:23:45 blazin kernel: ....... : LTS : 0
Jun 17 23:23:45 blazin kernel: .... register #01: 00178020
Jun 17 23:23:45 blazin kernel: ....... : max redirection entries: 0017
Jun 17 23:23:45 blazin kernel: ....... : PRQ implemented: 1
Jun 17 23:23:45 blazin kernel: ....... : IO APIC version: 0020
Jun 17 23:23:45 blazin kernel: .... register #02: 00178020
Jun 17 23:23:45 blazin kernel: ....... : arbitration: 00
Jun 17 23:23:45 blazin kernel: An unexpected IO-APIC was found. If this kernel
release is less than
Jun 17 23:23:45 blazin kernel: three months old please report this to
linux-smp@vger.kernel.org
This is an Intel D865PERL motherboard with a 2.4ghz P4 800MHZ FSB with
Hyper-Thread enabled in the Bios. I compiled the kernel with SMP support,
and 2 CPUS do show up, BUT, a "cat /proc/interrupts" shows this:
CPU0 CPU1
0: 32731 0 IO-APIC-edge timer
1: 223 0 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
8: 1 0 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
12: 6301 0 IO-APIC-edge PS/2 Mouse
14: 9114 0 IO-APIC-edge ide0
15: 110 0 IO-APIC-edge ide1
16: 11619 0 IO-APIC-level usb-uhci, usb-uhci, nvidia
17: 4324 0 IO-APIC-level Intel ICH5
18: 0 0 IO-APIC-level usb-uhci
19: 258 0 IO-APIC-level usb-uhci, eth0
Anything I can help with?
Ricky McInnes
next reply other threads:[~2003-06-18 3:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 3:32 Ricky McInnes [this message]
2003-06-18 12:12 ` Kernel 2.4.21 APIC error Maciej W. Rozycki
2003-06-21 20:04 ` Earle R. Nietzel
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=200306172332.30531.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox