All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>,
	marcelo.tosatti@cyclades.com
Subject: Re: 2.4.24 + cryptoloop: __alloc_pages: 5-order allocation failed
Date: Wed, 25 Feb 2004 05:04:19 +0100	[thread overview]
Message-ID: <403C1EC3.5070808@g-house.de> (raw)

[sorry, took me a while]
 > Christian, Daniel,
 >
 > Please do
 >
 > echo 1 > /proc/sys/vm/vm_gfp_debug

i did so, but it revealed not much (any?) more information:

Feb 25 03:05:17 sheep kernel: __alloc_pages: 0-order allocation failed 
(gfp=0x30/0)
Feb 25 03:05:17 sheep kernel: This architecture does not implement 
dump_stack()
Feb 25 03:05:27 sheep kernel: __alloc_pages: 0-order allocation failed 
(gfp=0x30/0)
Feb 25 03:05:27 sheep kernel: This architecture does not implement 
dump_stack()
Feb 25 03:05:27 sheep kernel: __alloc_pages: 0-order allocation failed 
(gfp=0x30/0)
Feb 25 03:05:27 sheep kernel: This architecture does not implement 
dump_stack()
Feb 25 03:05:27 sheep kernel: __alloc_pages: 0-order allocation failed 
(gfp=0x30/0)
Feb 25 03:05:27 sheep kernel: This architecture does not implement 
dump_stack()
Feb 25 03:06:17 sheep syslog-ng[324]: STATS: dropped 94
Feb 25 03:07:42 sheep kernel: __alloc_pages: 0-order allocation failed 
(gfp=0x30/0)
Feb 25 03:07:42 sheep kernel: This architecture does not implement 
dump_stack()
Feb 25 03:07:52 sheep kernel: __alloc_pages: 0-order allocation failed 
(gfp=0x30/0)
Feb 25 03:07:52 sheep kernel: This architecture does not implement 
dump_stack()
Feb 25 03:07:52 sheep kernel: __alloc_pages: 0-order allocation failed 
(gfp=0x30/0)
Feb 25 03:07:52 sheep kernel: This architecture does not implement 
dump_stack()
Feb 25 03:07:52 sheep kernel: __alloc_pages: 0-order allocation failed 
(gfp=0x30/0)
Feb 25 03:07:52 sheep kernel: This architecture does not implement 
dump_stack()

for the record:

root@sheep:~# cat /proc/sys/vm/vm_gfp_debug
1
root@sheep:~#

some thoughts of mine:
after setting vm_gfp_debug to 1 i run the benchmarks again, with a 200MB 
  testfile (within a 700MB fs, setup via cryptoloop). in the log the 
messages from above showed up, but this time the benchmark was able to 
finish, the system was *never unusable* during the test (like i was 
experienceing with former kernels too). but: i don't know if i had 
another memory consuming app running last time. even if i did, i did not 
get any OOM messages, but i could think of higher memory- / vm-pressure 
last time....

oh, and just in case i forgot last time, this is the machine:
http://nerdbynature.de/bits/sheep/2.4.24-benh/ver_linux

(maybe this is why syslog says: "
Feb 25 03:07:52 sheep kernel: This architecture does not implement 
dump_stack()"?)

Thank you,
Christian.
-- 
BOFH excuse #141:

disks spinning backwards - toggle the hemisphere jumper.


             reply	other threads:[~2004-02-25  4:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25  4:04 Christian [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-17  2:08 2.4.24 + cryptoloop: __alloc_pages: 5-order allocation failed Christian Kujau
2004-02-18 23:42 ` Marcelo Tosatti
2004-02-19  7:37   ` Christian Kujau

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=403C1EC3.5070808@g-house.de \
    --to=evil@g-house.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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.