From owner-freebsd-current  Fri Oct 11 10:57:19 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA14485
          for current-outgoing; Fri, 11 Oct 1996 10:57:19 -0700 (PDT)
Received: from red.jnx.com (red.jnx.com [208.197.169.254])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA14464;
          Fri, 11 Oct 1996 10:56:30 -0700 (PDT)
Received: from base.jnx.com (base.jnx.com [208.197.169.238]) by red.jnx.com (8.7.6/8.7.3) with ESMTP id KAA00818; Fri, 11 Oct 1996 10:55:51 -0700 (PDT)
Received: from base.jnx.com (localhost.jnx.com [127.0.0.1]) by base.jnx.com (8.7.6/8.7.3) with ESMTP id KAA01433; Fri, 11 Oct 1996 10:55:50 -0700 (PDT)
Message-Id: <199610111755.KAA01433@base.jnx.com>
To: dyson@FreeBSD.org
cc: current@FreeBSD.org
Subject: Re: recent kernel panics in the vm system 
In-reply-to: Your message of "Fri, 11 Oct 1996 12:51:35 CDT."
             <199610111751.MAA03838@dyson.iquest.net> 
Date: Fri, 11 Oct 1996 10:55:50 -0700
From: Paul Traina <pst@jnx.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

I found at least two bugs in my recent tcp/socket changes, but those don't
seem to be the cause of my recent crashes.  I wasn't aware there was any
unstability with the PCB hashing, I'll look there next, thanks.

Paul

  From: John Dyson <dyson@dyson.iquest.net>
  Subject: Re: recent kernel panics in the vm system
  > 
  > 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