[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQU795SWFfnQU=0STbQconSraac8heCNnkMpynY6fbi-4w@mail.gmail.com>
Date: Fri, 24 Jan 2014 10:24:26 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: Dave Hansen <dave.hansen@...el.com>
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 Fri, Jan 24, 2014 at 10:19 AM, Dave Hansen <dave.hansen@...el.com> wrote:
> 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.
then that is not a problem, as you are using 4k page mapping only.
and that printout is too spew...
>
> How many problems in this code are we tracking, btw? This is at least
> 3, right?
two problems:
1. big numa system.
2. Andrew's system with swiotlb.
The two patches should address them.
Thanks
Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists