From owner-freebsd-current Mon Oct 14 10:55: 9 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 7387937B401 for ; Mon, 14 Oct 2002 10:55:08 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 1948543EA9 for ; Mon, 14 Oct 2002 10:55:08 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 33412 invoked by uid 1000); 14 Oct 2002 17:55:08 -0000 Date: Mon, 14 Oct 2002 10:55:08 -0700 (PDT) From: Nate Lawson To: Andrew Gallatin Cc: current@freebsd.org Subject: Re: X problems & 5.0... -RELEASE? In-Reply-To: <15786.50928.826403.959175@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 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. Thanks, Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message