From: Andrew Morton <akpm@osdl.org>
To: Martin Bligh <mbligh@google.com>
Cc: apw@shadowen.org, linux-kernel@vger.kernel.org
Subject: Re: sparsemem panic in 2.6.17-rc5-mm1 and -mm2
Date: Tue, 6 Jun 2006 16:42:41 -0700 [thread overview]
Message-ID: <20060606164241.69d55238.akpm@osdl.org> (raw)
In-Reply-To: <4484D174.7080902@google.com>
On Mon, 05 Jun 2006 17:51:00 -0700
Martin Bligh <mbligh@google.com> wrote:
> http://test.kernel.org/abat/34264/debug/console.log
What sort of machine is this, anyway?
> WARNING: Not an IBM x440/NUMAQ and CONFIG_NUMA enabled!
And is it expected that ZONE_NORMAL only has 384MB? That seems awfully low
for a 64GB x86 machine. Could be that we went oom because we chose to
allocate really big hash tables, based on the total amount of memory?
next prev parent reply other threads:[~2006-06-06 23:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-06 0:51 sparsemem panic in 2.6.17-rc5-mm1 and -mm2 Martin Bligh
2006-06-06 3:07 ` Andrew Morton
2006-06-06 5:19 ` KAMEZAWA Hiroyuki
2006-06-06 5:36 ` Yasunori Goto
2006-06-06 7:27 ` Andrew Morton
2006-06-07 0:43 ` KAMEZAWA Hiroyuki
2006-06-07 4:58 ` Andrew Morton
2006-06-07 5:36 ` Rusty Russell
2006-06-07 5:50 ` Andrew Morton
2006-06-07 6:49 ` Rusty Russell
2006-06-07 9:26 ` Andy Whitcroft
2006-06-07 16:29 ` Andrew Morton
2006-06-07 16:35 ` Andrew Morton
2006-06-07 17:50 ` Andy Whitcroft
2006-06-15 12:28 ` [PATCH] zone handle unaligned zone boundaries Andy Whitcroft
2006-06-07 17:22 ` sparsemem panic in 2.6.17-rc5-mm1 and -mm2 Andy Whitcroft
2006-06-06 23:42 ` Andrew Morton [this message]
2006-06-07 9:16 ` Mel Gorman
2006-06-07 17:38 ` Andy Whitcroft
2006-06-07 17:41 ` Andy Whitcroft
-- strict thread matches above, loose matches on Subject: below --
2006-06-06 3:50 Chuck Ebbert
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=20060606164241.69d55238.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
/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