From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OE1TL-0007Ik-AA for garchives@archives.gentoo.org; Mon, 17 May 2010 14:39:11 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 054A8E070D; Mon, 17 May 2010 14:38:32 +0000 (UTC) Received: from mail.oversi.com (oversrv1.oversi.com [209.88.189.2]) by pigeon.gentoo.org (Postfix) with ESMTP id C2D1DE070D for ; Mon, 17 May 2010 14:38:31 +0000 (UTC) Received: from [10.2.2.28] (unknown [10.2.2.28]) by mail.oversi.com (Postfix) with ESMTPA id 015F75DAC67 for ; Mon, 17 May 2010 17:38:31 +0300 (IDT) Message-ID: <4BF154E6.3000407@oversi.com> Date: Mon, 17 May 2010 17:38:30 +0300 From: Amit Dor-Shifer User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: X hoggs CPU (xorg-server-1.7.6) References: <4BEA9E3B.7050809@oversi.com> <4BEBD2D3.1060800@oversi.com> <4BEFA8DF.2000608@oversi.com> <4BF0E565.9080700@oversi.com> In-Reply-To: <4BF0E565.9080700@oversi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 6bd685a1-810f-4927-a46d-e8f41f532038 X-Archives-Hash: 8f06f5fae2e7c3f4d0bb0a269a2cc826 On 05/17/10 09:42, Amit Dor-Shifer wrote: > Well, I'm less inclined to think now that X is responsible for the > high CPU load. I wasn't too knowledgeable about the relationships > between X and its clients when I made my initial assumption. It was > more like "I startx + I move mouse + CPU shoots-up => it's X". > > Looks more like kde is rocking my CPU. Indeed, xev doesn't print > anything while I'm generating high CPU with mouse movements. Also, I > had a notion twm didn't exhibit the phenomenon as long as I didn't > execute any kde apps. But I'm not 100% sure about the latter experiment. > > I'm runing KDE 3.5.10. > > Amit a. I had the "nv" driver instead of the "nvidia" driver loaded. b. openGL was assigned to xorg. 'eselect opengl set' to nvidia fixed that. X still goes as high as 30%. Still looks suspicious, but more acceptable. Amit