Symmetric Multiprocessing (SMP) development
 help / color / mirror / Atom feed
From: "Vladimir G. Ivanovic" <vladimir@acm.org>
To: linux-smp@vger.kernel.org
Cc: Matthias Kleine <kleine_matthias@gmx.de>
Subject: Re: Why is "noapic" with some Dual P3 boards necessary?
Date: Tue, 29 Oct 2002 09:03:23 -0800	[thread overview]
Message-ID: <200210291703.g9TH3Np26310@bach.leonora.org> (raw)
In-Reply-To: Your message of "Sun, 27 Oct 2002 13:08:04 +0200." <200210271208.04738.kleine_matthias@gmx.de>

It is not necessary to boot a CUV4X-DLS board with the "noapic" option.

I have been running a CUV4X-DLS board (== CUV4X-D + LAN + SCSI) for over
a year now with APIC. You must however fall back to MPS 1.1 from the
default MPS 1.4. (It's a BIOS setting.) 

I suspect that a CUV4X-D board will have the same behavior.

--- Vladimir

------------------------------------------------------------------------
Vladimir G. Ivanovic                        http://leonora.org/~vladimir
2770 Cowper St.                                         vladimir@acm.org
Palo Alto, CA 94306-2447                                 +1 650 678 8014

"MK" == Matthias Kleine <kleine_matthias@gmx.de> writes:

  MK> I am using an ASUS CUV4X-D mainboard since the days this
  MK> board came out (about beginning of 2001). Right from the
  MK> beginning, it was necessary to start the kernel with the "noapic"
  MK> option. This is, of course, a limitation of an SMP system, because
  MK> there are not all the IRQ's of both CPU's available when booted
  MK> "noapic". So I guess it must have some strong technical reason
  MK> why this kind of board cannot be used in apic mode. Can anybody
  MK> explain me the very reason why this is the case?

  parent reply	other threads:[~2002-10-29 17:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-27 11:08 Why is "noapic" with some Dual P3 boards necessary? Matthias Kleine
2002-10-27 11:42 ` Alan Cox
2002-10-29 17:03 ` Vladimir G. Ivanovic [this message]
2002-10-29 18:42   ` Matthias Kleine
2002-10-29 18:50     ` Dr. Michael Weller
2002-10-30 19:20       ` Bill Davidsen
2002-10-30 22:11         ` Matthias Kleine
2002-10-30 23:48           ` Alan Cox
2002-10-31  2:54         ` vladimir
2002-10-31  3:27           ` Eff Norwood
2002-11-02 19:18             ` Vladimir G. Ivanovic
2002-10-31 20:29           ` Bill Davidsen

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=200210291703.g9TH3Np26310@bach.leonora.org \
    --to=vladimir@acm.org \
    --cc=kleine_matthias@gmx.de \
    --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