ISSUE: vm bug? in 2.4.10

paran213@student.liu.se
Tue, 09 Oct 2001 17:38:14 +0200 (CEST)


Hi
I am having serious problems with the vm in 2.4.10.
Here is my bugrepport:

System configuration:
Debian GNU/Linux 2.2 potato, bunks .deb files for kernel 2.4
gcc version 2.95.2 20000220 (Debian GNU/Linux)
600M swap

Hardware:
AMD K6-2 400MHz (66*6)
AOpen AP5T motherboard
160M SDRAM
580M swap

Tested kernel versions:
2.4.9 ok
2.4.10 crashes
2.4.10-ac4 ok
2.4.10-ac10 ok
I also compiled 2.4.10 with only a minimum of options selected in my
kernel config. No modules, no network, no k6 optimisations (used i386),
nothing that isn't neccessary to start the system. But I still got the
same problem with 2.4.10

Problem desciption (On 2.4.10):
When I run a command that use up all the main memory my console immediately fills upp with
lots of messages like this:

"__alloc_pages: 0-order allocation failed (gpf=0x1d2/0) from c01232ee"
and then
"VM: killing process X"

where X is any process that happens to be running, from bash to syslogd and even init.
This kills all my processes in a couple of seconds.
Then everything but my login is killed. But when I try
to log in (even if I wait a long time) I immediately gets the errors. I
cant reboot by ctrl+alt+del either since VM kills shutdown.. So I have to
manually reboot the machine.

How to replicate the problem:
When I tested the various kernels I made a 200M file with:
"dd if=/dev/zero bs=10k of=/tmp/bigfile count=20k"
And then ran "md5sum /tmp/bigfile"
It works fine on 2.4.10 untill the main memory is full, then the problem
occurs. The command executes fine on all the other tested kernels.

Acctually, this was how I discovered the problem. After having upgraded to
2.4.10 I was going to check the md5sum of a linux-mandrake .iso i
downloaded for my brother. But thats of-topic ;)

Best Regards
Pär Andersson

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/