From: "Martin J. Bligh" <mbligh@mbligh.org>
To: "Abu M. Muttalib" <abum@aftek.com>
Cc: Paulo Marques <pmarques@grupopie.com>, linux-kernel@vger.kernel.org
Subject: Re: Page Allocation Failure, Why?? Bug in kernel??
Date: Thu, 01 Jun 2006 07:59:19 -0700 [thread overview]
Message-ID: <447F00C7.4060904@mbligh.org> (raw)
In-Reply-To: <BKEKJNIHLJDCFGDBOHGMGEIHCNAA.abum@aftek.com>
Abu M. Muttalib wrote:
> Hi,
>
> I am sorry to cause inconvenience. To put the doubts concisely, I am doing
> the following:
>
> I am removing the sound driver (shipped with kernel 2.6.13) and then
> inserting the same. This all I am doing inside an infinite loop. Before this
> I have reserved and used (setting the same with memset) some 900 pages to
> simulate an application environment. I am running this application on Linux
> 2.6.13 on an ARM based target. During the course of the run I get the
> following page allocation error:
> ----------------------------------------------------------------------------
> ---------------------------------------------------------------insmod: page
> allocation failure. order:5, mode:0xd0
Order 5 allocations will never work reliably, except possibly at boot.
We don't have 32 contig pages to give you - fragmentation.
M.
next prev parent reply other threads:[~2006-06-01 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 9:26 Page Allocation Failure, Why?? Bug in kernel?? Abu M. Muttalib
2006-06-01 13:25 ` Paulo Marques
2006-06-01 13:51 ` Abu M. Muttalib
2006-06-01 14:59 ` Martin J. Bligh [this message]
2006-06-02 6:26 ` Abu M. Muttalib
2006-06-02 7:05 ` Jesper Juhl
2006-06-02 7:21 ` Abu M. Muttalib
2006-06-02 7:39 ` Dave Airlie
2006-06-02 7:43 ` Nick Piggin
2006-06-02 7:53 ` Jesper Juhl
2006-06-02 8:41 ` Abu M. Muttalib
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=447F00C7.4060904@mbligh.org \
--to=mbligh@mbligh.org \
--cc=abum@aftek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.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