From owner-freebsd-current  Mon May 20 16:53:35 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA29912
          for current-outgoing; Mon, 20 May 1996 16:53:35 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA29907
          for <current@freebsd.org>; Mon, 20 May 1996 16:53:32 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id SAA01994; Mon, 20 May 1996 18:53:01 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199605202353.SAA01994@dyson.iquest.net>
Subject: Re: Possible problem with new VM code?
To: sysseh@devetir.qld.gov.au (Stephen Hocking)
Date: Mon, 20 May 1996 18:53:01 -0500 (EST)
Cc: current@freebsd.org
In-Reply-To: <199605202338.XAA13440@netfl15a.devetir.qld.gov.au> from "Stephen Hocking" at May 21, 96 09:38:50 am
X-Mailer: ELM [version 2.4 PL24 ME8]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> 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.
> 
Another idea, it appears that some people might be seeing some timing problems.
Try defining splvm to be the same as splhigh in /sys/i386/include/spl.h.

John