From owner-freebsd-current  Sat Apr 20 06:20:41 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id GAA12464
          for current-outgoing; Sat, 20 Apr 1996 06:20:41 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id GAA12459
          for <current@freebsd.org>; Sat, 20 Apr 1996 06:20:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id GAA00206; Sat, 20 Apr 1996 06:20:05 -0700 (PDT)
To: Bruce Evans <bde@zeta.org.au>
cc: current@freebsd.org
Subject: Re: Anyone else notice NFS broken in -current? 
In-reply-to: Your message of "Sat, 20 Apr 1996 20:01:19 +1000."
             <199604201001.UAA02505@godzilla.zeta.org.au> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <203.830006404.1@time.cdrom.com>
Date: Sat, 20 Apr 1996 06:20:05 -0700
Message-ID: <204.830006405@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> The ip header optimizations broken it yesterday.  All large packets
> are probably broken.

:-(

Is this part of a larger fix you're working on, or should we run
with some interim solution to fix the broken state of the world?

> I'm running with the following fix.  Note that it has breakpoint
> instructions to trap the header optimizations that haven't  failed
> yet.

Yep, I just hit one.. :-)  Do you want the crash dump, or do you already
have plenty of your own to look at?

					Jordan