From: Yinghai Lu <yinghai@kernel.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Grygorii Strashko <grygorii.strashko@ti.com>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Panic on 8-node system in memblock_virt_alloc_try_nid()
Date: Fri, 24 Jan 2014 09:45:17 -0800 [thread overview]
Message-ID: <CAE9FiQVy+8CF5qwnyL8YGzqwKOJF+y7N_+reAXWw7p8-BaVQPg@mail.gmail.com> (raw)
In-Reply-To: <52E28067.1060507@intel.com>
On Fri, Jan 24, 2014 at 7:01 AM, Dave Hansen <dave.hansen@intel.com> wrote:
> There are two failure modes I'm seeing: one when (failing to) allocate
> the first node's mem_map[], and a second where it oopses accessing the
> numa_distance[] table. This is the numa_distance[] one, and it happens
> even with the patch you suggested applied.
>
>> [ 0.000000] memblock_find_in_range_node():239
>> [ 0.000000] __memblock_find_range_top_down():150
>> [ 0.000000] __memblock_find_range_top_down():152 i: 600000001
>> [ 0.000000] memblock_find_in_range_node():241 ret: 2147479552
>> [ 0.000000] memblock_reserve: [0x0000007ffff000-0x0000007ffff03f] flags 0x0 numa_set_distance+0xd2/0x252
that address is wrong.
Can you post whole log with current linus' tree + two patches that I
sent out yesterday?
>> [ 0.000000] numa_distance phys: 7ffff000
>> [ 0.000000] numa_distance virt: ffff88007ffff000
>> [ 0.000000] numa_distance size: 64
>> [ 0.000000] numa_alloc_distance() accessing numa_distance[] at byte: 0
>> [ 0.000000] BUG: unable to handle kernel paging request at ffff88007ffff000
--
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:[~2014-01-24 17:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 22:49 Dave Hansen
2014-01-24 0:27 ` Dave Hansen
2014-01-24 3:43 ` Santosh Shilimkar
2014-01-24 5:55 ` Yinghai Lu
2014-01-24 6:38 ` Santosh Shilimkar
2014-01-24 6:56 ` Santosh Shilimkar
2014-01-24 7:04 ` Yinghai Lu
2014-01-24 7:22 ` Santosh Shilimkar
2014-01-24 7:46 ` Yinghai Lu
2014-01-24 7:54 ` Santosh Shilimkar
2014-01-24 6:57 ` Yinghai Lu
2014-01-24 7:04 ` Andrew Morton
2014-01-24 15:01 ` Dave Hansen
2014-01-24 15:25 ` Dave Hansen
2014-01-24 17:45 ` Yinghai Lu [this message]
2014-01-24 18:09 ` Dave Hansen
2014-01-24 18:13 ` Yinghai Lu
2014-01-24 18:19 ` Dave Hansen
2014-01-24 18:24 ` Yinghai Lu
2014-01-24 18:42 ` Dave Hansen
2014-01-24 18:51 ` Yinghai Lu
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=CAE9FiQVy+8CF5qwnyL8YGzqwKOJF+y7N_+reAXWw7p8-BaVQPg@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=grygorii.strashko@ti.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=santosh.shilimkar@ti.com \
--cc=tj@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