Date: Tue, 20 May 2003 16:47:36 -0500 From: Glenn Johnson <gjohnson@srrc.ars.usda.gov> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: current@freebsd.org Subject: Re: XFree86 process gets stuck in *Giant Message-ID: <20030520214736.GA9756@node1.cluster.srrc.usda.gov> In-Reply-To: <20030520183041.GA79086@troutmask.apl.washington.edu> References: <20030520180258.GA2768@node1.cluster.srrc.usda.gov> <20030520183041.GA79086@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 20, 2003 at 11:30:41AM -0700, Steve Kargl wrote: > 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. I am using the 4BSD scheduler. By the way, the machine is a dual AthlonMP-2400+ with a Matrox 550 graphics card (DRI enabled). This behavior happened most recently with a -CURRENT from May 16, 2003. I put FreeBSD-5 on this machine back in March. This "event" has happened twice in two months so it is relatively rare. -- Glenn Johnson USDA, ARS, SRRC Phone: (504) 286-4252 New Orleans, LA 70124 e-mail: gjohnson@srrc.ars.usda.gov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030520214736.GA9756>