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 15:47:17 +0100 [thread overview]
Message-ID: <15958.15349.873243.599197@gargle.gargle.HOWL> (raw)
In-Reply-To: <Pine.LNX.4.44.0302202058140.16982-100000@moisil.badula.org>
Ion Badulescu writes:
> On Thu, 20 Feb 2003, Jeff Garzik wrote:
>
> > Ion Badulescu wrote:
> > > A UP kernel compiled with CONFIG_X86_LOCAL_APIC=y dies a very horrible
> > > death on an SMP Athlon motherboard (Tyan S2462 and S2468), flooding the
> > > console with the following messages:
> >
> > IMO just assume this option is just broken, unless you absolutely need it.
>
> My only boxes on which this is a problem are the SMP athlons, and only
> with UP kernels...
Chipset?
Is the second CPU installed or not?
If the second CPU is installed, has it been disabled in BIOS?
Relevant config? What combinations of UP_APIC and UP_IOAPIC have
you been using? Has ACPI been enabled or not?
A plain kernel with UP_APIC but no SMP or UP_IOAPIC shouldn't
provoke the kinds of APIC errors you mentioned, unless the APIC
bus is noisy due to a missing second CPU (just a theory).
> Anyway, I'd like to get to the bottom of this, since I've narrowed it down
> so much. Anyone know who submitted the APIC changes in 2.4.10-pre12?
Ingo Molnar, Maciej W. Rozycki, and myself.
> debug it myself, but I know next to nothing about the APIC. If you know
> where to get some documentation, I'm more than willing to give it a shot.
Intel's IA32 manual set, Volume 3, is required reading.
/Mikael
next prev parent reply other threads:[~2003-02-21 14:37 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 [this message]
2003-02-21 15:09 ` Ion Badulescu
2003-02-21 15:41 ` Mikael Pettersson
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.15349.873243.599197@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®