public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Christian Kujau <evil@g-house.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOM in 2.6.19-rc*
Date: Sat, 11 Nov 2006 19:53:49 +0100	[thread overview]
Message-ID: <20061111185349.GD25057@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0611111832180.1247@sheep.housecafe.de>

On Sat, Nov 11, 2006 at 06:38:05PM +0000, Christian Kujau wrote:
> On Sat, 11 Nov 2006, Adrian Bunk wrote:
> >Can you test whether an older kernel (preferably the one that worked
> >before) shows the same problem?
> 
> I could try 2.6.17...but currently I don't know how to reproduce the OOM 
> condition - so I'd have to wait 24h until *something* happens and the 
> OOM killer kicks in.

If you want to know what caused your provlem, this is the logical first 
step.

> >This way you might know whether it's a kernel problem or a distribution
> >problem.
> 
> I think I'm more interested as to why the OOM killer seems to kill 
> innocent apps at random. I can imagine that it's not easy for the kernel 
> to tell which userland-application is using up too much memory. Hm, 
> egrep -r "OOM|ut of memory" Documentation/    does not reveal much :(

mm/oom_kill.c is well documented.

> Thanks,
> Christian.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-11-11 18:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 16:40 OOM in 2.6.19-rc* Christian Kujau
2006-11-11 17:23 ` Benoit Boissinot
2006-11-11 18:31   ` Christian Kujau
2006-11-11 18:19 ` Adrian Bunk
2006-11-11 18:38   ` Christian Kujau
2006-11-11 18:53     ` Adrian Bunk [this message]
2006-11-11 19:12       ` Christian Kujau
2006-11-11 20:38     ` Tim Schmielau
2006-11-12  9:15 ` Arjan van de Ven
2006-11-13  0:56   ` Christian Kujau

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=20061111185349.GD25057@stusta.de \
    --to=bunk@stusta.de \
    --cc=evil@g-house.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