Date: Tue, 08 Oct 2002 19:33:58 +0300 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: freebsd-current@FreeBSD.org Subject: Re: sorry state of Xserver in 5.0 Message-ID: <3DA308F6.8D87BF0@FreeBSD.org> References: <15777.52918.689192.919124@grasshopper.cs.duke.edu> <20021008064433.GA77334@vega.vega.com> <15778.55259.990703.531720@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Gallatin wrote: > > 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. Backing out 1.540 and 1.541 didn't solve the problem with SIGFPE for me, so that the problem is probably elsewhere. :( -Maxim > > 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?3DA308F6.8D87BF0>