From owner-freebsd-current  Fri Oct 11 23:20:15 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id XAA01305
          for current-outgoing; Fri, 11 Oct 1996 23:20:15 -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 XAA01299;
          Fri, 11 Oct 1996 23:20:13 -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 XAA04154; Fri, 11 Oct 1996 23:19:42 -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 XAA01007; Fri, 11 Oct 1996 23:19:41 -0700 (PDT)
Message-Id: <199610120619.XAA01007@base.jnx.com>
To: Karl Denninger <karl@Mcs.Net>
cc: jkh@time.cdrom.com (Jordan K. Hubbard), 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 21:14:23 CDT."
             <199610120214.VAA01365@Jupiter.Mcs.Net> 
Date: Fri, 11 Oct 1996 23:19:41 -0700
From: Paul Traina <pst@jnx.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Karl, are you using LKM's?  I changed the size of the socket structure recently.

  From: Karl Denninger  <karl@Mcs.Net>
  Subject: Re: recent kernel panics in the vm system
  > 
  > I thought that everyone was complaining that Paul's SYN wait fixes
  > had hosed the show, or are we talking about something else?  FWIW,
  > my system is now crashing too, but without any crash dumps being
  > left behind for debugging. :(
  > 
  > 					Jordan
  > 
  
  We have two issues here:
  
  1)	The SYN fixes did hose the show.  We have a prelim patch in which
  	APPEARS to be working (despite an analysis that it shouldn't); no
  	crashes in 30 hours attributable to it (there was one, but this
  	wasn't the cause).  I understand a REAL fix has been committed
  	and should be in tonight's SUPper.
  
  2)	We have another extant problem with NFS in -current.  This one is
  	REALLY odd.  What happens is that directories become inaccessible
  	and "pwd" fails (ie: ftpd cannot determine the current directory).
  	The problem comes and goes without reboot or other prodding that we
  	are able to determine.
  
  The second problem we have no good, hard evidence of a fix for.
  
  --
  --
  Karl Denninger (karl@MCS.Net)| MCSNet - The Finest Internet Connectivity
  http://www.mcs.net/~karl     | T1 from $600 monthly; speeds to DS-3 available
  			     | 23 Chicagoland Prefixes, 13 ISDN, much more
  Voice: [+1 312 803-MCS1 x219]| Email to "info@mcs.net" WWW: http://www.mcs.ne
>>t/
  Fax:   [+1 312 248-9865]     | Home of Chicago's only FULL Clarinet feed!