Re: Hard Hang with __alloc_pages: 0-order allocation failed (gfp=0x20/1) - Not out of memory

Marcelo Tosatti
2004-05-26T17:45:40Z

On Tue, May 25, 2004 at 04:12:12PM -0700, David S. Miller wrote:
> On Tue, 25 May 2004 15:26:30 -0700
> Doug Dumitru <doug@easyco.com> wrote:
>
> > This is the original trap dump from a __page_alloc error
> >
> > __alloc_pages: 0-order allocation failed (gfp=0x20/1)
>
> 0x20 means GFP_ATOMIC which means it's fine to fail
> and e1000 is doing nothing wrong. GFP_ATOMIC in interrupts
> is a fine condition.

Yeap, but the crash is not a fine condition... I suspect
what can be happening is extreme gigabit traffic resulting in
memory shortage.

Doug said the load average is really high. Doug, you're not
using NAPI, right? Can you try it?