From: Jiri Slaby <jirislaby@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Ingo Molnar <mingo@redhat.com>,
tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Andi Kleen <andi@firstfloor.org>,
the arch/x86 maintainers <x86@kernel.org>,
Mike Travis <travis@sgi.com>,
nickpiggin@yahoo.com.au
Subject: Re: [PATCH 1/1] MM: virtual address debug
Date: Wed, 18 Jun 2008 18:11:51 +0200 [thread overview]
Message-ID: <485933C7.8050801@gmail.com> (raw)
In-Reply-To: <20080618135928.GA12803@elte.hu>
Ingo Molnar napsal(a):
> No NUMA configuration found
> Faking a node at 0000000000000000-000000003fff0000
> Entering add_active_range(0, 0, 159) 0 entries of 25600 used
> Entering add_active_range(0, 256, 262128) 1 entries of 25600 used
> Bootmem setup node 0 0000000000000000-000000003fff0000
> NODE_DATA [000000000000a000 - 000000000003dfff]
> PANIC: early exception 06 rip 10:ffffffff80ba7531 error 0 cr2 f06f53
> Pid: 0, comm: swapper Not tainted 2.6.26-rc6 #7709
>
> Call Trace:
> [<ffffffff80b9c196>] early_idt_handler+0x56/0x6a
> [<ffffffff80ba7531>] setup_node_bootmem+0x12a/0x2d4
Hmm, it's at
nid = phys_to_nid(nodedata_phys);
and
VIRTUAL_BUG_ON((addr >> memnode_shift) >= memnodemapsize);
triggers. Apparently memnodemapsize is not available for real numas. Going
to remove the test and respin the patch with Nick's comment applied.
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-06-18 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 11:56 Jiri Slaby
2008-06-18 12:12 ` Ingo Molnar
2008-06-18 13:59 ` Ingo Molnar
2008-06-18 14:11 ` Jiri Slaby
2008-06-18 16:11 ` Jiri Slaby [this message]
2008-06-18 18:35 ` [PATCH v2] " Jiri Slaby
2008-06-19 11:34 ` Ingo Molnar
2008-06-18 12:51 ` [PATCH 1/1] " Nick Piggin
2008-06-18 13:41 ` Jiri Slaby
2008-06-18 14:01 ` Nick Piggin
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=485933C7.8050801@gmail.com \
--to=jirislaby@gmail.com \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=nickpiggin@yahoo.com.au \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=x86@kernel.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