From owner-freebsd-alpha  Wed Jul 26 17: 2:34 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8C13137B7B7; Wed, 26 Jul 2000 17:02:31 -0700 (PDT)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id UAA11939;
	Wed, 26 Jul 2000 20:02:30 -0400 (EDT)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.9.3/8.9.1) id UAA68613;
	Wed, 26 Jul 2000 20:02:29 -0400 (EDT)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 26 Jul 2000 20:02:29 -0400 (EDT)
To: obrien@freebsd.org
Cc: freebsd-alpha@freebsd.org
Subject: XFree86 4.0.1
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14719.30658.265885.818087@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Well.. It seems that XFree86-4.0.1 is not without bugs.

I've been using my home miata more intensely these days, and noticed
that the X server still has problems.  About 1/3 of the time, the X
server will lock solid & will be unkillable unless you give it a kill
-9, and then it doesn't release the console & you cannot restart X.
When this is happening, its in a tight CPU bound loop, and its not
making any system calls (according to ktrace).

The other 2/3 of the time, it gets into a funky state where the screen
is not being properly refreshed, but you can at least exit from it ;-)

These feel like compiler bugs.

I noticed that the XFree86-4 port is patching the OptimizedCDebugFlags 
to be ''.   This reminded me of the problem that I diagnosed a few
months ago where a person had a massively unstable system due to his
setting CFLAGS to '-pipe' in /etc/make.conf (thereby omitting -O).

I'm rebuilding XFree86-4 right now with OptimizedCDebugFlags set to -O
to see if it improves things..

Drew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message