mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: [ACPI] IO-APIC on MS-6163 (2.4.23). ACPI?
Date: Wed, 10 Dec 2003 07:55:16 -0600	[thread overview]
Message-ID: <20031210135516.GA2687@dbz.icequake.net> (raw)
In-Reply-To: <16343.8777.389445.2007@alkaid.it.uu.se>

[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]


On Wed, Dec 10, 2003 at 02:40:25PM +0100, Mikael Pettersson wrote:
> Ryan Underwood writes:
>  > 
>  > Attached dmesg and interrupts with acpi=off.  Also attached kernel
>  > config.
>  > 
>  > As you see, it acknowledges a local APIC but mentions nothing about
>  > IO-APIC.  So I guess this isn't ACPI issue after all.  But, I wonder why
>  > the IO-APIC isn't being used on this board anymore.  There was a
>  > blacklist entry for it, but it was removed after it was discovered to be
>  > in error.
> 
> Your dmesg log doesn't mention any MP-table. With neither ACPI MADT
> nor an MP-table the kernel has no way of knowing about any I/O-APIC.
> 
> You do have UP_IOAPIC enabled, so the kernel should look for it.
> Please check your BIOS settings, and try with no ACPI at all in the kernel
> (just to verify that acpi=off doesn't prevent MP-table parsing).

I went back and found the messages corresponding to our previous
discussions:

http://www.cs.helsinki.fi/linux/linux-kernel/2003-23/1675.html

Looks like again I've confused the local APIC with the IO-APIC regarding
that blacklist entry.  However, I thought 440BX had a IO-APIC built-in
to the southbridge.  Again, that was proved to be wrong by examining the
integrator's guide:
ftp://download.intel.com/design/chipsets/designex/29063401.pdf

page 99 of the PDF says:
"An I/O APIC is required for a DP system and optional for a UP system."

So it looks like I've never had an I/O-APIC on this board at all, only a
local APIC, and this thread is thus a waste of time. :)

In any case, thanks for leading me to the right answer!

-- 
Ryan Underwood, <nemesis@icequake.net>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-12-10 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-10  2:56 Yu, Luming
2003-12-10 12:55 ` Ryan Underwood
2003-12-10 13:40   ` Mikael Pettersson
2003-12-10 13:55     ` Ryan Underwood [this message]

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=20031210135516.GA2687@dbz.icequake.net \
    --to=nemesis-lists@icequake.net \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.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

Powered by JetHome