Date: Tue, 8 Oct 2002 09:44:33 +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: <20021008064433.GA77334@vega.vega.com> In-Reply-To: <15777.52918.689192.919124@grasshopper.cs.duke.edu> References: <15777.52918.689192.919124@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 07, 2002 at 02:13:10PM -0400, Andrew Gallatin wrote: > > Every so often, my X server locks up. It seems to be in a tight > loop, 95% user time, and making only these ktrace'able calls: > > 27069 XFree86 0.019988 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 > 27069 XFree86 0.000039 CALL sigreturn(0xbd9e7b0c) > 27069 XFree86 0.000004 RET sigreturn JUSTRETURN > 27069 XFree86 0.019951 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 > 27069 XFree86 0.000015 CALL sigreturn(0xbd9e6e0c) > 27069 XFree86 0.000004 RET sigreturn JUSTRETURN > 27069 XFree86 0.019980 PSIG SIGALRM caught handler=0x80d219c mask=0x0 code=0x0 I'm experiencing this too. > Anybody have a workaround for this? > > The whole system (2.53 Ghz P4) was compiled from sources late last > week... > > 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. -Maxim 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?20021008064433.GA77334>