From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: "David S. Miller" <davem@redhat.com>
Cc: Doug Dumitru <doug@easyco.com>, linux-kernel@vger.kernel.org
Subject: Re: Hard Hang with __alloc_pages: 0-order allocation failed (gfp=0x20/1) - Not out of memory
Date: Wed, 26 May 2004 09:59:21 -0300 [thread overview]
Message-ID: <20040526125921.GJ6439@logos.cnet> (raw)
In-Reply-To: <20040525161212.6478216e.davem@redhat.com>
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?
next prev parent reply other threads:[~2004-05-26 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 22:26 Hard Hang with __alloc_pages: 0-order allocation failed (gfp=0x20/1) - Not out of memory Doug Dumitru
2004-05-25 23:12 ` David S. Miller
2004-05-26 12:59 ` Marcelo Tosatti [this message]
2004-05-26 18:59 ` Doug Dumitru
-- strict thread matches above, loose matches on Subject: below --
2004-05-26 1:22 (Found?) " Roger Larsson
2004-05-26 19:58 ` Roger Larsson
2004-05-25 22:17 Doug Dumitru
2004-05-25 21:20 Feldman, Scott
2004-05-25 21:47 ` David S. Miller
2004-05-25 22:53 ` Marcelo Tosatti
2004-05-25 23:39 ` Marcelo Tosatti
2004-05-25 22:53 ` Marcelo Tosatti
2004-05-24 3:08 Doug Dumitru
2004-05-25 19:02 ` Marcelo Tosatti
2004-05-23 21:54 Doug Dumitru
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040526125921.GJ6439@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=davem@redhat.com \
--cc=doug@easyco.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox