From: Jens Axboe <axboe@suse.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: "John O'Donnell" <johnod@voicefx.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.0: __alloc_pages: 3-order allocation failed.
Date: Mon, 8 Jan 2001 05:06:12 +0100 [thread overview]
Message-ID: <20010108050612.A2519@suse.de> (raw)
In-Reply-To: <3A58E69D.30005@voicefx.com> <Pine.LNX.4.21.0101072006450.21675-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0101072006450.21675-100000@duckman.distro.conectiva>; from riel@conectiva.com.br on Sun, Jan 07, 2001 at 08:07:52PM -0200
On Sun, Jan 07 2001, Rik van Riel wrote:
> > __alloc_pages: 3-order allocation failed.
>
> This debugging check should probably be removed around
> 2.4.5, in the mean time it is much too useful to track
> down badly behaving device drivers ;)
It need not be a badly written driver, it could be a fine one
just trying to see if it can get 2^3 successive pages for
performance reasons. As long as it continues on its merry way when
this fails it would be fine, and this message just confuses users.
Plus, for this to be really useful as a catch-bad-guys tool it
would be nice with a hint as what causes it (EIP or even a
call trace).
--
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-08 4:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-07 21:58 2.4.0: __alloc_pages: 3-order allocation failed John O'Donnell
2001-01-07 22:07 ` Rik van Riel
2001-01-08 4:06 ` Jens Axboe [this message]
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=20010108050612.A2519@suse.de \
--to=axboe@suse.de \
--cc=johnod@voicefx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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