From: Pekka Pietikainen <pp@ee.oulu.fi>
To: "Mihai Donțu" <mihai.dontu@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: b44 - swapper: page allocation failure
Date: Thu, 15 Jan 2009 15:40:55 +0200 [thread overview]
Message-ID: <20090115134055.GA15551@ee.oulu.fi> (raw)
In-Reply-To: <200901151527.43646.mihai.dontu@gmail.com>
On Thu, Jan 15, 2009 at 03:27:43PM +0200, Mihai Donțu wrote:
> > > A friend of mine just booted 2.6.28 and when someone else tried to send
> > > something to him over ssh (scp), the transfer failed and the following
> > > appeared in dmesg:
> > You missed the all important order line before the stack trace.
> Right, sorry for that. Here it is:
> swapper: page allocation failure. order:0, mode:0x21
> > If it's order 0, then you're just out of memory, if it's greater
> > than order 0, then either you're using jumbo frames or b44 is
> > broken.
> It is order zero, but he's not out of memory. He has just booted 2.6.28 (no X,
> no thing), has 3GB of RAM and 2GB of swap.
b44 uses GFP_DMA bounce buffers in some situations (x86_64 with > 1GB of
memory would do the trick I think, as does x86 with 4:4 memory split),
and that's a very limited resource (Memory < 16MB ).
Lovely hardware feature requiring nasty workarounds
(the chip can't do DMA for addresses > 1GB).
Maybe something else sucks up GFP_DMA memory with 2.6.28?
next prev parent reply other threads:[~2009-01-15 14:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 18:34 b44 - swapper: page allocation failure Mihai Donțu
2009-01-15 11:15 ` Herbert Xu
2009-01-15 13:27 ` Mihai Donțu
2009-01-15 13:40 ` Pekka Pietikainen [this message]
2009-01-15 14:40 ` Eric Dumazet
2009-01-15 16:49 ` [PATCH] b44: GFP_DMA skb should not escape from driver Eric Dumazet
2009-01-15 17:14 ` Ionut Leonte
2009-01-15 17:28 ` Eric Dumazet
2009-01-15 23:29 ` David Miller
2009-01-15 14:05 ` b44 - swapper: page allocation failure Ionut Leonte
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=20090115134055.GA15551@ee.oulu.fi \
--to=pp@ee.oulu.fi \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mihai.dontu@gmail.com \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.