Date: Tue, 8 Oct 2002 09:04:27 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Maxim Sobolev <sobomax@FreeBSD.ORG> Cc: freebsd-current@FreeBSD.ORG Subject: Re: sorry state of Xserver in 5.0 Message-ID: <15778.55259.990703.531720@grasshopper.cs.duke.edu> In-Reply-To: <20021008064433.GA77334@vega.vega.com> References: <15777.52918.689192.919124@grasshopper.cs.duke.edu> <20021008064433.GA77334@vega.vega.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Maxim Sobolev writes: > > Between this, and the Type1 bezier font abort, the state of 5.0 on a > > desktop is very sorry indeed. My old alpha running -stable is far > > more stable. > > > > Sigh. > > Agreed. I could add that after recent kernel updating I'm also often > observing XFree86 dying with SIGFPU. I guess that it may have something > to do with recent context saving changes. Note that the recent sys/i386/i386/machdep.c (1.540 and 1.541) should be backed out if you're running any FP apps (like, say, X). It somehow messes up the fp context and causes a gpf. Happens to me when I start gnome2. 1.539 more or less works, albeit with the problems I'm compaining about above. Question: Did the "Bezier too big" stuff start when people upgraded their X server port, or when they upgraded their kernel? (I just started running -current on an x86 last week) I have a sneaking suspicion that the fp context is not being saved correctly, which is leading to the Bezier problem. 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?15778.55259.990703.531720>