From: "Morten W. Petersen" <morten@nidelven-it.no>
To: linux-kernel@vger.kernel.org
Subject: Fixing page allocation failure
Date: Thu, 18 Nov 2004 12:28:22 +0100 [thread overview]
Message-ID: <419C8756.3080709@nidelven-it.no> (raw)
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
Hi all,
I have a server that a couple of times each day squirts out messages
about page allocation failures (python: page allocation failure.
order:3, mode:0x20). What's the reason for this, and could it affect
the stability of the box?
The server that squirts these messages just crashed, for no apparent
reason, so that's why I'm wondering. It's a UML box. Also, I'm
wondering, are there any howto's for tweaking /proc settings so that the
machine becomes more stable? Are there any settings for increasing the
verbosity of the kernel log so that the reason for a server crashing is
easier to find?
Thanks in advance, and please CC me any replies :)
Regards,
Morten
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next reply other threads:[~2004-11-18 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 11:28 Morten W. Petersen [this message]
2004-11-18 12:10 ` Fixing page allocation failure Nick Piggin
2004-11-19 2:01 ` Andrew Morton
2004-11-20 1:10 ` Morten W. Petersen
2004-11-20 3:57 ` Andrew Morton
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=419C8756.3080709@nidelven-it.no \
--to=morten@nidelven-it.no \
--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