[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQX9kTxnaqpWNgg3dUzr7+60YCrEx3q3xxO-G1n6z64xVQ@mail.gmail.com>
Date: Thu, 23 Jan 2014 21:55:13 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: Dave Hansen <dave.hansen@...el.com>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>
Cc: Grygorii Strashko <grygorii.strashko@...com>,
Linux-MM <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
Santosh Shilimkar <santosh.shilimkar@...com>,
Tejun Heo <tj@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Panic on 8-node system in memblock_virt_alloc_try_nid()
On Thu, Jan 23, 2014 at 2:49 PM, Dave Hansen <dave.hansen@...el.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.
Yinghai
View attachment "fix_numa_x.patch" of type "text/x-patch" (1868 bytes)
Powered by blists - more mailing lists