From owner-freebsd-current  Mon May 20 16:43:35 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA29293
          for current-outgoing; Mon, 20 May 1996 16:43:35 -0700 (PDT)
Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA29273
          for <current@freebsd.org>; Mon, 20 May 1996 16:43:26 -0700 (PDT)
Received: from bunyip.cc.uq.oz.au by bunyip.cc.uq.oz.au 
          id <02038-0@bunyip.cc.uq.oz.au>; Tue, 21 May 1996 09:37:50 +1000
Received: from netfl15a.devetir.qld.gov.au 
          by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP 
          id JAA29223; Tue, 21 May 1996 09:38:26 +1000
Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) 
          id XAA13440; Mon, 20 May 1996 23:38:52 GMT
Message-Id: <199605202338.XAA13440@netfl15a.devetir.qld.gov.au>
X-Mailer: exmh version 1.6.5 12/11/95
To: current@freebsd.org
cc: toor@dyson.iquest.net
Subject: Possible problem with new VM code?
X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 
        7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! 
        >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 
        M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 21 May 1996 09:38:50 +1000
From: Stephen Hocking <sysseh@devetir.qld.gov.au>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I compiled up the new VM patches (as at ctm src-cur 1804) and installed them 
on my home machine (486/66, 8Mb, 1542B, barracuda). Whilst running the X 
server & two xterms, I ran systat -vmstat in one and started doing a make all 
install of libc_r in the other. It seemed to be paging more heavily than I 
expected, so I switched WM focus (I was using 9wm as the window manager) to 
the window running systat. This took far longer than I expected (9wm only has 
about 32k of text, without counting the shared libs & my Xserver has PEX & 
other cruft stripped out), with a high level of disk activity being 
maintained. I typed :q to get out of systat, which led to an even higher level 
of disk activity. The system then froze. I have a kernel with DDB compiled in, 
but with running X, I could not switch back to the console to see where it had 
died, or provoke a dump to dissect later. 

Now I compiled all the userland binaries recently, and systat did seem to be 
picking up all the right stats, but I was wondering if systat could have been 
leaking memory at a furious rate and hence caused problems by exhausting VM, 
owing to some sort of mismatch in what it thought kernel structures looked 
like and how they actually were. I'll try recompiling everything else & get 
back to you.


	Stephen
-- 
The views expressed above are not those of the Worker's Compensation Board of
Queensland, Australia.