From: Marc-Christian Petersen <mcp@linux-systeme.de>
To: linux-kernel@vger.kernel.org
Subject: Kernel 2.4.18 and strange OOM Killer behaveness
Date: Fri, 26 Apr 2002 16:38:08 +0200 [thread overview]
Message-ID: <200204261636.14573.mcp@linux-systeme.de> (raw)
Hi there,
i just opened an 800mb movie file with pico/nano, waited for the OOM, and here
it is, have a look:
Apr 26 16:10:45 codeman kernel: Out of Memory: Killed process 19789 (apache).
Apr 26 16:10:46 codeman kernel: Out of Memory: Killed process 27828 (apache).
Apr 26 16:10:48 codeman kernel: Out of Memory: Killed process 14554 (apache).
Apr 26 16:10:50 codeman kernel: Out of Memory: Killed process 19893 (apache).
Apr 26 16:10:52 codeman kernel: Out of Memory: Killed process 32036 (apache).
Apr 26 16:10:54 codeman kernel: Out of Memory: Killed process 8370 (apache).
Apr 26 16:10:56 codeman kernel: Out of Memory: Killed process 680 (mysqld).
Apr 26 16:10:56 codeman kernel: Out of Memory: Killed process 7638 (mysqld).
Apr 26 16:10:56 codeman kernel: Out of Memory: Killed process 26780 (mysqld).
Apr 26 16:10:56 codeman kernel: Out of Memory: Killed process 26038 (mysqld).
Apr 26 16:11:01 codeman kernel: Out of Memory: Killed process 3914 (pico).
Apr 26 16:11:01 codeman kernel: VM: killing process pico
Apr 26 16:11:04 codeman kernel: Out of Memory: Killed process 20471 (squid).
So, you guess, apache, mysqld, squid and the causer pico are killed, but NO,
ONLY, and i mean ONLY pico was killed, all the other Processes listed above
are running fine, accepting connections, short: works fine!!
And yes, its reproduceable !!
The above is a kernel without rmap!
I also tried this with rmap enabled kernel, no OOM Messages appears, but the
system freezes. It does NOT accept any input on keyboard, mouse or via the
network (e.g ping, traceroute, telnet to smtp port etc.). Also, if the system
does not accept any input, the harddisk is doing something, i've waited ~ 45
minutes, system was still not accepting anything, harddisk was doing
anything. This was rmap12h with 2.4.18.
Kinda strange, isn't it?! :-)
I like it, cause only the causer get killed, but why those syslog messages?!
Syslogd lies like a trooper ;)
--
Kind regards
Marc-Christian Petersen
http://sourceforge.net/projects/wolk
PGP/GnuPG Key: 1024D/569DE2E3DB441A16
Fingerprint: 3469 0CF8 CA7E 0042 7824 080A 569D E2E3 DB44 1A16
Key available at wwwkeys.pgp.net. Encrypted e-mail preferred.
next reply other threads:[~2002-04-26 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-26 14:38 Marc-Christian Petersen [this message]
2002-04-26 19:56 ` Kernel 2.4.18 and strange OOM Killer behaveness Diego Calleja
2002-04-27 14:29 ` Alvaro Figueroa
-- strict thread matches above, loose matches on Subject: below --
2002-04-26 17:46 Dieter Nützel
2002-04-26 21:25 ` Andrea Arcangeli
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=200204261636.14573.mcp@linux-systeme.de \
--to=mcp@linux-systeme.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