From: Faik Uygur <faikuygur@ttnet.net.tr>
To: David Mansfield <lkml@dm.cobite.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oom killer and its superior braindamage in 2.4
Date: Sun, 23 Feb 2003 18:25:04 +0200 [thread overview]
Message-ID: <20030223162504.GA3137@ttnet.net.tr> (raw)
In-Reply-To: <Pine.LNX.4.44.0302231058070.23778-100000@admin>
> This exact thing happened to me as well, on a 2.4.20-pre that hasn't been
> upgraded to 2.4.20 yet. The thing that concerns me most is:
>
> Why won't the system kill the process it claims to be killing?
>
> If, in Marc's case, the system wants to kill PID 2657, a lowly sleeping
> apache process, why can't it? This is a bug for sure.
>
> For me, there was some python process chosen as the one for killing and it
> repeated the 'Out of Memory: Killed process xxxxx (python)' for hours
> while making no progress. The machine was still routing packets but I
> couldn't log in. Sys-rq was disabled, so I was forced to use the big red
> button.
>
> Rik, any ideas?
But, did you follow that thread? Rik van Riel, already suggested a solution for
the problem.
http://marc.theaimsgroup.com/?l=linux-kernel&m=104594301523518&w=2
next prev parent reply other threads:[~2003-02-23 16:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 16:06 David Mansfield
2003-02-23 16:25 ` Faik Uygur [this message]
2003-02-23 16:25 ` Rik van Riel
2003-02-23 18:07 ` David Mansfield
2003-02-23 20:14 ` Rik van Riel
2003-02-23 20:22 ` David Mansfield
2003-02-23 20:53 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2003-02-24 9:13 Mikael Starvik
2003-02-24 9:27 ` Marc-Christian Petersen
2003-02-22 19:35 Marc-Christian Petersen
2003-02-22 20:14 ` Rik van Riel
2003-02-22 20:32 ` Rik van Riel
2003-02-23 17:35 ` Marc-Christian Petersen
2003-02-23 20:18 ` Rik van Riel
2003-02-23 20:29 ` Marc-Christian Petersen
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=20030223162504.GA3137@ttnet.net.tr \
--to=faikuygur@ttnet.net.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dm.cobite.com \
/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
all inboxes | Powered by JetHome®