From owner-freebsd-questions  Fri Jun  7 21:00:29 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA01497
          for questions-outgoing; Fri, 7 Jun 1996 21:00:29 -0700 (PDT)
Received: from hod.tera.com (hod.tera.com [206.215.142.67])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA01482
          for <questions@freebsd.org>; Fri, 7 Jun 1996 21:00:23 -0700 (PDT)
Received: from athena.tera.com (athena.tera.com [206.215.142.62]) by hod.tera.com (8.7.5/8.7.3) with ESMTP id UAA21487; Fri, 7 Jun 1996 20:59:00 -0700 (PDT)
From: Gary Kline <kline@tera.com>
Received: (from kline@localhost) by athena.tera.com (8.7.5/8.7.3) id UAA13381; Fri, 7 Jun 1996 20:58:58 -0700 (PDT)
Message-Id: <199606080358.UAA13381@athena.tera.com>
Subject: Re: lockups
To: cslye@info.infosite.com (Cameron Slye)
Date: Fri, 7 Jun 1996 20:58:58 -0700 (PDT)
Cc: cslye@info.infosite.com, questions@freebsd.org
In-Reply-To: <199606070413.VAA00249@info.infosite.com> from Cameron Slye at "Jun 6, 96 09:13:57 pm"
X-Mailer: ELM [version 2.4ME+ PL11 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

According to Cameron Slye:
> > I am having a problem with a 2.1.0-RELEASE box.  Seems after a while of
> > using the SLIP/CSLIP stuff the console locks, sometimes I can keep working
> > on it via telnet etc, and sometimes it locks the box (ie no pings etc)
> > I am using dip to dialup and login.  I have also used the startslip, and it
> > does the same thing.  I have tried a diffrent video card, and tried removing
> > the network card.  Have also tried the other serial port.  None of these
> > seem to have worked.  Any other ideas ?  On a side note, I would try PPP and
> > see if that works, but cant get it to work, just times out waiting for lcp
> > info..  Even thought I know the portmaster is sending it.
> 
> 
> Update on this, I have used PPP now and it does the same thing.  I have also
> disabled routed.  Anything else anyone can think of doing ?
> 


	The same thing began happening on my 2.0.5 system in the
	past several days.  Previously, no trouble.  Given this,
	I figured that there might be some inconsistancy in the 
	filesystem.  

	Long-story-short: fsck'ing everything found that my /var
	fs was damaged.  It's been a day or two since I did the
	fs check and clean.  So far, so good.

	You might want to try doing a number of fsck runs until
	everything is *clean*.   Reboot and see if the lockup
	problem reoccurs.

	gary line