From owner-freebsd-current  Sun Aug  4 16:55:44 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA03220
          for current-outgoing; Sun, 4 Aug 1996 16:55:44 -0700 (PDT)
Received: from whistle.com (s205m131.whistle.com [207.76.205.131])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA03215
          for <current@FreeBSD.org>; Sun, 4 Aug 1996 16:55:41 -0700 (PDT)
Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA13769; Sun, 4 Aug 1996 16:55:10 -0700 (PDT)
Received: from shrimp.whistle.com(207.76.205.74) by whistle.com via smap (V1.3)
	id sma013767; Sun Aug  4 16:55:06 1996
Received: (from julian@localhost) by shrimp.whistle.com (8.6.12/8.6.12) id QAA06353; Sun, 4 Aug 1996 16:55:06 -0700
From: Julian Elischer <julian@whistle.com>
Message-Id: <199608042355.QAA06353@shrimp.whistle.com>
Subject: Re: problem with -current system grinding to a halt...
To: msmith@atrad.adelaide.edu.au (Michael Smith)
Date: Sun, 4 Aug 1996 16:55:06 -0700 (PDT)
Cc: scrappy@ki.net, msmith@atrad.adelaide.edu.au, dg@root.com,
        current@FreeBSD.org
In-Reply-To: <199608042234.IAA09424@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Aug 5, 96 08:04:45 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

do you have cmomconsole?
if so, you should drop into ddb and do a ps..
that'll tell you what everything is hanging on..
alternatively,
set the default tty mode to include stty status ^T
and then if s process hangs, and you are logger into it, you can do a ^T
and see what it's waiting for.....


> 
> Marc G. Fournier stands accused of saying:
> > > 
> > > I should have been clearer I guess; the 'w' freeze was coincidental -
> > > the system dies _consistently_ after about 18 hours of uptime, with no
> > > console messages.  Regardless of whether I'm logged in or not, and
> > > apparently unrelated to any specific system activity.  I say 'apparently'
> > > because it's not easy to see exactly what the system is doing.
> > >
> > 
> > 	This sounds like the SCSI bus hangs I used to get with one of
> > my systems...where everything seemed to be running until you tried to
> > deal with somethin gthat had to go to the drive (ie. login, w, df, etc)
> > 
> > 	When this happens, check your drive...does the hard drive light
> > come on and stay on?
> 
> I can't tell.  It's in Sweden and I'm not. 8(
> 
> How did you eventually resolve your problem?
> 
> > Marc G. Fournier                                  scrappy@ki.net
> 
> -- 
> ]] Mike Smith, Software Engineer        msmith@atrad.adelaide.edu.au    [[
> ]] Genesis Software                     genesis@atrad.adelaide.edu.au   [[
> ]] High-speed data acquisition and      (GSM mobile) 0411-222-496       [[
> ]] realtime instrument control          (ph/fax)  +61-8-267-3039        [[
> ]] Collector of old Unix hardware.      "Where are your PEZ?" The Tick  [[
>