[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52E2AEA3.2020907@intel.com>
Date: Fri, 24 Jan 2014 10:19:15 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Yinghai Lu <yinghai@...nel.org>
CC: "H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>,
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 01/24/2014 10:13 AM, Yinghai Lu wrote:
> On Fri, Jan 24, 2014 at 10:09 AM, Dave Hansen <dave.hansen@...el.com> wrote:
>> On 01/24/2014 09:45 AM, Yinghai Lu wrote:
>> 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?
>
> that looks like different problem. and it can not set memory mapping properly.
>
> can you send me .config ?
Here you go.
FWIW, I did turn of memblock=debug. It eventually booted, but
slooooooooooowly.
How many problems in this code are we tracking, btw? This is at least
3, right?
View attachment "config-3.13.0-05617-g3aacd62-dirty.txt" of type "text/plain" (76962 bytes)
Powered by blists - more mailing lists