Skip to contentSkip to conversation

2.4.24 + cryptoloop: __alloc_pages: 5-order allocation failed

DISCUSSION Christian 1 participant 1 message Feb 25, 2004

lore
Share & tools
lore

Christian

author
#0 lore raw

[sorry, took me a while]

Quoted 5 lines

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.

Signature · 3 lines
BOFH excuse #141:

disks spinning backwards - toggle the hemisphere jumper.