Messages in this thread | | | Date | Thu, 3 Jul 2003 14:15:08 -0700 | From | Andrew Morton <> | Subject | Re: 2.5.74-mm1 |
| |
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/
| |