From owner-freebsd-current  Sat Dec 23 17:10:24 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA08199
          for current-outgoing; Sat, 23 Dec 1995 17:10:24 -0800 (PST)
Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id RAA08192
          for <freebsd-current@FreeBSD.ORG>; Sat, 23 Dec 1995 17:10:18 -0800 (PST)
Received: (from mark@localhost) by linus.demon.co.uk (8.7.3/8.7.3) id BAA00749; Sun, 24 Dec 1995 01:10:50 GMT
Message-Id: <199512240110.BAA00749@linus.demon.co.uk>
From: mark@linus.demon.co.uk (Mark Valentine)
Date: Sun, 24 Dec 1995 01:10:50 +0000
In-Reply-To: Kent Hamilton's message of Dec 23,  5:19pm
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: KentH@HNS.St-Louis.Mo.US, freebsd-current@FreeBSD.ORG
Subject: Re: Kernel Panic in Current
Sender: owner-current@FreeBSD.ORG
Precedence: bulk

> From: Kent Hamilton <kenth@HNS.St-Louis.Mo.US>
> Date: Sat 23 Dec, 1995
> Subject: Kernel Panic in Current

> I'm able to re-produce this pretty much at will by connecting using 
> usermode ppp to my service provider, then connecting to a remote 
> machine that is connected to the same provider via a 14.4 modem and
> SLIP.

Garrett committed a fix for this recently - see sys/netinet/tcp_subr.c.

 *      $Id: tcp_subr.c,v 1.25 1995/12/20 17:42:28 wollman Exp $

If you're up to date and still having problems, I can probably help you
with a workaround...

		Cheers,

		Mark.