From: Andrea Arcangeli <andrea@suse.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: akpm@osdl.org, Nick Piggin <piggin@cyberone.com.au>, linux-mm@kvack.org
Subject: Re: [cliffw@osdl.org: Re: 2.6.10-ac12 + kernbench == oom-killer: (OSDL)]
Date: Sat, 19 Feb 2005 17:56:33 +0100 [thread overview]
Message-ID: <20050219165633.GC7247@opteron.random> (raw)
In-Reply-To: <20050219202703.GD4874@dmt.cnet>
On Sat, Feb 19, 2005 at 06:27:03PM -0200, Marcelo Tosatti wrote:
>
> FYI
>
> ----- Forwarded message from cliff white <cliffw@osdl.org> -----
>
> From: cliff white <cliffw@osdl.org>
> Date: Thu, 17 Feb 2005 12:49:16 -0800
> To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
> Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
> Subject: Re: 2.6.10-ac12 + kernbench == oom-killer: (OSDL)
>
> On Wed, 9 Feb 2005 10:12:06 -0200
> Marcelo Tosatti <marcelo.tosatti@cyclades.com> wrote:
>
> > On Tue, Feb 08, 2005 at 02:57:07PM -0800, cliff white wrote:
> > >
> > > Running 2.6.10-ac10 on the STP 1-CPU machines, we don't seem to be able to complete
> > > a kernbench run without hitting the OOM-killer. ( kernbench is multiple kernel compiles,
> > > of course ) Machine is 800 mhz PIII with 1GB memory. We reduce memory for some of the runs.
> >
> > Cliff,
> >
> > Please try recent v2.6.11-rc3, they include a series of OOM killer fixes from Andrea et all.
> >
>
> Sorry for the delay in response. Recent -bk runs still show this problem, for example:
> http://khack.osdl.org/stp/300713/logs/TestRunFailed.console.log.txt
> ( patch-2.6.11-rc3-bk4 )
What is the problem? It looks genuine oom.
Free swap = 0kB
And only one task was killed (you might see two logs, but that's fine,
it's the same task 13188 that was sent a signal twice, and this is
intentional to happen sometime).
This could be one of those .c files that grows like crazy and allocates
tons of ram when you compile it (I've seen one that grows to the
gigabites).
Please let me know if I overlooked something, thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2005-02-19 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 20:27 Marcelo Tosatti
2005-02-19 16:56 ` Andrea Arcangeli [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=20050219165633.GC7247@opteron.random \
--to=andrea@suse.de \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=piggin@cyberone.com.au \
/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