From lamarcjp@dmr.ca  Wed Feb  1 10:41:38 1995
Received: from poterne.mtl.dmr.ca (poterne.mtl.dmr.ca [192.219.247.65]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id KAA01564 for <FreeBSD-gnats-submit@freebsd.org>; Wed, 1 Feb 1995 10:41:33 -0800
Received: (from lamarcjp@localhost) by poterne.mtl.dmr.ca (8.6.9/8.6.6) id KAA06419; Wed, 1 Feb 1995 10:16:11 -0500
Message-Id: <199502011516.KAA06419@poterne.mtl.dmr.ca>
Date: Wed, 1 Feb 1995 10:16:11 -0500
From: lamarcjp@dmr.ca
Reply-To: lamarcjp@dmr.ca
To: FreeBSD-gnats-submit@freebsd.org
Subject: Crash & Hang problems
X-Send-Pr-Version: 3.2

>Number:         202
>Category:       misc
>Synopsis:       System hang or reboot without clues, tcp ppp named routed?
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          support
>Submitter-Id:   current-users
>Arrival-Date:   Wed Feb  1 10:50:01 1995
>Closed-Date:    Thu Feb 8 08:33:09 PST 1996
>Last-Modified:  Thu Feb  8 08:33:54 PST 1996
>Originator:     Jean-Pierre Lamarche
>Release:        FreeBSD 2.1.0-Development i386
>Organization:
DMR inc.
>Environment:
 Our system is a 386 with FreeBsd 2.0. It serves as an Internet 
 gateway. The main link with our provider is with a 28,000bps modem with PPP.
 We aded a couple a serial cards and we provide 4x14000bps links in,
 for our users with SLIP. They mostly use Netscape for news and
 some surfing.
 

>Description:
 Please refer to prob misc/83, we already sent you a problem report. The answer
 was to try to new snap-shot, which we did, but our problem is still there. 
 Before the upgrade to the snap-shot I was able to reproduce the crash by 
 abruptlu ending a slip session.(the system would reboot with no messages or
 core). Now I dont seem to be able to reproduce this anymore, after the upgrade.
 But we still get an average of 1 crash per day, at random times. We really
 would apreciate any clues as to where to look. It was suggested that it was
 a hardware problem but we did not have any problems we our current hardware
 before upgrading to 2.0. We dont seem to be the only ones with a similar
 problem. There are dicussions in the news-groups, about people having 
 unexplained reboot, using slip or ppp. Also people are talking about named,
 routed problems. We are starting to get desperate and contemplating 
 reinstalling a 1.xxx version to see if this would be more stable. We would
 hate taking a step backwards.


>How-To-Repeat:

See above

>Fix:
	
	

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: wollman 
State-Changed-When: Thu Feb 8 08:33:09 PST 1996 
State-Changed-Why:  
This PR is stale.  If the problem still persists, please send 
a PR against the current system. 
>Unformatted:


