From: "Randy.Dunlap" <rddunlap@osdl.org>
To: linux-smp@vger.kernel.org
Cc: mattias@kregert.se
Subject: Re: WARNING: unexpected IO-APIC, please mail to linux-smp@vger.kernel.org
Date: Tue, 27 May 2003 13:52:34 -0700 [thread overview]
Message-ID: <20030527135234.3e8c488a.rddunlap@osdl.org> (raw)
In-Reply-To: <33093.4.64.196.31.1054015426.squirrel@www.osdl.org>
On Mon, 26 May 2003 23:03:46 -0700 (PDT) "Randy.Dunlap" <rddunlap@osdl.org> wrote:
| > Good morning,
| >
| > I think you might be interested in this log.
| >
| > My hardware:
| > - - - - - - -
| > Motherboard: Abit IC7
| > Chipset: Intel 82875P (MCH) + 82801EB (ICH5R)
| > Memory: 2 x DDR400 256MB CAS 2.5 (Dual DDR Mode Enabled)
| > CPU: 1 x Pentium-4 2.4Ghz 800Mhz PSB
| >
| > Please send me a mail if you need more information.
| >
| > /Mattias
| >
| >
| > --------
| > BOOT LOG
| > --------
| > ---snip---
| > ENABLING IO-APIC IRQs
| > Setting 2 in the phys_id_present_map
| > ...changing IO-APIC physical APIC ID to 2 ... ok.
| > init IO_APIC IRQs
| > IO-APIC (apicid-pin) 2-0, 2-5, 2-9, 2-10, 2-11, 2-22 not connected.
| > ..TIMER: vector=0x31 pin1=2 pin2=0
| > number of MP IRQ sources: 24.
| > number of IO-APIC #2 registers: 24.
| > testing the IO APIC.......................
| >
| > IO APIC #2......
| > .... register #00: 02000000
| > ....... : physical APIC id: 02
| > .... register #01: 00178020
| > ....... : max redirection entries: 0017
| > ....... : PRQ implemented: 1
| > ....... : IO APIC version: 0020
| > .... register #02: 00178020
| > ....... : arbitration: 00
| > WARNING: unexpected IO-APIC, please mail
| > to linux-smp@vger.kernel.org
| > .... IRQ redirection table:
|
| That looks odd to me. Reg. 01 and Reg. 02 are both 00178020 ?????
| I'll look into it tomorrow (my time) unless someone else does or already
| knows about this.
The Intel 82801EB (ICH5) datasheet does not specify that this chipset
has a register 2 for the IO APIC. We need to find a way to recognize
this and ignore reg. 02 (a way other than register 1's IO APIC
version value, which is currently being used).
I'm still looking into this.
--
~Randy
next prev parent reply other threads:[~2003-05-27 20:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 5:53 WARNING: unexpected IO-APIC, please mail to linux-smp@vger.kernel.org Mattias Kregert
2003-05-27 6:03 ` Randy.Dunlap
2003-05-27 20:52 ` Randy.Dunlap [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-15 13:06 Rinat Yangurazov
2004-10-18 3:15 David Hill
2004-09-10 17:35 Agustín Ciciliani
2003-11-14 19:58 Ingo Claro
2003-07-18 20:48 M. J. Blom
2003-05-03 7:54 Joshua McClintock
2003-02-09 21:20 Eli
2003-01-13 7:30 D. Nathan Cookson
2002-11-29 19:52 R. Lemos
2002-11-22 2:49 Craig Anderson
2002-11-22 9:19 ` Dave Jones
2002-11-22 13:35 ` Alan Cox
2002-11-22 15:28 ` Robert M. Hyatt
2002-11-25 0:53 ` Alan Cox
2002-11-25 3:26 ` Robert M. Hyatt
2002-11-25 13:15 ` Alan Cox
2002-11-25 17:25 ` Robert M. Hyatt
2002-11-25 17:57 ` Mihai Burcea
2002-10-12 9:33 Trevor Lee
2002-10-13 3:12 ` Randy.Dunlap
2002-10-21 22:57 ` Alan Cox
2002-08-10 18:41 Chris McGinlay
2002-01-16 21:23 Tim Lee
2003-01-30 18:48 ` Alan Cox
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=20030527135234.3e8c488a.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-smp@vger.kernel.org \
--cc=mattias@kregert.se \
/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