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

[David S. Miller]

On Tue, 25 May 2004 15:26:30 -0700
Doug Dumitru <doug@xxxxxxxxxx> 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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/