From owner-freebsd-current Sat Dec 23 21:40:30 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA00528 for current-outgoing; Sat, 23 Dec 1995 21:40:30 -0800 (PST) Received: from gwydion.hns.st-louis.mo.us (root@dialup-66.icon-stl.net [199.217.153.66]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA00519 for ; Sat, 23 Dec 1995 21:40:26 -0800 (PST) Received: (from kenth@localhost) by gwydion.hns.st-louis.mo.us (8.7.3/8.7.2) id XAA00316; Sat, 23 Dec 1995 23:39:54 -0600 (CST) From: Kent Hamilton Message-Id: <199512240539.XAA00316@gwydion.hns.st-louis.mo.us> Subject: Re: Kernel Panic in Current To: mark@linus.demon.co.uk (Mark Valentine) Date: Sat, 23 Dec 1995 23:39:54 -0600 (CST) Cc: KentH@HNS.St-Louis.Mo.US, freebsd-current@FreeBSD.ORG In-Reply-To: <199512240110.BAA00749@linus.demon.co.uk> from "Mark Valentine" at Dec 24, 95 01:10:50 am Reply-To: KentH@HNS.St-Louis.Mo.US X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk > > > > From: Kent Hamilton > > 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... I'm current on it and I'm still getting the panic. I guess I'd like to get some info about the work-around since I consult for the person I'm connecting to and this is my way of getting in to do work. :-) -- Kent Hamilton Work: KHamilton@Hunter.COM URL: http://www.icon-stl.net/~khamilto Play: KentH@HNS.St-Louis.Mo.US