From: Albert Sodyl <exitware@shaw.ca>
To: linux-smp@vger.kernel.org
Subject: WARNING: unexpected IO-APIC
Date: Sun, 27 Jul 2003 17:25:16 -0700 [thread overview]
Message-ID: <1059351916.19256.8.camel@localhost> (raw)
I am using Linux version 2.4.20-gentoo-r5 (gcc version 3.2.3 20030422
(Gentoo Linux 1.4 3.2.3-r1, propolice)).
Strict kernel warning on uniprocessor AMD Athlon XP 2000+ on Asus A7V333
motherboard, ACPI and APIC enabled.
Log:
ENABLING IO-APIC IRQs
init IO_APIC IRQs
IO-APIC (apicid-pin) 2-0, 2-16, 2-17, 2-18, 2-19, 2-20, 2-21, 2-22,
2-23 not connected.
..TIMER: vector=0x31 pin1=2 pin2=0
number of MP IRQ sources: 16.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................
IO APIC #2......
.... register #00: 02000000
....... : physical APIC id: 02
.... register #01: 00178002
....... : max redirection entries: 0017
....... : PRQ implemented: 1
....... : IO APIC version: 0002
WARNING: unexpected IO-APIC, please mail
to linux-smp@vger.kernel.org
.... IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 000 00 1 0 0 0 0 0 0 00
01 001 01 0 0 0 0 0 1 1 39
02 001 01 0 0 0 0 0 1 1 31
03 001 01 0 0 0 0 0 1 1 41
04 001 01 0 0 0 0 0 1 1 49
05 001 01 0 0 0 0 0 1 1 51
06 001 01 0 0 0 0 0 1 1 59
07 001 01 0 0 0 0 0 1 1 61
08 001 01 0 0 0 0 0 1 1 69
09 001 01 1 1 0 1 0 1 1 71
0a 001 01 0 0 0 0 0 1 1 79
0b 001 01 0 0 0 0 0 1 1 81
0c 001 01 0 0 0 0 0 1 1 89
0d 001 01 0 0 0 0 0 1 1 91
0e 001 01 0 0 0 0 0 1 1 99
0f 001 01 0 0 0 0 0 1 1 A1
10 000 00 1 0 0 0 0 0 0 00
11 000 00 1 0 0 0 0 0 0 00
12 000 00 1 0 0 0 0 0 0 00
13 000 00 1 0 0 0 0 0 0 00
14 000 00 1 0 0 0 0 0 0 00
15 000 00 1 0 0 0 0 0 0 00
16 000 00 1 0 0 0 0 0 0 00
17 000 00 1 0 0 0 0 0 0 00
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:5
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:9
IRQ10 -> 0:10
IRQ11 -> 0:11
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
.................................... done.
next reply other threads:[~2003-07-28 0:25 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 0:25 Albert Sodyl [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-26 7:50 WARNING: unexpected IO-APIC BURKHARD JOCHEN
2004-08-11 14:39 Deepak Dogra
2004-08-06 10:19 Chris Kant
2004-06-06 19:18 Graham Wilson
2004-06-05 11:53 Philipp Walderdorff
2004-05-25 5:52 Amedeo Minutolo
2004-02-09 21:07 ,,,
2003-12-22 3:32 Scott Weber
2003-11-12 15:38 Nick Starai
2003-06-03 21:51 idiot [James Green]
2003-05-08 15:05 bl8n8r
2003-04-19 21:45 Daniel Bergman
2003-03-10 17:10 Bob Schuknecht
2003-02-28 15:10 Bernard and Jennifer Cohen
2003-02-27 16:51 DR Aldrich
2003-02-21 19:17 Radek Aster
2003-02-16 1:23 rod
2003-02-03 19:35 Matt King
2003-02-04 12:26 ` Alan Cox
2003-01-12 9:24 Sakari Aaltonen
2003-01-09 20:04 Anderson Oliveira da Silva
2003-01-03 20:16 Jeff Frost
2002-12-22 11:53 John Rye
2002-12-25 21:35 ` Alan Cox
2002-12-18 19:48 Kazik
2002-12-04 19:02 Christian Birchinger
2002-11-26 22:23 Warning " Rafal Cichosz
2002-11-16 2:50 WARNING: " Chia-Hsing Yu
2002-11-09 3:42 PASTOR Michel
2002-11-09 3:41 PASTOR Michel
2002-10-24 14:58 warning " Thomas Björnell
2002-10-25 9:56 ` Maciej W. Rozycki
2002-10-03 13:33 WARNING: " Brian Jonnes
2002-10-03 13:43 ` David McIlwraith
2002-10-04 6:52 ` Brian Jonnes
2002-10-03 15:02 ` Randy.Dunlap
2002-10-04 6:54 ` Brian Jonnes
2002-10-08 0:40 ` Randy.Dunlap
2002-10-16 13:19 ` Maciej W. Rozycki
2002-10-18 0:59 ` Randy.Dunlap
2002-10-01 22:00 Avinesh Bangar
2002-08-29 16:06 brian
2002-08-14 20:04 james.oden
2002-08-15 1:14 ` Alan Cox
2002-07-17 13:06 countdown
2002-07-12 17:22 dwh
2002-07-12 18:07 ` Alan Cox
2002-07-08 16:31 Enkh Tumenbayar
2002-07-08 18:43 ` WARNING: " Vladimir G. Ivanovic
2002-07-08 20:22 ` E. Robert Bogusta
2002-07-09 16:44 ` Vladimir G. Ivanovic
2002-07-08 13:35 Michael Arndt
2002-06-23 23:29 Josh Wilcox
2002-06-11 10:06 Philipp Schulte
2002-05-15 14:48 Melissa Vandenbrink
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=1059351916.19256.8.camel@localhost \
--to=exitware@shaw.ca \
--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