From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Julien Cristau <jcristau@debian.org>,
599345@bugs.debian.org, ilw@linux.intel.com,
linux-wireless@vger.kernel.org
Subject: Re: Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure
Date: Thu, 07 Oct 2010 09:51:10 +0200 [thread overview]
Message-ID: <1286437870.3657.16.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1286402043.2955.81.camel@localhost>
On Wed, 2010-10-06 at 22:54 +0100, Ben Hutchings wrote:
> On Wed, 2010-10-06 at 21:19 +0200, Julien Cristau wrote:
> > Package: linux-2.6
> > Version: 2.6.32-23
> > Oct 6 21:05:02 radis kernel: [378665.326381] NetworkManager: page allocation failure. order:4, mode:0x40d0
> > Oct 6 21:05:02 radis kernel: [378665.326393] Pid: 25555, comm: NetworkManager Not tainted 2.6.32-5-amd64 #1
> [...]
> > Oct 6 21:05:02 radis kernel: [378665.363630] iwlagn 0000:0c:00.0: kmalloc for auxiliary BD structures failed
> [...]
>
> This particular allocation is for an array which is not used for DMA and
> therefore could be stored in non-contiguous pages allocated with
> vmalloc(). But there may be some good reason not to do this.
I have, however much more recently than that kernel, cleaned this up in
commit ff0d91c3eea6e25b47258349b455671f98f1b0cd -- this particular
allocation is now 2048 or 4096 bytes depending on the architecture (32
vs 64 bit pointers). If you want to backport this, there are two or
three more commits right before it that would probably be required.
johannes
next prev parent reply other threads:[~2010-10-07 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101006191947.GA3036@radis.liafa.jussieu.fr>
2010-10-06 21:54 ` Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure Ben Hutchings
2010-10-07 7:51 ` Johannes Berg [this message]
2010-10-10 19:03 ` Ben Hutchings
2010-10-10 19:37 ` Johannes Berg
2010-10-13 15:17 ` Julien Cristau
2010-10-13 15:30 ` Johannes Berg
2010-12-22 4:11 ` Ben Hutchings
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=1286437870.3657.16.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=599345@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=ilw@linux.intel.com \
--cc=jcristau@debian.org \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).