public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jorge Nerin <comandante@zaralinux.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Linux SMP <linux-smp@vger.kernel.org>
Subject: Memory management issues with 2.4.4
Date: Wed, 02 May 2001 16:57:13 +0200	[thread overview]
Message-ID: <3AF02049.1080901@zaralinux.com> (raw)

Short version:
Under very heavy thrashing (about four hours) the system either lockups 
or OOM handler kills a task even when there is swap space left.

Long version:
My system is a dual 2x200MMX in a Gigabyte 586DX with 96Mb and 226Mb of 
swap this way:

[root@quartz ~]# swapon -s
Filename                        Type            Size    Used    Priority
/dev/hda7                       partition       96348   6456    1
/dev/hdc6                       partition       130276  6460    1

Well, I have tried to compile Mozilla 0.8.1 since the day it came out, 
but I always lockup in the same place, wich it's begining to be a bit 
frustrating ;-)

The problem is that compiling the file  
content/base/src/nsStyleContext.o makes cc1plus grow up to a size of 
141M, at this point the system is in heavy thrashing, kswapd is using 
about 7-12% of CPU time and cc1plus is using 8-14%.

If I use a SMP kernel the system always ends up frozen, some times after 
about almost one day of uptime and compiling since booting, and another 
times  it gets frozen in much less time, three or four hours.

If I use a non SMP kernel the system doesn't lokup but after some hours, 
it varies between 6-8h, the cc1plus procces get a kill signal by OOM 
killer, althought there is plenty of swap space left ((96Mb RAM + 226Mb 
swap) - (140Mb - tiny amount used by the system) = plenty ;-).

For this tries I have left the system in single user, so no cron jobs, 
no network trafic, no etc...

I suspect there is a race in the swap handling in SMP, and that the OOM 
doesn't take into account the swap space left sometimes.

I don't know what to try next, suggestions?

-- 
Jorge Nerin
<comandante@zaralinux.com>


             reply	other threads:[~2001-05-02 18:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02 14:57 Jorge Nerin [this message]
2001-05-02 19:27 ` Memory management issues with 2.4.4 Marcelo Tosatti
2001-05-04  6:31   ` Jorge Nerín
2001-05-04 15:29   ` Jorge Nerin

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=3AF02049.1080901@zaralinux.com \
    --to=comandante@zaralinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-smp@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