All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Chris Ross <chris@tebibyte.org>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: slow OOM killing with 2.6.9?
Date: Thu, 16 Dec 2004 10:36:56 -0600	[thread overview]
Message-ID: <41C1B9A8.2020003@nortelnetworks.com> (raw)
In-Reply-To: <41C1777A.3080105@tebibyte.org>

Chris Ross wrote:
> 
> Chris Friesen escreveu:
> 
>> I've got a ppc box with 2GB of ram, running 2.6.9.
>>
>> If I run a few instances of memory chewing programs, eventually the 
>> OOM-killer kicks in.  At that point, the machine locks up for about 10 
>> seconds while deciding what to kill.
> 
> 
> OOM killing is known to be broken in 2.6.9, specifically it kills things 
> even when the machine isn't out of memeory and/or kills the "wrong" 
> things when it is. See threads assim for more details.
> 
> The OOM Killer is working properly again in 2.6.10-rc2-mm4. Could you 
> try that kernel and report whether it fixed your problems too?

Hmm...downloaded 2.6.9, patched to 2.6.10-rc2, patched to 2.6.10-rc2-mm4.  Tried 
building and got the following error:

[cfriesen@hsdbsk204-83-218-112 linux-2.6.10-rc2-mm4]$ make
   CHK     include/linux/version.h
make[1]: `arch/ppc/kernel/asm-offsets.s' is up to date.
   CHK     include/linux/compile.h
   CHK     usr/initramfs_list
   GEN     .version
   CHK     include/linux/compile.h
   UPD     include/linux/compile.h
   CC      init/version.o
   LD      init/built-in.o
   LD      .tmp_vmlinux1
arch/ppc/mm/built-in.o(.init.text+0x5f4): In function `paging_init':
: undefined reference to `pgd_offset_is_obsolete'
make: *** [.tmp_vmlinux1] Error 1

Any ideas?

Chris

  reply	other threads:[~2004-12-16 16:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-15 16:26 slow OOM killing with 2.6.9? Chris Friesen
2004-12-16 11:54 ` Chris Ross
2004-12-16 16:36   ` Chris Friesen [this message]
2004-12-16 17:10   ` Chris Friesen

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=41C1B9A8.2020003@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=akpm@osdl.org \
    --cc=chris@tebibyte.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.