From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: "David S. Miller" <davem@redhat.com>
Cc: "Feldman, Scott" <scott.feldman@intel.com>,
doug@easyco.com, linux-kernel@vger.kernel.org, cramerj@intel.com,
john.ronciak@intel.com, ganesh.venkatesan@intel.com,
jgarzik@pobox.com
Subject: Re: Hard Hang with __alloc_pages: 0-order allocation failed (gfp=0x20/1) - Not out of memory
Date: Tue, 25 May 2004 20:39:49 -0300 [thread overview]
Message-ID: <20040525233949.GA5451@logos.cnet> (raw)
In-Reply-To: <20040525225308.GA5344@logos.cnet>
On Tue, May 25, 2004 at 07:53:09PM -0300, Marcelo Tosatti wrote:
> On Tue, May 25, 2004 at 02:47:59PM -0700, David S. Miller wrote:
> > On Tue, 25 May 2004 14:20:23 -0700
> > "Feldman, Scott" <scott.feldman@intel.com> wrote:
> >
> > > Marcelo Tosatti wrote:
> > >
> > > > It seems we are calling alloc_skb(GFP_KERNEL) from inside an
> > > > interrupt handler. Oops.
> > >
> > > We're calling dev_alloc_skb() from hard interrupt context, but it uses
> > > GFP_ATOMIC, not GFP_KERNEL, so this is OK, right? I don't see the
> > > problem with e1000.
> >
> > Neither do I, where is the detailed backtrace of this GFP_KERNEL
> > allocation supposedly from interrupt context?
>
> That was just a very wrong guess, I must admit.
>
> Actually what seems to be happening is an e1000 IRQ while
> trying to free memory (shrink_caches()) which tries to
> allocate more memory.
>
> Locked caused by extremely high load it seems.
>
> You know better than me.
Probably NAPI makes a difference?
next prev parent reply other threads:[~2004-05-25 23:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 21:20 Hard Hang with __alloc_pages: 0-order allocation failed (gfp=0x20/1) - Not out of memory Feldman, Scott
2004-05-25 21:47 ` David S. Miller
2004-05-25 22:53 ` Marcelo Tosatti
2004-05-25 23:39 ` Marcelo Tosatti [this message]
2004-05-25 22:53 ` Marcelo Tosatti
-- 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:26 Doug Dumitru
2004-05-25 23:12 ` David S. Miller
2004-05-26 12:59 ` Marcelo Tosatti
2004-05-26 18:59 ` Doug Dumitru
2004-05-25 22:17 Doug Dumitru
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=20040525233949.GA5451@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=cramerj@intel.com \
--cc=davem@redhat.com \
--cc=doug@easyco.com \
--cc=ganesh.venkatesan@intel.com \
--cc=jgarzik@pobox.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott.feldman@intel.com \
/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