From: Richard Ems <Richard.Ems@mtg-marinetechnik.de>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org, Hubert Mantel <mantel@suse.de>
Subject: Re: [PROBLEM] Badness in out_of_memory (Plain)
Date: Thu, 06 Jan 2005 18:51:18 +0100 [thread overview]
Message-ID: <41DD7A96.5060006@mtg-marinetechnik.de> (raw)
In-Reply-To: <20050106173052.GW4597@dualathlon.random>
Andrea Arcangeli wrote:
> On Thu, Jan 06, 2005 at 06:03:35PM +0100, Richard Ems wrote:
>
>>Hi list, hi Mr. Mantel,
>>
>>the following "badness" happened on a SuSE 9.2 with all actual updates
>>and SuSE's kernel 2.6.8-24.10-smp.
>>The system is a dual AMD Athlon MP 2200+ with 1GB memory and 1GB swap.
>
>
> This is a warning only (2.6.9 had the swap token breakage that triggered
> suprious oom kills, so the warning was meant to get more info), can you
> try with the kernel of the day?
>
> http://ftp.suse.com/pub/projects/kernel/kotd/9.2-i386/SL92_BRANCH
>
> It has my latest oom fixes that I recently posted to l-k and it should
> be very reliable for the first time in oom-killer terms.
>
>
I will try it tomorrow evening, it's a production system, so it's not so
easy to "try".
How can I trigger the oom kills? I'm not sure if I can easily reproduce
this! Do you know a memory eater program other than starting lots of
mozilla's, OpenOffices's, etc.?
Thanks, Richard
--
Richard Ems
Tel: +49 40 65803 312
Fax: +49 40 65803 392
Richard.Ems@mtg-marinetechnik.de
MTG Marinetechnik GmbH - Wandsbeker Königstr. 62 - D 22041 Hamburg
GF Dipl.-Ing. Ullrich Keil
Handelsregister: Abt. B Nr. 11 500 - Amtsgericht Hamburg Abt. 66
USt.-IdNr.: DE 1186 70571
next prev parent reply other threads:[~2005-01-06 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 17:03 [PROBLEM] Badness in out_of_memory Richard Ems
2005-01-06 17:30 ` Andrea Arcangeli
2005-01-06 17:51 ` Richard Ems [this message]
2005-01-06 23:41 ` [PROBLEM] Badness in out_of_memory (Plain) Andrea Arcangeli
2005-01-07 15:18 ` Richard Ems
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=41DD7A96.5060006@mtg-marinetechnik.de \
--to=richard.ems@mtg-marinetechnik.de \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mantel@suse.de \
/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
all inboxes | Powered by JetHome®