From: Con Kolivas <kernel@kolivas.org>
To: Alastair Stevens <alastair.stevens@mrc-bsu.cam.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: VM / OOM troubles in 2.4.20-ck4 (-aa VM)
Date: Wed, 5 Mar 2003 11:27:33 +1100 [thread overview]
Message-ID: <200303051127.33140.kernel@kolivas.org> (raw)
In-Reply-To: <Pine.GSO.4.50.0303041249251.5801-100000@quaratino>
On Tue, 4 Mar 2003 11:58 pm, Alastair Stevens wrote:
> Hi Guys - I was surprised to discover that the very latest 2.4.20
> kernels running the latest -ck patches still have major VM problems,
> even with the -aa VM.
>
> Our dual Athlon server with 512Mb RAM / 1.2Gb swap, and not particularly
> heavily loaded, lasted 81 days with 2.4.20-ck1 under RH8.0, and then
> succumbed with these errors:
>
> VM error: killing process wineserver
> _alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
>
> This time, it only lasted _3 days_ with -ck4 before the same thing
> happened.
>
> I presume this is the OOM killer? Swap is indeed full, but I've no idea
> why, on a machine that's only running a couple of instances of a small
> Windoze app under WINE.
>
> Is there a problem here? Should I just give up and run 2.5? ;-)
My first guess would be wine. There are all sorts of leaks in that.
I'm not aware of any memory leak / vm problems with -ck although that may be
possible. However ck4 does not have the OOM killer enabled so it's not that
in action; you simply have run out of memory and it can't allocate any more.
Have you tried without the aa vm addons in ck? Does this happen with vanilla
2.4.20? -ck is a very different branch.
Con
next prev parent reply other threads:[~2003-03-05 0:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 12:58 VM / OOM troubles in 2.4.20-ck4 (-aa VM) Alastair Stevens
2003-03-04 15:33 ` Mike Galbraith
2003-03-05 0:27 ` Con Kolivas [this message]
2003-03-05 10:20 ` Alastair Stevens
2003-03-11 9:10 ` Alastair Stevens
2003-03-11 9:48 ` Con Kolivas
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=200303051127.33140.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=alastair.stevens@mrc-bsu.cam.ac.uk \
--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