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 1Ol8BM-0004s1-5y for garchives@archives.gentoo.org; Mon, 16 Aug 2010 22:29:28 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2DFF2E0946; Mon, 16 Aug 2010 22:28:50 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 0B8F8E0946 for ; Mon, 16 Aug 2010 22:28:50 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 97E441B40F2 for ; Mon, 16 Aug 2010 22:28:49 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -2.912 X-Spam-Level: X-Spam-Status: No, score=-2.912 required=5.5 tests=[AWL=-0.313, BAYES_00=-2.599] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VJWqvGJlM-ml for ; Mon, 16 Aug 2010 22:28:43 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by smtp.gentoo.org (Postfix) with ESMTP id D39E41B4067 for ; Mon, 16 Aug 2010 22:28:41 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Ol8AT-0005OH-DD for gentoo-user@gentoo.org; Tue, 17 Aug 2010 00:28:33 +0200 Received: from adsl-69-234-211-239.dsl.irvnca.pacbell.net ([69.234.211.239]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 17 Aug 2010 00:28:33 +0200 Received: from w41ter by adsl-69-234-211-239.dsl.irvnca.pacbell.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 17 Aug 2010 00:28:33 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: walt Subject: [gentoo-user] Re: dmesg warning about mtrr: type mismatch and allocation failed Date: Mon, 16 Aug 2010 15:28:21 -0700 Message-ID: References: <20100815232718.GA3864@waltdnes.org> 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 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: adsl-69-234-211-239.dsl.irvnca.pacbell.net User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b4pre) Gecko/20100816 Shredder/3.2a1pre In-Reply-To: <20100815232718.GA3864@waltdnes.org> X-Archives-Salt: 8a7f3e67-d554-4796-b2cf-d1657d76e3ac X-Archives-Hash: b4155cc101145ae033ee8f9e3bf06330 On 08/15/2010 04:27 PM, Walter Dnes wrote: > I'm running 64-bit Gentoo on an Intel 4-core i3 with an Intel integrated > graphics controller. An excerpt from dmesg follows, with the video- > related stuff. Note the two lines that I've split off. They mention > the mtrr type mismatch and the allocation failure. Is this a problem > and if so, what do I do about it? > > [ 0.519939] Linux agpgart interface v0.103 > [ 0.520016] agpgart-intel 0000:00:00.0: Intel HD Graphics Chipset > [ 0.520842] agpgart-intel 0000:00:00.0: detected 131068K stolen memory > [ 0.580462] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000 Does your BIOS let you set the AGP aperture manually? Couldn't hurt to make it bigger if you're able. The comment about 'stolen memory' sounds a bit evil ;) > [ 0.608643] mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining > [ 0.608725] [drm] MTRR allocation failed. Graphics performance may suffer. Do you have MTRR support in your linux kernel? It was selected automatically in my SMP kernel config, so I didn't have a choice. > [ 0.946741] Console: switching to colour frame buffer device 240x75 > [ 0.952156] fb0: inteldrmfb frame buffer device I'm wondering if console framebuffer support is really necessary for Intel graphics chips, I dunno. You could try disabling it in your kernel config to see if it make any difference. I'm assuming that all of the dmesg stuff came from boot time, right? Does your /var/cache/Xorg.0.log have any suspicious messages? I'm assuming your X works correctly? Or not.