Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752316AbaAXSKB (ORCPT ); Fri, 24 Jan 2014 13:10:01 -0500 Received: from mga02.intel.com ([134.134.136.20]:62824 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752067AbaAXSKA (ORCPT ); Fri, 24 Jan 2014 13:10:00 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.95,714,1384329600"; d="scan'208";a="471986215" Message-ID: <52E2AC5A.3000005@intel.com> Date: Fri, 24 Jan 2014 10:09:30 -0800 From: Dave Hansen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Yinghai Lu CC: "H. Peter Anvin" , Ingo Molnar , Grygorii Strashko , Linux-MM , LKML , Santosh Shilimkar , Tejun Heo , Andrew Morton Subject: Re: Panic on 8-node system in memblock_virt_alloc_try_nid() References: <52E19C7D.7050603@intel.com> <52E28067.1060507@intel.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/24/2014 09:45 AM, Yinghai Lu wrote: > On Fri, Jan 24, 2014 at 7: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. >> >>> [ 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? Here you go. It's still spitting out memblock_reserve messages to the console. I'm not sure if it's making _some_ progress or not. https://www.sr71.net/~dave/intel/3.13/dmesg.with-2-patches But, it's certainly not booting. Do you want to see it without memblock=debug? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/