mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@user.it.uu.se>
To: Ion Badulescu <ionut@badula.org>
Cc: Jeff Garzik <jgarzik@pobox.com>, <linux-kernel@vger.kernel.org>
Subject: Re: UP local APIC is deadly on SMP Athlon
Date: Fri, 21 Feb 2003 16:41:35 +0100	[thread overview]
Message-ID: <15958.18607.772631.502418@gargle.gargle.HOWL> (raw)
In-Reply-To: <Pine.LNX.4.44.0302210959090.17290-100000@guppy.limebrokerage.com>

Ion Badulescu writes:
 > AMD 760MP and 760MPX, both have this problem.

Ok, AMD's chipsets are reasonable.

 > > Is the second CPU installed or not?
 > 
 > Installed.
 > 
 > > If the second CPU is installed, has it been disabled in BIOS?
 > 
 > It hasn't been disabled (the BIOS doesn't have that option).

That kills the noisy-bus theory.

 > Well, the second CPU is there, and there are no problems with the APIC and 
 > the IO-APIC if the kernel is compiled with CONFIG_SMP=y. Only the UP case 
 > causes the problem. So I don't think the bus itself is noisy, unless the 
 > noises are produced by the second CPU somehow, and we can't do anything 
 > about it because we're not touching that second CPU.

An UP_APIC kernel without IOAPIC shouldn't generate any APIC bus messages.
Have you checked if the BIOS has an option for choosing "PIC" or "APIC"
interrupt delivery? Try setting it to PIC mode.

 > I know that AMD's K7 APIC is supposed to be compatible with the Intel P6 
 > APIC, but do you think there might be some incompatibility between that 
 > that causes this? Or perhaps some undefined behavior we rely on, and which 
 > is different between Intel and AMD?...

None that I know of, to both questions.
All problems I've seen have been caused by non-Intel chipsets.

/Mikael

  reply	other threads:[~2003-02-21 15:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 15:05 Ion Badulescu
2003-02-21  0:12 ` Jeff Garzik
2003-02-21  2:03   ` Ion Badulescu
2003-02-21 14:47     ` Mikael Pettersson
2003-02-21 15:09       ` Ion Badulescu
2003-02-21 15:41         ` Mikael Pettersson [this message]
2003-02-21 20:42         ` Ion Badulescu
2003-02-21 21:41           ` Marc-Christian Petersen
2003-02-21 21:49             ` Ion Badulescu
2003-02-22  0:38 Mikael Pettersson
2003-02-22  8:05 ` Ion Badulescu
2003-02-22  9:06   ` Willy Tarreau
2003-02-22  9:19     ` Willy Tarreau

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=15958.18607.772631.502418@gargle.gargle.HOWL \
    --to=mikpe@user.it.uu.se \
    --cc=ionut@badula.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®