Re: YIKES!!! A very scary thing happened today [2.2.13] Memory bug?

From: Rik van Riel (riel@nl.linux.org)
Date: Tue Jan 11 2000 - 09:16:27 EST


On Tue, 11 Jan 2000, Lord Apollyon wrote:

> Out of memory for nmbd.
> Out of memory for klogd.
> Out of memory for atalkd.
> Out of memory for checkups.
> Out of memory for powerd.
> Out of memory for rpc.mountd.
> Out of memory for rpc.nfsd.
> Out of memory for tiff2bin.

And all of this with tiff2bin being the obvious `guilty
party'...

> Now, my $64,000 question:
>
> Why didn't the system kill the process that was being the pig
> (tiff2bin)? It seemed to kill processes "early" in the process
> table to free up memory or something. powerd and checkups don't
> allocate memory once they've started up, so they didn't die
> because they were attempting to allocate memory and failed. And
> klogd! I've never seen klogd or syslogd ever die like this.

I have an (old) patch that does try to find the `guilty
party' and get rid of that, and only that. I'll soon move
house and have a test machine (at the office); then I'll
port the patch to 2.2.14 and 2.3.<new> and will fix the
last few bugs in it.

People without that patience are welcome to take a look at
my patches page, grab the (old) OOM killer patch and do the
obvious things (compiling, reading it, sending me comments,
etc)...

        http://www.nl.linux.org/~riel/patches/

cheers,

Rik

--
The Internet is not a network of computers. It is a network
of people. That is its real strength.

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sat Jan 15 2000 - 21:00:18 EST