Symmetric Multiprocessing (SMP) development
 help / color / mirror / Atom feed
From: "Vladimir G. Ivanovic" <vladimir@acm.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: u.milde@gdsys.de, linux-smp@vger.kernel.org
Subject: Re: SMP "unexpected IO-APIC"
Date: Mon, 15 Apr 2002 09:12:19 -0700	[thread overview]
Message-ID: <200204151612.g3FGCJp06320@bach.leonora.org> (raw)
In-Reply-To: Your message of "Mon, 15 Apr 2002 14:05:12 BST." <E16x6AS-000697-00@the-village.bc.nu>

The fix for this is to turn off MPS 1.4 support in your BIOS (i.e.
downgrade to MPS 1.1). There is no need to set "noapic".

--- Vladimir

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

"AC" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:

  >> The system is a Asus CUV4X-D motherboard with VIA Apollo Pro 133A
  >> chipset. The CPUs are two identical Pentium III Coppermine stepping 06.

  AC> What BIOS version do you have ? I've seen several reports of BIOS updates
  AC> being needed. Specifying "noapic" might also help
  AC> -
  AC> To unsubscribe from this list: send the line "unsubscribe linux-smp" in
  AC> the body of a message to majordomo@vger.kernel.org
  AC> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2002-04-15 16:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15  8:55 SMP "unexpected IO-APIC" u.milde
2002-04-15 13:05 ` Alan Cox
2002-04-15 16:12   ` Vladimir G. Ivanovic [this message]
2002-04-15 18:50 ` Jonathan Claxton
  -- strict thread matches above, loose matches on Subject: below --
2002-04-16 10:09 u.milde
2002-04-16 14:51 ` Randy.Dunlap

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=200204151612.g3FGCJp06320@bach.leonora.org \
    --to=vladimir@acm.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-smp@vger.kernel.org \
    --cc=u.milde@gdsys.de \
    /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