From owner-freebsd-current Mon Oct 7 23:44:59 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 339E537B401 for ; Mon, 7 Oct 2002 23:44:58 -0700 (PDT) Received: from baraca.united.net.ua (ns.united.net.ua [193.111.8.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8425743EA3 for ; Mon, 7 Oct 2002 23:44:55 -0700 (PDT) (envelope-from max@vega.com) Received: from vega.vega.com (xDSL-2-2.united.net.ua [193.111.9.226]) by baraca.united.net.ua (8.11.6/8.11.6) with ESMTP id g986igB45666; Tue, 8 Oct 2002 09:44:44 +0300 (EEST) (envelope-from max@vega.com) Received: from vega.vega.com (max@localhost [127.0.0.1]) by vega.vega.com (8.12.6/8.12.5) with ESMTP id g986iZTs077352; Tue, 8 Oct 2002 09:44:35 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: (from max@localhost) by vega.vega.com (8.12.6/8.12.5/Submit) id g986iXAr077346; Tue, 8 Oct 2002 09:44:33 +0300 (EEST) Date: Tue, 8 Oct 2002 09:44:33 +0300 From: Maxim Sobolev To: Andrew Gallatin Cc: freebsd-current@FreeBSD.ORG Subject: Re: sorry state of Xserver in 5.0 Message-ID: <20021008064433.GA77334@vega.vega.com> References: <15777.52918.689192.919124@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <15777.52918.689192.919124@grasshopper.cs.duke.edu> User-Agent: Mutt/1.4i 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, 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