All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <petkov@uni-muenster.de>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Zwane Mwaikambo <zwane@linuxpower.ca>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: OOM-killer killed everything
Date: Sat, 25 Sep 2004 15:50:20 +0200	[thread overview]
Message-ID: <200409251550.20587.petkov@uni-muenster.de> (raw)
In-Reply-To: <20040925125707.GO9106@holomorphy.com>

On Saturday 25 September 2004 14:57, William Lee Irwin III wrote:
> On Sat, 25 Sep 2004, William Lee Irwin III wrote:
> >> Usually I only get "Kernel panic: Out of memory and no killable
> >> processes..." from local DoS testcases; I'd be surprised if anyone
> >> tripped over such cases by accident unless they're doing something
> >> particularly stressful (e.g. forking server with zillions of clients) or
> >> there's a
> >> particularly outrageously offensive memory leak.
>
> On Sat, Sep 25, 2004 at 03:54:59PM +0300, Zwane Mwaikambo wrote:
> > The burning CD audio one is a known issue afaik, i've run into it before
> > too.
>
> That would be the particularly outrageously offensive memory leak, then.
>
>
> -- wli

Thanks to you all guys for the help, I've applied the 2 akpm mm3 patches for 
the 2.6.8.1.  I'll try to repeat the stress test and burn an audio cd at the 
same time but I think not freeing pages of unaligned audio frames while 
burning an audio cd was the reason for the memory leak.

Regards,
Boris.

      reply	other threads:[~2004-09-25 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-25 11:26 OOM-killer killed everything Borislav Petkov
2004-09-25 12:12 ` Alexander E. Patrakov
2004-09-25 12:44 ` William Lee Irwin III
2004-09-25 12:54   ` Zwane Mwaikambo
2004-09-25 12:57     ` William Lee Irwin III
2004-09-25 13:50       ` Borislav Petkov [this message]

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=200409251550.20587.petkov@uni-muenster.de \
    --to=petkov@uni-muenster.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.com \
    --cc=zwane@linuxpower.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.