[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52E2B431.5090705@intel.com>
Date: Fri, 24 Jan 2014 10:42:57 -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:24 AM, Yinghai Lu wrote:
> On Fri, Jan 24, 2014 at 10:19 AM, Dave Hansen <dave.hansen@...el.com> wrote:
>> 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...
This means that, essentially, memblock=debug and
KMEMCHECK/DEBUG_PAGEALLOC can't be used together. That's a shame
because my DEBUG_PAGEALLOC config *broke* this code a few months ago,
right? Oh well.
>> 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.
Can I ask politely for some more caution on your part in this area?
This is two consecutive kernels where this code has broken my system.
--
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