public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juan <piernas@ditec.um.es>
To: kernel list <linux-kernel@vger.kernel.org>
Subject: Bad, bad, bad VM behaviour in 2.4.10
Date: Tue, 25 Sep 2001 23:17:55 +0200	[thread overview]
Message-ID: <3BB0F483.69929A79@ditec.um.es> (raw)

Hi!

My test is very simple. I have started X-Window and XMMS in order to
listen to some songs. Then, I have executed

	dd if=/dev/hdc1 of=/dev/null

as root within a terminal, and I have got the following a few seconds
later:

Sep 25 22:05:55 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:00 localhost last message repeated 2 times
Sep 25 22:06:00 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0xf0/0) from c012ff60
Sep 25 22:06:00 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:00 localhost last message repeated 2 times
Sep 25 22:06:00 localhost kernel: VM: killing process xmms
Sep 25 22:06:00 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:04 localhost last message repeated 11 times
Sep 25 22:06:04 localhost kernel: VM: killing process xmms
Sep 25 22:06:04 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:04 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:04 localhost kernel: VM: killing process kmix
Sep 25 22:06:04 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:04 localhost last message repeated 2 times
Sep 25 22:06:04 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0xf0/0) from c012ff60
Sep 25 22:06:04 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:04 localhost last message repeated 3 times
Sep 25 22:06:04 localhost kernel: VM: killing process gpm
Sep 25 22:06:05 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:06 localhost last message repeated 6 times
sep 25 22:06:06 localhost su(pam_unix)[2548]: session closed for user
root
Sep 25 22:06:06 localhost kernel: VM: killing process sendmail
Sep 25 22:06:07 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:07 localhost kernel: VM: killing process konsole
Sep 25 22:06:07 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:07 localhost kernel: VM: killing process named
Sep 25 22:06:07 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:07 localhost kernel: VM: killing process xmms
Sep 25 22:06:07 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:07 localhost last message repeated 3 times
Sep 25 22:06:07 localhost kernel: VM: killing process ksmserver
Sep 25 22:06:07 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:07 localhost kernel: VM: killing process kdeinit
Sep 25 22:06:08 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:08 localhost kernel: VM: killing process X
Sep 25 22:06:08 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0xf0/0) from c012ff60
Sep 25 22:06:08 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
f60
Sep 25 22:06:08 localhost last message repeated 2 times
Sep 25 22:06:08 localhost kernel: VM: killing process kdeinit
Sep 25 22:06:08 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:08 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:08 localhost kernel: VM: killing process startkde
Sep 25 22:06:09 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:09 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60
Sep 25 22:06:09 localhost kernel: VM: killing process named
Sep 25 22:06:09 localhost kernel: __alloc_pages: 0-order allocation
failed (gfp=0x1d2/0) from c012ff60

The /dev/hdc1 partition capacity is 6 GB. My root partition is on
/dev/hda5. My computer is a Pentium III with 384 MB of RAM.

BTW, the same test in 2.4.6 works fine without any problem.

Regards.


-- 
D. Juan Piernas Cánovas
Departamento de Ingeniería y Tecnología de Computadores
Facultad de Informática. Universidad de Murcia
Campus de Espinardo - 30080 Murcia (SPAIN)
Tel.: +34968367657    Fax: +34968364151
email: piernas@ditec.um.es
PGP public key:
http://pgp.rediris.es:11371/pks/lookup?search=piernas%40ditec.um.es&op=index

             reply	other threads:[~2001-09-25 21:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-25 21:17 Juan [this message]
2001-09-25 20:03 ` Bad, bad, bad VM behaviour in 2.4.10 Marcelo Tosatti
2001-09-25 21:52   ` khromy
2001-09-25 22:08   ` Juan
2001-09-25 21:23     ` Marcelo Tosatti
2001-09-26 10:36       ` Juan
2001-09-26  8:05   ` Jacek Popławski
2001-09-26 15:23 ` Dan Mann

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=3BB0F483.69929A79@ditec.um.es \
    --to=piernas@ditec.um.es \
    --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