From owner-freebsd-stable  Mon Mar 25 18:23:16 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA29123
          for stable-outgoing; Mon, 25 Mar 1996 18:23:16 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id SAA29118
          for <stable@freebsd.org>; Mon, 25 Mar 1996 18:23:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id SAA29660; Mon, 25 Mar 1996 18:21:37 -0800 (PST)
To: "Marc G. Fournier" <scrappy@ki.net>
cc: stable@freebsd.org
Subject: Re: Stable not very stable 
In-reply-to: Your message of "Mon, 25 Mar 1996 16:23:42 EST."
             <Pine.BSF.3.91.960325161320.242A-100000@ki.net> 
Date: Mon, 25 Mar 1996 18:21:37 -0800
Message-ID: <29658.827806897@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 	Essentially, the system does a bunch of disk thrashing (I believe
> its thrashing while it unbatches news, but am not 100% certain that that is
> what it is doing), then it grinds to a complete halt.
> 
> 	I can change VT's, but that is about it.

FWIW, that failure mode has been reported by others.  Any chance of
swapping this motherboard for something other than a DX4, just to
narrow this a little?  The failures seem to happen about 500% more
often with the DX4 parts, though I'm not sure why.

					Jordan