From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx105.postini.com [74.125.245.105]) by kanga.kvack.org (Postfix) with SMTP id A09C06B004F for ; Tue, 6 Dec 2011 02:55:10 -0500 (EST) Date: Tue, 6 Dec 2011 08:55:31 +0100 From: Stanislaw Gruszka Subject: Re: [PATCH repost] mm,x86: remove debug_pagealloc_enabled Message-ID: <20111206075530.GA3105@redhat.com> References: <1322582711-14571-1-git-send-email-sgruszka@redhat.com> <20111205110656.GA22259@elte.hu> <20111205150019.GA5434@redhat.com> <20111205155434.GD30287@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111205155434.GD30287@elte.hu> Sender: owner-linux-mm@kvack.org List-ID: To: Ingo Molnar Cc: linux-mm@kvack.org, x86@kernel.org, linux-kernel@vger.kernel.org, Mel Gorman , Andrew Morton , Ingo Molnar , "H. Peter Anvin" , Thomas Gleixner On Mon, Dec 05, 2011 at 04:54:34PM +0100, Ingo Molnar wrote: > > * Stanislaw Gruszka wrote: > > > On Mon, Dec 05, 2011 at 12:06:56PM +0100, Ingo Molnar wrote: > > > > > > * Stanislaw Gruszka wrote: > > > > > > > When (no)bootmem finish operation, it pass pages to buddy allocator. > > > > Since debug_pagealloc_enabled is not set, we will do not protect pages, > > > > what is not what we want with CONFIG_DEBUG_PAGEALLOC=y. > > > > > > > > To fix remove debug_pagealloc_enabled. That variable was introduced by > > > > commit 12d6f21e "x86: do not PSE on CONFIG_DEBUG_PAGEALLOC=y" to get > > > > more CPA (change page attribude) code testing. But currently we have > > > > CONFIG_CPA_DEBUG, which test CPA. > > > > > > > > Signed-off-by: Stanislaw Gruszka > > > > Acked-by: Mel Gorman > > > > --- > > > > arch/x86/mm/pageattr.c | 6 ------ > > > > include/linux/mm.h | 10 ---------- > > > > init/main.c | 5 ----- > > > > mm/debug-pagealloc.c | 3 --- > > > > 4 files changed, 0 insertions(+), 24 deletions(-) > > > > > > I'm getting this boot crash with the patch applied: > > > > I'm sorry for breaking the boot. I tried to reproduce problem > > on my laptop, but failed. I plan to test patch with your > > config on some other machines. > > > > On the meantime can you test attached incremental patch and > > see if it workaround the crash? I suspect memblock reuse pages > > that it passed already to buddy allocator. > > That will take some time - so if you could try my config on > another box that would be great. There isnt anything special > about that box. I reproduced with limiting memory via mem=1G and increase find_range_array count argument, what caused "struct range" array was bigger and needed more memory. With that I can confirm that previous patch fixes the problem. I think it's the simplest possible fix, I'll post patch with changelog and comment in the next email. Stanislaw -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org