Re: 32bit panic on 4 sockets

From: Ingo Molnar
Date: Wed Mar 04 2009 - 06:07:41 EST



* Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:

> On Wed, 2009-03-04 at 11:34 +0100, Ingo Molnar wrote:
> > * Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:
> >
> > > On Tue, 2009-03-03 at 22:57 -0800, Yinghai Lu wrote:
> > > > On Tue, Mar 3, 2009 at 6:05 PM, Tejun Heo <tj@xxxxxxxxxx> wrote:
> > > > > Looks like a genuine bootmem bug. Cc'ing Johannes and
> > > > > quoting whole body.
> > > >
> > > > it is x86 32bit numa code problem. it assume bootmem will
> > > > sit on first node only.
> > >
> > > Seems a bit daft to run a 32bit kernel on such a machine.. at
> > > some point we should just give up and not push this 32 bit
> > > madness any further.
> >
> > it works just fine on a lot of systems - and since we keep
> > unifying a lot of these codepaths we are better off keeping it
> > all working.
>
> Sure, but eg. running with 16GB on a 32bit system just isn't
> going to work well. Same with large cpu-count, at some point
> you might be able to boot, but not much else.

Sure.

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/