Re: oom killer in 2.4.23

From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: Kristian Peters <kristian.peters@korseby.net>
Cc: Andrea Arcangeli <andrea@suse.de>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: oom killer in 2.4.23
Date: Fri, 5 Dec 2003 08:56:07 -0500	[thread overview]
Message-ID: <20031205135607.GP16568@rdlg.net> (raw)
In-Reply-To: <20031205140520.39289a3a.kristian.peters@korseby.net>

[-- Attachment #1: Type: text/plain, Size: 2511 bytes --]

Thus spake Kristian Peters (kristian.peters@korseby.net):

> 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)
<snip>
> 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.
> 
> 

I'm see'ing similar except it's killing random apps such as CRON, named
and some others.

How far do I have to roll back to get the previous oomkiller?  Trying to
roll 2.4.23 out.

:wq!
---------------------------------------------------------------------------
Robert L. Harris                     | GPG Key ID: E344DA3B
                                         @ x-hkp://pgp.mit.edu
DISCLAIMER:
      These are MY OPINIONS ALONE.  I speak for no-one else.

Life is not a destination, it's a journey.
  Microsoft produces 15 car pileups on the highway.
    Don't stop traffic to stand and gawk at the tragedy.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]