Date: Fri, 30 Apr 2004 13:31:10 -0700
From: Andrew Morton <akpm@osdl.org>
To: corbet@lwn.net (Jonathan Corbet)
Cc: linux-kernel@vger.kernel.org, mikpe@csd.uu.se, ak@suse.de
Subject: Re: [BUG] 2.6.6-rc2-bk5 mm/slab.c change broke x86-64 SMP
Message-Id: <20040430133110.5b9d293f.akpm@osdl.org>
In-Reply-To: <20040430192911.14289.qmail@lwn.net>
References: <20040430112704.3dca3c4c.akpm@osdl.org>
	<20040430192911.14289.qmail@lwn.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1157
Lines: 30

corbet@lwn.net (Jonathan Corbet) wrote:
>
> > 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
> > +
> 
> That made my x86_64 boot problem go away; with that patch the system comes
> up just fine.

OK, thanks.  It broke parisc too...

> Now I have weird display problems with my Radeon card instead.  Ever seen X
> running 100% in kernel space, unkillable?

I did, about a year ago.  It was spinning madly in some ioctl waiting for a
bit in a device register to change state.  Are you able to generate a
kernel profile while it's being silly?  That will tell us where it's stuck.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/