Return-Path: <linux-kernel-owner+w=401wt.eu-S1753169AbZL3SFr@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753169AbZL3SFr (ORCPT <rfc822;w@1wt.eu>);
	Wed, 30 Dec 2009 13:05:47 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753094AbZL3SFq
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Wed, 30 Dec 2009 13:05:46 -0500
Received: from mail.vyatta.com ([76.74.103.46]:58194 "EHLO mail.vyatta.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752924AbZL3SFp (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 30 Dec 2009 13:05:45 -0500
Date: Wed, 30 Dec 2009 10:05:19 -0800
From: Stephen Hemminger <shemminger@vyatta.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>, Len Brown <lenb@kernel.org>,
       linux-acpi@vger.kernel.org,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       linux-mm@kvack.org, Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: ACPI warning from alloc_pages_nodemask on boot (2.6.33 
 regression)
Message-ID: <20091230100519.5a72d82c@nehalam>
In-Reply-To: <1262187344.7135.230.camel@laptop>
References: <20091229094202.25818e9b@nehalam>
	<alpine.LFD.2.00.0912291435070.14938@localhost.localdomain>
	<2f11576a0912292221r7ba59e9dw431c7b43b578a04@mail.gmail.com>
	<1262187344.7135.230.camel@laptop>
Organization: Vyatta
X-Mailer: Claws Mail 3.7.2 (GTK+ 2.18.3; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1441
Lines: 39

On Wed, 30 Dec 2009 16:35:44 +0100
Peter Zijlstra <peterz@infradead.org> wrote:

> On Wed, 2009-12-30 at 15:21 +0900, KOSAKI Motohiro wrote:
> > >> [    1.630020] ------------[ cut here ]------------
> > >> [    1.630026] WARNING: at mm/page_alloc.c:1812 __alloc_pages_nodemask+0x617/0x730()
> > >
> > >        if (order >= MAX_ORDER) {
> > >                WARN_ON_ONCE(!(gfp_mask & __GFP_NOWARN));
> > >                return NULL;
> > >        }
> > >
> > > I don't know what the mm alloc code is complaining about here.
> 
> > >> [    1.630028] Hardware name: System Product Name
> > >> [    1.630029] Modules linked in:
> > >> [    1.630032] Pid: 1, comm: swapper Not tainted 2.6.33-rc2 #4
> > >> [    1.630034] Call Trace:
> 
> > >> [    1.630064]  [<ffffffff812cae3e>] acpi_os_allocate+0x25/0x27 
> 
> Right, so ACPI is trying to allocate something larger than 2^MAX_ORDER
> pages, which on x86 computes to 4K * 2^11 = 8M.
> 
> That's not going to work.
> 
> Did this machine properly boot before? I seem to remember people working
> on moving away from bootmem and getting th page/slab stuff up and
> running sooner, it might be fallout from that...
> 

Yes, and it still boots now.

-- 
--
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/