Date: Thu, 3 Jul 2003 14:15:08 -0700
From: Andrew Morton <akpm@osdl.org>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: zboszor@freemail.hu, linux-kernel@vger.kernel.org
Subject: Re: 2.5.74-mm1
Message-Id: <20030703141508.796e4b82.akpm@osdl.org>
In-Reply-To: <20030703200858.GA31084@hh.idb.hist.no>
References: <3F0407D1.8060506@freemail.hu>
	<3F042AEE.2000202@freemail.hu>
	<20030703122243.51a6d581.akpm@osdl.org>
	<20030703200858.GA31084@hh.idb.hist.no>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1262
Lines: 38

Helge Hafting <helgehaf@aitel.hist.no> wrote:
>
> On Thu, Jul 03, 2003 at 12:22:43PM -0700, Andrew Morton wrote:
> > Boszormenyi Zoltan <zboszor@freemail.hu> wrote:
> > >
> > > Hi,
> > > 
> > > I actually tried it. It seems that although I compiled an SMP kernel, it 
> > > does not use both CPUs.
> > 
> > You're right.  The kernel sort-of saw the second CPU but it appears to have
> > not come up.
> > 
> I may have this problem on my dual celeron.  I noticed X got sluggish
> while generating a key for mozilla - very strange on a dual
> but I put it down to the scheduler changes.
> 
> Looking at dmesg I see that both is detected, and it claims
> both are "activated", but I get this a little later:
> 
> Starting migration thread for cpu 0
> Bringing up 1
> CPU 1 IS NOW UP!
> Starting migration thread for cpu 1
> CPUS done 2
> mtrr: v2.0 (20020519)
> 
> I never get a CPU 2 IS NOW UP (or CPU 0)
> 

ok.  If you're feeling keen could you please revert the cpumask_t patch.

And please send the .config, thanks.
-
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/