From nobody@FreeBSD.ORG Sat Jul 17 21:36:07 1999
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id 6AA1214C0E; Sat, 17 Jul 1999 21:36:07 -0700 (PDT)
Message-Id: <19990718043607.6AA1214C0E@hub.freebsd.org>
Date: Sat, 17 Jul 1999 21:36:07 -0700 (PDT)
From: davestg@bigfoot.com
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@freebsd.org
Subject: 3.1-RELEASE freezes when another client on a LAN connects
X-Send-Pr-Version: www-1.0

>Number:         12688
>Category:       misc
>Synopsis:       3.1-RELEASE freezes when another client on a LAN connects
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Jul 17 21:40:01 PDT 1999
>Closed-Date:    Thu Jul 22 00:02:02 PDT 1999
>Last-Modified:  Thu Jul 22 00:02:24 PDT 1999
>Originator:     Dave St.Germain
>Release:        3.1-RELEASE
>Organization:
>Environment:
FreeBSD guardian.dotdot.us 3.1-RELEASE FreeBSD 3.1-RELEASE #12: Sun Jul 11 23:34:24 EDT 1999     root@guardian.dotdot.us:/usr/src/sys/compile/GUARDIAN  i386

5x86 133Mhz with a DEC 21040 connected on a BNC LAN to a windows 80Mhz 486 with a 3Com 509	

>Description:
FreeBSD will completely lock up if I connect from the windows machine.  The problem seems
random, but I haven't been able to keep an uptime of more than 3 days.  I have
ipfw and natd as well as ppp running, and the internet link works MOST of the time.
However, recently, FreeBSD has crashed during normal use of natd and ipfw.  I 
can't be exactly sure as to where the problem is because there is no information
on the console at the time of the freeze, and there is no indication in any logs.
>How-To-Repeat:
Connect via telnet or ftp from the windows machine.  Various events have triggered
a freeze including "more", transferring files to FreeBSD from windows, sending 
mail to sendmail which gets bounced back, accessing POP too many times, trying to use
Apache as a proxy for more than 1 minute, accessing a web page.
>Fix:
Don't connect to freebsd with the windows machine.  Everything works fine on
the FreeBSD side when connected to the internet; it only crashes at certain times
when connecting from windows (or any host?  I might boot up with PicoBSD on the
Windows machine and hammer it...)


>Release-Note:
>Audit-Trail:

From: "Dave St.Germain" <davestg@bigfoot.com>
To: freebsd-gnats-submit@freebsd.org, davestg@bigfoot.com
Cc:  
Subject: Re: misc/12688: 3.1-RELEASE freezes when another client on a LAN 
 connects
Date: Wed, 21 Jul 1999 17:14:02 -0400

 I consider this report closed.  The fix was in the BIOS.  I had to
 disable the PCI burst settings, and now everything works fine.  The
 settings worked under Linux, but I guess the de driver under FreeBSD
 isn't as forgiving.  Thanks to all that helped.
 
 				Dave
 
State-Changed-From-To: open->closed 
State-Changed-By: n_hibma 
State-Changed-When: Thu Jul 22 00:02:02 PDT 1999 
State-Changed-Why:  
Submitter states that the problem was in the BIOS and has been resolved. 
>Unformatted:
