From owner-freebsd-current Mon Oct 14 6:31: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3343E37B401 for ; Mon, 14 Oct 2002 06:31:01 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7897E43EAF for ; Mon, 14 Oct 2002 06:31:00 -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 JAA18433; Mon, 14 Oct 2002 09:30:54 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g9EDUOK53796; Mon, 14 Oct 2002 09:30:24 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15786.50928.826403.959175@grasshopper.cs.duke.edu> Date: Mon, 14 Oct 2002 09:30:24 -0400 (EDT) To: Kris Kennaway Cc: Wesley Morgan , current@FreeBSD.ORG Subject: Re: X problems & 5.0... -RELEASE? In-Reply-To: <20021014041422.GA31437@xor.obsecurity.org> References: <20021013231430.F92271-100000@volatile.chemikals.org> <20021014041422.GA31437@xor.obsecurity.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kris Kennaway writes: > On Sun, Oct 13, 2002 at 11:28:51PM -0400, Wesley Morgan wrote: > > > I know there is some work being done on the recent signal changes to fix > > some things, but are we sure this is the problem? I would hate to see > > release schedules pushed back because these problems are lost in the > > noise, and I can't see a release being made that has a known unstable X. > > I thought this was believed to be a bug in X that was exposed by > kernel changes. Given that it (apparently) happens on X servers compiled months ago, my gut feeling is that it is a bug in the kernel floating point context save/restore in the presence of signals. I still can't run X without crashing the *kernel* because of the conglomeration of hacks that was added to i386/machdep.c to paper-over floatingpoing problems after the latest KSE brea^W import. The last machdep.c that works for me is 1.539. This has been dragging on for nearly 2 weeks. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message