khromy wrote:
>
> On Sun, Dec 29, 2002 at 12:42:20PM -0800, Andrew Morton wrote:
> > khromy wrote:
> > >
> > > Running 2.5.53-mm3, I found the following in dmesg. I don't remember
> > > getting anything like this with 2.5.53-mm3.
> > >
> > > xmms: page allocation failure. order:5, mode:0x20
> >
> > gack. Someone is requesting 128k of memory with GFP_ATOMIC. It fell
> > afoul of the reduced memory reserves. It deserved to.
> >
> > Could you please add this patch, and make sure that you have set
> > CONFIG_KALLSYMS=y? This will find the culprit.
>
> XFree86: page allocation failure. order:0, mode:0xd0
> Call Trace:
> [<c012a3dd>] __alloc_pages+0x255/0x264
> [<c012a414>] __get_free_pages+0x28/0x60
> [<c012c7e6>] cache_grow+0xb6/0x20c
> [<c012c9cf>] __cache_alloc_refill+0x93/0x220
> [<c012cb96>] cache_alloc_refill+0x3a/0x58
> [<c012cf1d>] kmem_cache_alloc+0x45/0xc8
> [<c017e36c>] journal_alloc_journal_head+0x10/0x68
> [<c017e458>] journal_add_journal_head+0x80/0x120
oops, sorry. They're all expected. I'd like to know where
the 5-order failure during xmms usage came from. Were you
using a CDROM at the time??
This should tell us, thanks:
--- 25/mm/page_alloc.c~a Sun Dec 29 15:52:29 2002
+++ 25-akpm/mm/page_alloc.c Sun Dec 29 15:52:47 2002
@@ -547,6 +547,8 @@ nopage:
printk("%s: page allocation failure."
" order:%d, mode:0x%x\n",
current->comm, order, gfp_mask);
+ if (order > 3)
+ dump_stack();
}
return NULL;
}
_
-
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/
This archive was generated by hypermail 2b29 : Tue Dec 31 2002 - 22:00:15 EST