From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: Ion Badulescu <ionut@badula.org>,
Mikael Pettersson <mikpe@user.it.uu.se>
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 22:41:23 +0100 [thread overview]
Message-ID: <200302212241.23251.m.c.p@wolk-project.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0302211535510.17290-100000@guppy.limebrokerage.com>
On Friday 21 February 2003 21:42, Ion Badulescu wrote:
Hi Ion,
> And this is what I found: eliminating two lines from
> APIC_init_uniprocessor() makes the problem go away.
> diff -urNX diff_kernel_excludes linux-2.4.10-pre12/arch/i386/kernel/apic.c
> linux-2.4.10-pre11++/arch/i386/kernel/apic.c ---
> linux-2.4.10-pre12/arch/i386/kernel/apic.c Wed Feb 19 23:53:15 2003 +++
> linux-2.4.10-pre11++/arch/i386/kernel/apic.c Fri Feb 21 15:37:06 2003 @@
> -1087,9 +1087,6 @@
>
> connect_bsp_APIC();
>
> - phys_cpu_present_map = 1;
> - apic_write_around(APIC_ID, boot_cpu_id);
> -
> apic_pm_init2();
>
> setup_local_APIC();
>
> [patch against 2.4.10-pre12, but 2.4.21-pre4 is reasonably similar]
Don't do this. I am pretty sure it will break all Intels. I still cannot
understand why this fixes your AMD Athlon problem.
ciao, Marc
next prev parent reply other threads:[~2003-02-21 21:32 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
2003-02-21 20:42 ` Ion Badulescu
2003-02-21 21:41 ` Marc-Christian Petersen [this message]
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=200302212241.23251.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=ionut@badula.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@user.it.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
all inboxes | Powered by JetHome®