From owner-freebsd-questions@FreeBSD.ORG Wed Oct 10 12:16:15 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F75616A419; Wed, 10 Oct 2007 12:16:15 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from snoogles.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id DB48D13C448; Wed, 10 Oct 2007 12:16:14 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (localhost [127.0.0.1]) by snoogles.rachie.is-a-geek.net (Postfix) with ESMTP id C99481CDFC; Wed, 10 Oct 2007 04:16:13 -0800 (AKDT) From: Mel To: freebsd-questions@freebsd.org Date: Wed, 10 Oct 2007 14:15:54 +0200 User-Agent: KMail/1.9.7 References: <639B1B9B25D010433F197CCD@paul-schmehls-powerbook59.local> In-Reply-To: <639B1B9B25D010433F197CCD@paul-schmehls-powerbook59.local> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710101415.57163.fbsd.questions@rachie.is-a-geek.net> Cc: Paul Schmehl , questions@freebsd.org Subject: Re: X (xorg 7.3) consumes all the CPU X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Oct 2007 12:16:15 -0000 On Wednesday 10 October 2007 05:01:50 Paul Schmehl wrote: > Is there a way to start a process so that memory and CPU usage can be > tracked closely enough to determine what the cause of 100% CPU use would > be? I've got a box, recently installed 6.2 RELEASE with xorg 7.3 > installed, and when X is started, CPU goes to 100% and stays there. > > Here's the bad machine > 1510 pauls 1 0 0 277M 7076K rdnrel 0 13:41 100.05% Xorg To shoot the obvious: it's not running as root here. No idea what rdnrel is for CPU state. ktrace(1) should show what it's doing. If that's not enough info, you could always attach gdb to it. -- Mel