From owner-freebsd-hackers  Sun Feb 23 21:54:37 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA29995
          for hackers-outgoing; Sun, 23 Feb 1997 21:54:37 -0800 (PST)
Received: from lightside.com (hamby1.lightside.net [207.67.176.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id VAA29990
          for <hackers@freebsd.org>; Sun, 23 Feb 1997 21:54:33 -0800 (PST)
Received: by lightside.com (SMI-8.6/SMI-SVR4)
	id VAA01312; Sun, 23 Feb 1997 21:55:23 -0800
Date: Sun, 23 Feb 1997 21:55:23 -0800
From: jehamby@lightside.com (Jake Hamby)
Message-Id: <199702240555.VAA01312@lightside.com>
To: hackers@freebsd.org
Subject: Recurring freeze with 2.1.5 system
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-MD5: RsP8+vwYxX6+7rl6UM4t+A==
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

There's a 486 system at my Internet provider that he's set up as a "geek 
box" for people to hack on.  It's a fairly lame configuration (486DX/4 
100MHz, 8MB RAM, IDE drives, NE2000 card).  Anyway, it has a recurring 
problem where it will only answer pings.  Logins, either remote or from the 
console, will hang (telnet will connect, but not prompt for username), and 
the system must be forcibly rebooted.

We think it may be a hardware problem, perhaps bad RAM.  I'm just curious if 
there are any known bugs in 2.1.5-RELEASE which might cause this.  The 
systems are similar to a SYN attack, except for the frozen local login.  
We're going to upgrade it to 2.2-GAMMA next weekend, and hopefully the 
problems will go away.  If not, can we safely conclude that it is a problem 
of buggy hardware?

-- Jake