From: Paulo Marques <pmarques@grupopie.com>
To: "Abu M. Muttalib" <abum@aftek.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Page Allocation Failure, Why?? Bug in kernel??
Date: Thu, 01 Jun 2006 14:25:48 +0100 [thread overview]
Message-ID: <447EEADC.4050306@grupopie.com> (raw)
In-Reply-To: <BKEKJNIHLJDCFGDBOHGMAEHNCNAA.abum@aftek.com>
Abu M. Muttalib wrote:
> Hi,
Hi,
> I tried to run an application, try-sound.c. In the course of the run of the
> application I repeatedly got page allocation failure, despite the fact that
> enough pages are free. Why this is so, is it a bug in mm subsystem of Linux
> kernel 2.6.13?
>
> Any pointer to help understand this behavior will be highly appreciated.
If you're expecting kernel developers to unpack your text file and read
through 40555(!!!) lines of text to find out what's wrong...
Please try to explain your problem better with some before / after
comparisons that fit nicely into an email and point out specifically
where you think it went wrong. Also describe what you're trying to do
and what kind of hardware you're using.
For more detailed information on how to report kernel bugs, please read
the file REPORTING-BUGS in the main kernel source directory.
Please don't see this as a "we don't care" message. If the kernel has
indeed a bug we very much do care! We just can't go through thousands of
lines of text to try to understand what the problem is... :(
--
Paulo Marques - www.grupopie.com
Pointy-Haired Boss: I don't see anything that could stand in our way.
Dilbert: Sanity? Reality? The laws of physics?
next prev parent reply other threads:[~2006-06-01 13:25 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 [this message]
2006-06-01 13:51 ` Abu M. Muttalib
2006-06-01 14:59 ` Martin J. Bligh
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=447EEADC.4050306@grupopie.com \
--to=pmarques@grupopie.com \
--cc=abum@aftek.com \
--cc=linux-kernel@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