From: Coywolf Qi Hunt <coywolf@gmail.com>
To: Christian Kujau <evil@g-house.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: oom with 2.6.11
Date: Fri, 18 Mar 2005 05:25:07 +0800 [thread overview]
Message-ID: <2cd57c90050317132570147e7c@mail.gmail.com> (raw)
In-Reply-To: <4238DD01.9060500@g-house.de>
On Thu, 17 Mar 2005 02:27:29 +0100, Christian Kujau <evil@g-house.de> wrote:
> hello again,
>
> unfortunately i've hit OOM again, this time with "#define DEBUG" enabled
> in mm/oom_kill.c:
>
> http://nerdbynature.de/bits/sheep/2.6.11/oom/oom_2.6.11.3.txt
>
> by "Mar 16 18:32" pppd died again and OOM kicked in 30min later.
> (there are a *lot* messages of a shell script named "check-route.sh". it's
> a little script which runs every minute or so to check if my default route
> is still ok and if ping to the outside world are possible. definitely not
> a memory hog, but noisy)
I do "grep check-route.sh oom_2.6.11.3.txt | wc" and it shows 4365
lines, which means
there're 4365 that script processes running, from pid 4260 to12747,
mostly with pretty low points, 123. Based on this points, suppose
each script consumes 100k, that'll be 100k*4k=400M roughly. And your
box's is merely 256M MemTotal.
The currently oom algorithm fails to find out such kinds of memory hog.
And the kernel kills other innocent processes because the its points
is much lower than most others.
Check this script and disable it; see what will happen.
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
next prev parent reply other threads:[~2005-03-17 21:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 15:21 oom with 2.6.11 Christian Kujau
2005-03-09 13:18 ` Mauricio Lin
2005-03-09 13:41 ` Mauricio Lin
2005-03-09 14:00 ` Christian Kujau
2005-03-10 15:12 ` Christian Kujau
2005-03-11 0:39 ` Andrew Morton
2005-03-11 1:14 ` Christian Kujau
2005-03-11 7:45 ` Pasi Kärkkäinen
2005-03-11 9:01 ` Mauricio Lin
2005-03-11 15:09 ` Christian Kujau
2005-03-15 8:52 ` Mauricio Lin
2005-03-15 14:12 ` Christian Kujau
2005-03-20 14:35 ` [SOLVED] " Christian Kujau
2005-03-11 10:59 ` Coywolf Qi Hunt
2005-03-11 15:10 ` Christian Kujau
2005-03-12 18:06 ` Christian Kujau
2005-03-17 1:27 ` Christian Kujau
2005-03-17 1:51 ` Andrew Morton
2005-03-17 2:00 ` Christian Kujau
2005-03-17 21:25 ` Coywolf Qi Hunt [this message]
2005-03-18 1:59 ` Christian Kujau
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 13:22 OOM " 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=2cd57c90050317132570147e7c@mail.gmail.com \
--to=coywolf@gmail.com \
--cc=akpm@osdl.org \
--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