From: Dave Hansen <dave@linux.vnet.ibm.com>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>
Cc: mjw <mjw@linux.vnet.ibm.com>,
Nathan Lynch <nathanl@austin.ibm.com>,
Paul Mackerras <paulus@samba.org>
Subject: Nodes with no memory
Date: Fri, 21 Nov 2008 15:50:41 -0800 [thread overview]
Message-ID: <1227311441.11607.57.camel@nimitz> (raw)
I was handed off a bug report about a blade not booting with a, um
"newer" kernel. After turning on some debugging messages, I got this
ominous message:
node 1
NODE_DATA() = c000000000000000
Which obviously comes from here:
arch/powerpc/mm/numa.c
for_each_online_node(nid) {
unsigned long start_pfn, end_pfn;
unsigned long bootmem_paddr;
unsigned long bootmap_pages;
get_pfn_range_for_nid(nid, &start_pfn, &end_pfn);
/* Allocate the node structure node local if possible */
NODE_DATA(nid) = careful_allocation(nid,
sizeof(struct pglist_data),
SMP_CACHE_BYTES, end_pfn);
NODE_DATA(nid) = __va(NODE_DATA(nid));
memset(NODE_DATA(nid), 0, sizeof(struct pglist_data));
...
careful_allocation() returns a NULL physical address, but we go ahead
and run __va() on it, stick it in NODE_DATA(), and memset it. Yay!
I seem to recall that we fixed some issues with memoryless nodes a few
years ago, like around the memory hotplug days, but I don't see the
patches anywhere.
I'm thinking that we need to at least fix careful_allocation() to oops
and not return NULL, or check to make sure all it callers check its
return code. Plus, we probably also need to ensure that all ppc code
doing for_each_online_node() does not assume a valid NODE_DATA() for all
those nodes.
Any other thoughts?
I'll have a patch for the above issue sometime soon.
-- Dave
next reply other threads:[~2008-11-21 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 23:50 Dave Hansen [this message]
2008-11-22 0:49 ` Nodes with no memory Nathan Lynch
2008-11-22 1:17 ` Dave Hansen
2008-11-22 8:58 ` Milton Miller
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=1227311441.11607.57.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mjw@linux.vnet.ibm.com \
--cc=nathanl@austin.ibm.com \
--cc=paulus@samba.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