From: Mike Gabriel <mgabriel@ecology.uni-kiel.de>
To: linux-kernel@vger.kernel.org
Subject: page allocation failed in 2.4.24
Date: Sun, 1 Feb 2004 00:18:23 +0100 [thread overview]
Message-ID: <200402010018.23725.mgabriel@ecology.uni-kiel.de> (raw)
hi there,
can anyone tell me what these messages mean? running linux-2.4.24 on asus
p4p800 deluxe.
Jan 31 02:38:02 galileo kernel: __alloc_pages: 0-order allocation failed
(gfp=0xf0/0)
Jan 31 02:38:02 galileo kernel: __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0)
Jan 31 02:38:02 galileo kernel: VM: killing process slapd
Jan 31 02:38:50 galileo kernel: __alloc_pages: 0-order allocation failed
(gfp=0xf0/0)
Jan 31 02:38:50 galileo kernel: ENOMEM in journal_get_undo_access_R9add2900,
retrying.
Jan 31 02:38:53 galileo kernel: __alloc_pages: 0-order allocation failed
(gfp=0xf0/0)
Jan 31 02:39:19 galileo last message repeated 3 times
Jan 31 02:39:25 galileo kernel: __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0)
Jan 31 02:39:25 galileo kernel: VM: killing process sshd
Jan 31 02:39:25 galileo kernel: __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0)
Jan 31 02:39:25 galileo kernel: VM: killing process sshd
I get plenty of them during copying (cp -av <source> <dest>) a huge amount of
data, which is densely filled with hard links from one raid to another... the
cp command runs in a screen session. on huge directories, it starts blasting
other processes from the system (sshd, nmbd, spong-client, etc.)
any ideas?
mike
--
Oekologiezentrum
Christian-Albrecht-Universität zu Kiel
- netzwerkteam -
Mike Gabriel
Olshausenstr 75.
24118 Kiel
fon: +49 431 880-1186
mail: mgabriel@ecology.uni-kiel.de
www: http://www.ecology.uni-kiel.de, http://zope.ecology.uni-kiel.de
next reply other threads:[~2004-01-31 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-31 23:18 Mike Gabriel [this message]
2004-02-02 0:13 ` Marcelo Tosatti
2004-02-02 9:47 ` Mike Gabriel
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=200402010018.23725.mgabriel@ecology.uni-kiel.de \
--to=mgabriel@ecology.uni-kiel.de \
--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
all inboxes | Powered by JetHome®