From: Michael Buesch <mbuesch@freenet.de>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: [2.4] 0-order allocation failed
Date: Thu, 7 Oct 2004 13:18:13 +0200 [thread overview]
Message-ID: <200410071318.21091.mbuesch@freenet.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
Hi all,
I'm running 2.4.28 bk snapshot of 2004.09.03
The machine has an uptime of 7 days, 23:46 now.
I was running several bittorrent clients inside of
a screen session. Suddenly they all died (including the
screen session).
dmesg sayed this:
__alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
VM: killing process python
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
__alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
VM: killing process screen
I already got this with kernel 2.4.27 vanilla after a
higher amount of uptime (I think it was over 10 days).
This was exactly the reason I updated to bk snapshot.
What can be the reason for this? Is it OOM? (I can't
really believe it is).
Is it a kernel memory leak?
With 2.4.26 I never got these errors. And I ran uptimes
up to 50 days.
--
Regards Michael Buesch [ http://www.tuxsoft.de.vu ]
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2004-10-07 9:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 11:18 Michael Buesch [this message]
2004-10-07 15:15 ` [2.4] 0-order allocation failed Marcelo Tosatti
2004-10-07 17:17 ` Michael Buesch
2004-10-07 15:39 ` Marcelo Tosatti
2004-10-07 18:28 ` Gabor Z. Papp
2004-10-07 16:42 ` Marcelo Tosatti
2004-10-07 18:43 ` Gabor Z. Papp
2004-10-07 16:53 ` Marcelo Tosatti
2004-10-07 18:53 ` Gabor Z. Papp
2004-10-07 19:36 ` Adam Heath
2004-10-07 19:25 ` Aleksandar Milivojevic
2004-10-07 18:50 ` Neil Horman
2004-10-07 18:54 ` Marc-Christian Petersen
2004-10-08 1:05 ` Marcelo Tosatti
2004-10-08 1:08 ` Marcelo Tosatti
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=200410071318.21091.mbuesch@freenet.de \
--to=mbuesch@freenet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.