From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>, linux-crypto@nl.linux.org
Subject: 2.4.24 + cryptoloop: __alloc_pages: 5-order allocation failed
Date: Tue, 17 Feb 2004 03:08:05 +0100 [thread overview]
Message-ID: <40317785.3060509@g-house.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
today i played around with some benchmarks i do from time to time [1]
this time with 2.4.24 and the cryptoloop patch
(patch-cryptoloop-jari-2.4.22.0, applies to 2.4.24 too) when using this
machine (powerpc)
http://www.nerdbynature.de/bits/sheep/2.4.24-benh/ver_linux
in short: i have a 700 MB file, losetup a loop device with a cipher
(aes,cast5,cast6,blowfish,serpent,twofish), create an ext3 fs on it.
then test with "tiobench" (size is only about 100MB). but the benchmarks
did not last very long, i have these messages in my syslog:
Dec 21 23:42:45 sheep kernel: __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0)
Dec 21 23:42:45 sheep kernel: VM: killing process nmbd
Dec 21 23:43:07 sheep kernel: __alloc_pages: 0-order allocation failed
(gfp=0x1d2/0)
[...]
Dec 23 22:26:37 sheep kernel: __alloc_pages: 5-order allocation failed
(gfp=0x20/0)
Dec 23 22:26:39 sheep kernel: __alloc_pages: 5-order allocation failed
(gfp=0x20/0)
Dec 23 22:26:40 sheep kernel: __alloc_pages: 5-order allocation failed
(gfp=0x20/0)
Dec 23 22:26:41 sheep kernel: __alloc_pages: 5-order allocation failed
(gfp=0x20/0)
[...]
Feb 16 15:17:21 sheep kernel: __alloc_pages: 0-order allocation failed
(gfp=0x30/0)
full log excerpt on:
http://www.nerdbynature.de/bits/sheep/2.4.24/messages-alloc_pages
i am then able to sysrq-S, but not all partitions can be synced, then i
try sysrq-E / -I / -U with no luck, nothing seems to be written/read
to/from the disk, sysrq-B works :-)
i did manage to make earlier tests with different filesystems [2] and
linux 2.4.22 and have never had these messages.
Thanks for your hints,
Christian.
[1] http://www.nerdbynature.de/bench/
[2] http://www.nerdbynature.de/bench/sheep/
- --
BOFH excuse #62:
need to wrap system in aluminum foil to fix problem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAMXeF+A7rjkF8z0wRAnpNAJ0evZDjZJdMorl60BfYCcogGWsYlwCgnU/B
ZICw1HmIv8Hnrh0D+W29l7A=
=o7Wu
-----END PGP SIGNATURE-----
next reply other threads:[~2004-02-17 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 2:08 Christian Kujau [this message]
2004-02-18 23:42 ` 2.4.24 + cryptoloop: __alloc_pages: 5-order allocation failed Marcelo Tosatti
2004-02-19 7:37 ` Christian Kujau
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 4:04 Christian
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=40317785.3060509@g-house.de \
--to=evil@g-house.de \
--cc=linux-crypto@nl.linux.org \
--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