From: Andrew Morton <akpm@osdl.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.6-rc2-bk5 mm/slab.c change broke x86-64 SMP
Date: Fri, 30 Apr 2004 11:27:04 -0700 [thread overview]
Message-ID: <20040430112704.3dca3c4c.akpm@osdl.org> (raw)
In-Reply-To: <200404301611.i3UGBkdK026345@harpo.it.uu.se>
Mikael Pettersson <mikpe@csd.uu.se> wrote:
>
> The change to mm/slab.c between 2.6.6-rc2-bk4 and -bk5
> broke x86-64 SMP. The symptoms are general protection
> faults in __switch_to shortly after init starts, and
> then the machine is dead. (Can't be more specific, my
> box can't log early boot oopses.)
>
> I'm only seeing this with x86-64 SMP; x86-64 UP and i386
> SMP on the same machine (Athlon64 UP) have no problems.
>
> Reverting 2.6.6-rc2-bk5's change to mm/slab.c eliminates
> the problem.
The "-bk5" terminology doesn't mean much to people who use bitkeeper or who
use http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/ - I assume
you refer to the alignment changes?
Does this fix?
diff -puN include/asm-x86_64/processor.h~a include/asm-x86_64/processor.h
--- 25/include/asm-x86_64/processor.h~a Fri Apr 30 11:24:58 2004
+++ 25-akpm/include/asm-x86_64/processor.h Fri Apr 30 11:25:28 2004
@@ -20,6 +20,8 @@
#include <asm/mmsegment.h>
#include <linux/personality.h>
+#define ARCH_MIN_TASKALIGN L1_CACHE_BYTES
+
#define TF_MASK 0x00000100
#define IF_MASK 0x00000200
#define IOPL_MASK 0x00003000
_
next prev parent reply other threads:[~2004-04-30 18:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 16:11 Mikael Pettersson
2004-04-30 18:21 ` Jonathan Corbet
2004-04-30 18:27 ` Andrew Morton [this message]
2004-04-30 19:29 ` Jonathan Corbet
2004-04-30 20:31 ` Andrew Morton
2004-04-30 19:33 ` R. J. Wysocki
2004-04-30 20:24 ` Andrew Morton
2004-05-01 1:48 ` Andi Kleen
2004-05-01 2:01 ` Andrew Morton
2004-05-01 2:02 ` Andi Kleen
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=20040430112704.3dca3c4c.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.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
Powered by JetHome