From owner-freebsd-current  Fri Mar 15 06:28:44 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id GAA01783
          for current-outgoing; Fri, 15 Mar 1996 06:28:44 -0800 (PST)
Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA01777
          for <current@FreeBSD.ORG>; Fri, 15 Mar 1996 06:28:37 -0800 (PST)
Received: (from root@localhost) by dyson.iquest.net (8.6.11/8.6.9) id JAA02018; Fri, 15 Mar 1996 09:24:06 GMT
From: "John S. Dyson" <toor@dyson.iquest.net>
Message-Id: <199603150924.JAA02018@dyson.iquest.net>
Subject: Re: -current and accelx
To: coredump@nervosa.com (invalid opcode)
Date: Fri, 15 Mar 1996 09:24:05 +0000 ()
Cc: mmead@Glock.COM, current@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.91.960314234922.1750A-100000@onyx.nervosa.com> from "invalid opcode" at Mar 14, 96 11:50:39 pm
X-Mailer: ELM [version 2.4 PL24 ME8]
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

> 
> On a similar note, I notice XFree86 will run for about 10 mins and than 
> the entire system will freeze. You can ctrl-c out of things, but than you 
> can't run anything after that, it just hangs there excepting terminal 
> input, but doing nothing with it. Other than that, -current is pretty 
> stable as I can see.
> 
Info, info, info :-).  Jordan wants to cut a new snap soon, and I want
to fix the problems for him ASAP.  Anything that you tell me about the hang
I'll be grateful.  I am going to grossly exercise my system tonight, and
will be looking forward for problems to fix.  If you can give me an idea
of what processes are waiting on (the tsleep states from the debugger ps
will help a bit.)

John