From owner-freebsd-current Sat Oct 19 14:44: 2 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 DE08037B401 for ; Sat, 19 Oct 2002 14:44:00 -0700 (PDT) Received: from haystack.lclark.edu (haystack.lclark.edu [149.175.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDD6843E91 for ; Sat, 19 Oct 2002 14:43:55 -0700 (PDT) (envelope-from eta@lclark.edu) Received: from copeland-30-191.lclark.edu (anholt@copeland-30-191.lclark.edu [149.175.30.191]) by haystack.lclark.edu (8.9.3/8.9.3) with ESMTP id OAA22712; Sat, 19 Oct 2002 14:43:24 -0700 (PDT) Subject: Re: sorry state of Xserver in 5.0 From: Eric Anholt To: Andrew Gallatin Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <15777.52918.689192.919124@grasshopper.cs.duke.edu> References: <15777.52918.689192.919124@grasshopper.cs.duke.edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 19 Oct 2002 14:43:24 -0700 Message-Id: <1035063805.890.80.camel@anholt.dyndns.org> Mime-Version: 1.0 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, 2002-10-07 at 11:13, 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 > > 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. Basically what this ktrace output means, from my reading, is that the server is stuck processing some client request and never gets back to it main scheduling loop / goes idle and turns off the alarm. Finding where the server is sitting would be valuable. If you have a hardware cursor and smooth mouse on (it's default) you'll still be able to move the mouse because the mouse response is done in a signal handler, so a busy server doesn't make your mouse stop working. Still wishing I could get a working gdb on an X. -- Eric Anholt http://people.freebsd.org/~anholt/dri/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message