From owner-freebsd-current Mon Oct 14 10:59: 5 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 9396237B401 for ; Mon, 14 Oct 2002 10:59:04 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E16443EAC for ; Mon, 14 Oct 2002 10:58:57 -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 NAA28292; Mon, 14 Oct 2002 13:58:56 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g9EHwQJ54052; Mon, 14 Oct 2002 13:58:26 -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: <15787.1474.824422.286474@grasshopper.cs.duke.edu> Date: Mon, 14 Oct 2002 13:58:26 -0400 (EDT) To: Nate Lawson Cc: current@freebsd.org Subject: Re: X problems & 5.0... -RELEASE? In-Reply-To: References: <15786.50928.826403.959175@grasshopper.cs.duke.edu> 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 Nate Lawson writes: > On Mon, 14 Oct 2002, Andrew Gallatin wrote: > > 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 > > I don't know how to say this strongly enough but can someone PLEASE PLEASE > fix this properly? It is preventing real work from getting done. I think we're all waiting for Julian and Jonathan Mini to fix this.. It would probably help if they had some sort of a test program that could duplicate the bug in a controlled setting without a lot of confusing application software running.. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message