From: Christoph Lameter <clameter@engr.sgi.com>
To: Tomi Lapinlampi <lapinlam@vega.lnet.lut.fi>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, alokk@calsoftinc.com
Subject: Re: 2.6.14-rc2 early boot OOPS (mm/slab.c:1767)
Date: Tue, 27 Sep 2005 16:35:54 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0509271630050.11040@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20050927202858.GG1046@vega.lnet.lut.fi>
On Tue, 27 Sep 2005, Tomi Lapinlampi wrote:
> I'm getting the following OOPS with 2.6.14-rc2 on an Alpha.
Hmmm. I am not familiar with Alpha. The .config looks as if this is a
uniprocessor configuration? No NUMA?
What is the value of MAX_NUMNODES?
next prev parent reply other threads:[~2005-09-27 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 20:28 2.6.14-rc2 early boot OOPS (mm/slab.c:1767) Tomi Lapinlampi
2005-09-27 23:35 ` Christoph Lameter [this message]
2005-09-28 6:30 ` Tomi Lapinlampi
2005-09-28 6:47 ` Andrew Morton
2005-09-28 17:08 ` Christoph Lameter
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=Pine.LNX.4.62.0509271630050.11040@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=alokk@calsoftinc.com \
--cc=lapinlam@vega.lnet.lut.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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;
as well as URLs for NNTP newsgroup(s).