From owner-freebsd-current  Fri Oct 11 11:35:54 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA16746
          for current-outgoing; Fri, 11 Oct 1996 11:35:54 -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 LAA16450;
          Fri, 11 Oct 1996 11:32:10 -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 LAA03588; Fri, 11 Oct 1996 11:31:37 -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 LAA00370; Fri, 11 Oct 1996 11:31:37 -0700 (PDT)
Message-Id: <199610111831.LAA00370@base.jnx.com>
To: dg@root.com
cc: dyson@FreeBSD.org, current@FreeBSD.org
Subject: Re: recent kernel panics in the vm system 
In-reply-to: Your message of "Fri, 11 Oct 1996 11:09:37 PDT."
             <199610111809.LAA29261@root.com> 
Date: Fri, 11 Oct 1996 11:31:37 -0700
From: Paul Traina <pst@jnx.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

Right, I screwed the pooch with a last-microsecond change in the code. :-(
Sigh.  I'm committing fixes in a few minutes.

  From: David Greenman <dg@root.com>
  Subject: Re: recent kernel panics in the vm system 
  >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 10
>>th?
  >  > 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 is a bit confused, I think. There is nothing wrong with the PCB
  hashing as far as I'm aware. The problem is with the SYN-flood drop code
  dereferencing a NULL.
  
  -DG
  
  David Greenman
  Core-team/Principal Architect, The FreeBSD Project