From owner-freebsd-current  Fri Oct 11 10:52:31 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA14294
          for current-outgoing; Fri, 11 Oct 1996 10:52:31 -0700 (PDT)
Received: from dyson.iquest.net ([198.70.144.127])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA14289;
          Fri, 11 Oct 1996 10:52:27 -0700 (PDT)
Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id MAA03838; Fri, 11 Oct 1996 12:51:35 -0500 (EST)
From: John Dyson <dyson@dyson.iquest.net>
Message-Id: <199610111751.MAA03838@dyson.iquest.net>
Subject: Re: recent kernel panics in the vm system
To: pst@jnx.com (Paul Traina)
Date: Fri, 11 Oct 1996 12:51:35 -0500 (EST)
Cc: current@FreeBSD.org, dyson@FreeBSD.org
In-Reply-To: <199610111715.KAA04306@red.jnx.com> from "Paul Traina" at Oct 11, 96 10:15:11 am
Reply-To: dyson@FreeBSD.org
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

> 
> John,
> Have you received reports of kernel instability in -current as of Oct 10th?
> I'm seeing a number of panics, and they all started in the last 2 days.
> 
The only problem that is severe that I know of (right now -- might have
forgotten though) is the PCB hashing thing.  I would love to see a
traceback so we can narrow things down.  The VM code itself should be
fairly stable, but a bit slow for low level benchmarks.

John