From Andre.Albsmeier@mchp.siemens.de  Mon May 26 06:36:32 1997
Received: from david.siemens.de (david.siemens.de [139.23.36.11])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA17616
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 26 May 1997 06:36:30 -0700 (PDT)
Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13])
	by david.siemens.de (8.8.5/8.8.5) with ESMTP id PAA08886
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 26 May 1997 15:31:22 +0200 (MDT)
Received: from curry.mchp.siemens.de (1@curry.mchp.siemens.de [146.180.31.23])
	by salomon.mchp.siemens.de (8.8.5/8.8.5) with ESMTP id PAA14992
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 26 May 1997 15:36:22 +0200 (MDT)
Received: (from daemon@localhost)
	by curry.mchp.siemens.de (8.8.5/8.8.5) id PAA23702
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 26 May 1997 15:36:21 +0200 (MET DST)
Message-Id: <199705261336.PAA00950@curry.mchp.siemens.de>
Date: Mon, 26 May 1997 15:36:04 +0200 (CEST)
From: Andre Albsmeier <Andre.Albsmeier@mchp.siemens.de>
Reply-To: Andre.Albsmeier@mchp.siemens.de
To: FreeBSD-gnats-submit@freebsd.org
Subject: vm problems on 2.2, 2.1.7 works
X-Send-Pr-Version: 3.2

>Number:         3690
>Category:       kern
>Synopsis:       vm problems on 2.2, 2.1.7 works
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon May 26 06:40:01 PDT 1997
>Closed-Date:    Thu Sep 18 04:09:31 PDT 1997
>Last-Modified:  Thu Sep 18 04:09:53 PDT 1997
>Originator:     Andre Albsmeier
>Release:        FreeBSD 2.2-STABLE i386
>Organization:
>Environment:

	Multiple environments running 2.2-STABLE

>Description:

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.

>How-To-Repeat:

cat BigMail |  procmail -f Sender -Y -d User

>Fix:
	
Unknown
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Thu Sep 18 04:09:31 PDT 1997 
State-Changed-Why:  

duplicate see 4524 
>Unformatted:

