xfs
[Top] [All Lists]

Re: [?] __alloc_pages: 1-order allocation failed.

To: Krzysztof Rusocki <kszysiu@xxxxxxxxxxxx>
Subject: Re: [?] __alloc_pages: 1-order allocation failed.
From: Andi Kleen <ak@xxxxxxx>
Date: Tue, 13 Feb 2001 14:56:10 +0100
Cc: linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx
In-reply-to: <20010213105957.A16713@main.braxis.co.uk>; from kszysiu@braxis.co.uk on Tue, Feb 13, 2001 at 10:59:57AM +0100
References: <20010213105957.A16713@main.braxis.co.uk>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Tue, Feb 13, 2001 at 10:59:57AM +0100, Krzysztof Rusocki wrote:
> 
> Hi,
> 
> Here's what i've found today in logs:
> 
> Feb 13 02:10:41 main kernel: __alloc_pages: 1-order allocation failed. 
> Feb 13 02:10:42 main last message repeated 143 times
> Feb 13 02:10:47 main kernel: ed. 
> Feb 13 02:10:47 main kernel: __alloc_pages: 1-order allocation failed. 
> Feb 13 02:50:30 main syslogd 1.3-3: restart (remote reception).
> 
> 
> After that there was possibly lock-up or reboot (i don't know, when i 
> connected to  the machine it was already running).
> 
> What can be possible cause of such things ?

When you add the following patch you should see the addresses of functions
that cause allocation failures. Look the hex value up in the System.map
then. For this XFS should be compiled in, not be a module.
Is it always the same address?




-Andi

Index: mm/page_alloc.c
===================================================================
RCS file: /cvs/linux-2.4-xfs/linux/mm/page_alloc.c,v
retrieving revision 1.32
diff -u -r1.32 page_alloc.c
--- mm/page_alloc.c     2000/12/17 19:15:00     1.32
+++ mm/page_alloc.c     2001/02/13 13:54:33
@@ -529,7 +529,8 @@
        }
 
        /* No luck.. */
-       printk(KERN_ERR "__alloc_pages: %lu-order allocation failed.\n", order);
+       printk(KERN_ERR "__alloc_pages: %lu-order allocation failed from %p\n", 
+               order, __builtin_return_address(0));
        return NULL;
 }
 

<Prev in Thread] Current Thread [Next in Thread>