From owner-freebsd-hackers  Mon May 26 07:22:50 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id HAA20750
          for hackers-outgoing; Mon, 26 May 1997 07:22:50 -0700 (PDT)
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA20738
          for <hackers@FreeBSD.ORG>; Mon, 26 May 1997 07:22:19 -0700 (PDT)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.8.5/8.8.5) id QAA07764;
	Mon, 26 May 1997 16:12:48 +0200 (SAT)
From: John Hay <jhay@zibbi.mikom.csir.co.za>
Message-Id: <199705261412.QAA07764@zibbi.mikom.csir.co.za>
Subject: Re: vm problems on 2.2, 2.1.7 works
In-Reply-To: <199705261332.PAA00837@curry.mchp.siemens.de> from Andre Albsmeier at "May 26, 97 03:32:38 pm"
To: Andre.Albsmeier@mchp.siemens.de (Andre Albsmeier)
Date: Mon, 26 May 1997 16:12:48 +0200 (SAT)
Cc: hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Hmmm. This looks a lot like the problem I have on my news server.
It will run ok for a while and then suddenly start to use up all
of the swap. According to top and ps no process is using that
memory, but if I kill innd quick enough all will be ok. So now
I have a script that runs every minute and kill and restart innd
as soon as the swap usage go over some value. Not nice, but it
works until someone find this thingy.

John
-- 
John Hay -- John.Hay@mikom.csir.co.za

> Hi,
> 
> I am running FreeBSD 2.2-STABLE on a 32MB system. When using
> procmail to deliver large mails, procmail dies with a
> "out of memory" message. After that, the system is either in
> an undefined state (producing messages as "junk pointer, too
> low to make sense.") or freezes completely.
> When running a high priority "top" in another window, I see
> the swap being used growing constantly until all of it is
> used. This is reproducable on different HW.
> However, on 2.1.7 systems everything works great.
> 
> Here are some results from my tests:
> 
> System     Version    RAM    SWAP    Mail Size    Status
> ==============================================================
> 486-66      2.1.7    12M     20M    8M/12M/16M     OK
> 486-120     2.1.7    20M     72M    8M/12M/16M     OK
> PPro-200    2.1.7    64M     300M   8M/12M/16M     OK
> 
> PPro-200    2.2      64M     300M   8M/12M         OK
> PPro-200    2.2      64M     300M   16M            FAIL
> P5-166      2.2      32M     150M   8M/12M/16M     FAIL
> P5-166      2.2      64M     150M   8M/12M         OK
> P5-166      2.2      64M     150M   16M            FAIL
> 
> I suspect a problem in the vm system in 2.2 but have no idea
> how to fix it. However, I (and others, who confirmed it via
> email)  can reproduce it... So if I should try something, tell 
> me.
> 
> Thanks for any hints
> 
> 	-Andre
>