Date: Mon, 14 Oct 2002 09:30:24 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Kris Kennaway <kris@obsecurity.org> Cc: Wesley Morgan <morganw@chemikals.org>, current@FreeBSD.ORG Subject: Re: X problems & 5.0... -RELEASE? Message-ID: <15786.50928.826403.959175@grasshopper.cs.duke.edu> In-Reply-To: <20021014041422.GA31437@xor.obsecurity.org> References: <20021013231430.F92271-100000@volatile.chemikals.org> <20021014041422.GA31437@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15786.50928.826403.959175>