linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kristian Peters <kristian.peters@korseby.net>
To: Andrea Arcangeli <andrea@suse.de>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: oom killer in 2.4.23
Date: Fri, 5 Dec 2003 14:05:20 +0100	[thread overview]
Message-ID: <20031205140520.39289a3a.kristian.peters@korseby.net> (raw)
In-Reply-To: <Zbyn-23P-29@gated-at.bofh.it>

Andrea Arcangeli <andrea@suse.de> schrieb:
> Marcelo asked me to to make it configurable at runtime so you could go
> in the deadlock prone stautus of 2.4.22 on demand, but I'm not going to
> add more features to 2.4 today unless they're blocker bugs (even if that
> would be simple to implement), actually it's not even my choice so don't
> ask me for that sorry.

Andrea, your vm does not work correctly in any cases.

It's so simple. I've tried to fill up my memory with that crappy khexedit that comes with kde2. You'll see how my memory fills with the contents of the whole file I load. When I have started 2 or 3 instances of khexedit my memory was nearly completely filled. Than I tried to start another khexedit (with a file that should nearly fit into memory), and the pain began.

See:

Dec  5 13:33:52 adlib kernel: __alloc_pages: 2-order allocation failed (gfp=0x1f0/0)
Dec  5 13:33:52 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Dec  5 13:33:59 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0)
Dec  5 13:33:59 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Dec  5 13:34:00 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Dec  5 13:34:01 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Dec  5 13:34:02 adlib last message repeated 3 times

-------> kernel killed wmfire without saying

Dec  5 13:34:02 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0)
Dec  5 13:34:03 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0)
Dec  5 13:34:18 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Dec  5 13:34:18 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Dec  5 13:34:22 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0)
Dec  5 13:34:22 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Dec  5 13:34:28 adlib last message repeated 3 times

-------> kernel killed xosview without mentioning

Dec  5 13:34:29 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0)
Dec  5 13:34:29 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Dec  5 13:34:32 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0)
Dec  5 13:34:41 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Dec  5 13:34:41 adlib kernel: VM: killing process khexedit

-------> that was intended



Ok. That still is acceptable but when I tried to start mozilla, it got even worse:

Dec  5 13:37:26 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Dec  5 13:37:27 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Dec  5 13:37:27 adlib kernel: VM: killing process mozilla-bin
Dec  5 13:37:27 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0)
Dec  5 13:37:27 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Dec  5 13:37:28 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Dec  5 13:37:30 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0)
Dec  5 13:37:30 adlib last message repeated 2 times
Dec  5 13:37:30 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Dec  5 13:37:40 adlib last message repeated 3 times
Dec  5 13:37:56 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Dec  5 13:37:56 adlib kernel: VM: killing process mozilla-bin

-------> that was intended too
-------> but not the killing of another xosview and aterm

Dec  5 13:37:57 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Dec  5 13:37:57 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0)
Dec  5 13:37:58 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0)
Dec  5 13:40:32 adlib kernel: __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
Dec  5 13:40:32 adlib kernel: VM: killing process XFree86

-------> ouch ...


Ok. Could you please describe what your vm really does here in my specific case ?
Rick's old vm worked better. It'd have killed the task that had last allocated memory.

PS: If you need more details it should be no problem to do this again.

*Kristian


   _o)
   /\\
  _\_V


       reply	other threads:[~2003-12-05 13:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Z6Iv-7O2-29@gated-at.bofh.it>
     [not found] ` <Z8Ag-3BK-3@gated-at.bofh.it>
     [not found]   ` <Zbyn-23P-29@gated-at.bofh.it>
2003-12-05 13:05     ` Kristian Peters [this message]
2003-12-05 13:56       ` oom killer in 2.4.23 Robert L. Harris
2003-12-05 19:58       ` Andrea Arcangeli
2003-12-06  9:31         ` Kristian Peters
2003-12-09 14:21           ` Andrea Arcangeli
2003-12-09 14:52             ` Richard B. Johnson
2003-12-09 17:06               ` Andrea Arcangeli
2003-12-09 18:50                 ` Kristian Peters
2003-12-05 22:38       ` Mike Fedyk
2003-12-05 22:56         ` Andrea Arcangeli
2003-12-04 16:12 Peter Bergmann
2003-12-04 17:02 ` Maciej Zenczykowski
2003-12-04 17:20   ` Guillermo Menguez Alvarez
2003-12-04 23:52     ` Andrea Arcangeli
2003-12-04 18:33   ` Peter Bergmann
2003-12-04 18:42     ` Jens Axboe
2003-12-04 20:38       ` Peter Bergmann
2003-12-04 20:28         ` Szakacsits Szabolcs
2003-12-04 23:58         ` Andrea Arcangeli

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=20031205140520.39289a3a.kristian.peters@korseby.net \
    --to=kristian.peters@korseby.net \
    --cc=andrea@suse.de \
    --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;
as well as URLs for NNTP newsgroup(s).