From: Ben Hutchings <ben@decadent.org.uk>
To: Julien Cristau <jcristau@debian.org>, 599345@bugs.debian.org
Cc: ilw@linux.intel.com, linux-wireless@vger.kernel.org
Subject: Re: Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure
Date: Wed, 06 Oct 2010 22:54:03 +0100 [thread overview]
Message-ID: <1286402043.2955.81.camel@localhost> (raw)
In-Reply-To: <20101006191947.GA3036@radis.liafa.jussieu.fr>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On Wed, 2010-10-06 at 21:19 +0200, Julien Cristau wrote:
> Package: linux-2.6
> Version: 2.6.32-23
> Severity: normal
>
> iwlagn decided 2 weeks of uptime was enough and it wanted me to reboot,
> because it was unhappy after resume.
You also told me that this machine had no swap enabled, which is an
unusual configuration and restricts the ability of the VM to defragment
memory. I would recommend adding a small swap file/partition. However:
> Bit of kern.log:
>
> 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.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next parent reply other threads:[~2010-10-06 21:54 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 ` Ben Hutchings [this message]
2010-10-07 7:51 ` Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure Johannes Berg
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=1286402043.2955.81.camel@localhost \
--to=ben@decadent.org.uk \
--cc=599345@bugs.debian.org \
--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).