linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Dave Hansen <dave.hansen@intel.com>,
	"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>, 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 01:38:14 -0500	[thread overview]
Message-ID: <52E20A56.1000507@ti.com> (raw)
In-Reply-To: <CAE9FiQX9kTxnaqpWNgg3dUzr7+60YCrEx3q3xxO-G1n6z64xVQ@mail.gmail.com>

Yinghai,

On Friday 24 January 2014 12:55 AM, Yinghai Lu wrote:
> On Thu, Jan 23, 2014 at 2:49 PM, Dave Hansen <dave.hansen@intel.com> wrote:
>> > Linus's current tree doesn't boot on an 8-node/1TB NUMA system that I
>> > have.  Its reboots are *LONG*, so I haven't fully bisected it, but it's
>> > down to a just a few commits, most of which are changes to the memblock
>> > code.  Since the panic is in the memblock code, it looks like a
>> > no-brainer.  It's almost certainly the code from Santosh or Grygorii
>> > that's triggering this.
>> >
>> > Config and good/bad dmesg with memblock=debug are here:
>> >
>> >         http://sr71.net/~dave/intel/3.13/
>> >
>> > Please let me know if you need it bisected further than this.
> Please check attached patch, and it should fix the problem.
> 

[...]

> 
> Subject: [PATCH] x86: Fix numa with reverting wrong memblock setting.
> 
> Dave reported Numa on x86 is broken on system with 1T memory.
> 
> It turns out
> | commit 5b6e529521d35e1bcaa0fe43456d1bbb335cae5d
> | Author: Santosh Shilimkar <santosh.shilimkar@ti.com>
> | Date:   Tue Jan 21 15:50:03 2014 -0800
> |
> |    x86: memblock: set current limit to max low memory address
> 
> set limit to low wrongly.
> 
> max_low_pfn_mapped is different from max_pfn_mapped.
> max_low_pfn_mapped is always under 4G.
> 
> That will memblock_alloc_nid all go under 4G.
> 
> Revert that offending patch.
> 
> Reported-by: Dave Hansen <dave.hansen@intel.com>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> 
>
This mostly will fix the $subject issue but the regression 
reported by Andrew [1] will surface with the revert. Its clear
now that even though commit fixed the issue, it wasn't the fix.

Would be great if you can have a look at the thread.

Regards,
Santosh

[1] http://lkml.indiana.edu/hypermail/linux/kernel/1312.1/03770.html

--
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>

  reply	other threads:[~2014-01-24  6:38 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 [this message]
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
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=52E20A56.1000507@ti.com \
    --to=santosh.shilimkar@ti.com \
    --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=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