From owner-freebsd-current  Sat May 25 22:32:08 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id WAA05485
          for current-outgoing; Sat, 25 May 1996 22:32:08 -0700 (PDT)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA05458;
          Sat, 25 May 1996 22:32:05 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id AAA03164; Sun, 26 May 1996 00:31:55 -0500 (EST)
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199605260531.AAA03164@dyson.iquest.net>
Subject: Re: -current panic 5/25 kernel
To: ejc@gargoyle.bazzle.com (Eric J. Chet)
Date: Sun, 26 May 1996 00:31:55 -0500 (EST)
Cc: freebsd-current@freebsd.org, dyson@freebsd.org
In-Reply-To: <Pine.BSI.3.93.960525090335.236A-100000@gargoyle> from "Eric J. Chet" at May 25, 96 09:11:29 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

> Hello
> 	I just made a kernel as of 8:30am EDT 5/25, the system paniced
> very quickly with no load on the system.
> 
> Panic freeing held page, count=1, pindex=32(0x20)
> 
Try again, there was a missing piece of code in vm_fault, and I just
committed it...  I could get it to break regularly by setting my MAXMEM=4384.
MAXMEM=8192 didn't seem to do it for me.

John