From: David Ford <david+cert@blue-labs.org>
To: linux-kernel@vger.kernel.org
Subject: kernel unable to kill processes? OOM bug
Date: Thu, 05 Sep 2002 09:55:04 -0400 [thread overview]
Message-ID: <3D776238.1050805@blue-labs.org> (raw)
This is 2.4.20-pre5
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21728 (httpd).
Out of Memory: Killed process 21917 (httpd).
sending pkt_too_big (len[1500] pmtu[1492]) to self
Out of Memory: Killed process 22362 (httpd).
Out of Memory: Killed process 22186 (httpd).
Out of Memory: Killed process 19465 (httpd).
(side note: why the pkt_too_big message? eth0 is 1500 and lo is 16436)
David
--
I may have the information you need and I may choose only HTML. It's up to
you. Disclaimer: I am not responsible for any email that you send me nor am
I bound to any obligation to deal with any received email in any given
fashion. If you send me spam or a virus, I may in whole or part send you
50,000 return copies of it. I may also publically announce any and all
emails and post them to message boards, news sites, and even parody sites.
I may also mark them up, cut and paste, print, and staple them to telephone
poles for the enjoyment of people without internet access. This is not a
confidential medium and your assumption that your email can or will be
handled confidentially is akin to baring your backside, burying your head in
the ground, and thinking nobody can see you butt nekkid and in plain view
for miles away. Don't be a cluebert, buy one from K-mart today.
reply other threads:[~2002-09-05 13:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D776238.1050805@blue-labs.org \
--to=david+cert@blue-labs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox