From owner-freebsd-current@FreeBSD.ORG Tue May 20 11:30:42 2003 Return-Path: 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 18CF837B401 for ; Tue, 20 May 2003 11:30:42 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D2EB43F3F for ; Tue, 20 May 2003 11:30:41 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) h4KIUfPR079467 for ; Tue, 20 May 2003 11:30:41 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)h4KIUfkc079466 for current@freebsd.org; Tue, 20 May 2003 11:30:41 -0700 (PDT) Date: Tue, 20 May 2003 11:30:41 -0700 From: Steve Kargl To: current@freebsd.org Message-ID: <20030520183041.GA79086@troutmask.apl.washington.edu> References: <20030520180258.GA2768@node1.cluster.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030520180258.GA2768@node1.cluster.srrc.usda.gov> User-Agent: Mutt/1.4i Subject: Re: XFree86 process gets stuck in *Giant X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2003 18:30:42 -0000 On Tue, May 20, 2003 at 01:02:59PM -0500, Glenn Johnson wrote: > I have had this happen a couple of times since running -CURRENT (since > about the days of 5.0-RELEASE). My machine (an SMP box) will be > non-responsive, no graphics, no ability to use the mouse or keyboard. > Upon logging into another machine and using ssh to connect to the hung > machine, I can login to it, albeit very slowly. Upon running 'top' I > see that the XFree86 process is stuck in *Giant and using > 100% of the > CPU (according to top). > > The only way out is a reboot because if I kill the XFree86 process the > machine will completely die. Has anyone else seen this? Is there > something I can do to prevent it from happening? > Which scheduler are you using? ULE (supposely) has issues with SMP. -- Steve