From: Dave Hansen <dave.hansen@intel.com>
To: Yinghai Lu <yinghai@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Ingo Molnar <mingo@elte.hu>
Cc: 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 07:25:14 -0800 [thread overview]
Message-ID: <52E285DA.1090107@intel.com> (raw)
In-Reply-To: <52E28067.1060507@intel.com>
On 01/24/2014 07:01 AM, Dave Hansen 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.
And with my second (lots of debugging enabled) config, I get the
mem_map[] oops. In other words, none of the reverts or patches are
helping either of the conditions that I'm able to trigger.
--
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 15:25 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 [this message]
2014-01-24 17:45 ` Yinghai Lu
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=52E285DA.1090107@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--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 \
--cc=yinghai@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