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 1Om3SC-0002IX-1v for garchives@archives.gentoo.org; Thu, 19 Aug 2010 11:38:40 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 84E96E0896; Thu, 19 Aug 2010 11:37:27 +0000 (UTC) Received: from ironport2-out.pppoe.ca (ironport2-out.teksavvy.com [206.248.154.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 772C2E0896 for ; Thu, 19 Aug 2010 11:37:27 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao4FAIezbExMCrW9/2dsb2JhbACTQY0acrwlhTcEhGaHfIQS X-IronPort-AV: E=Sophos;i="4.56,233,1280721600"; d="scan'208";a="72979495" Received: from 76-10-181-189.dsl.teksavvy.com (HELO waltdnes.org) ([76.10.181.189]) by ironport2-out.pppoe.ca with SMTP; 19 Aug 2010 07:37:26 -0400 Received: by waltdnes.org (sSMTP sendmail emulation); Thu, 19 Aug 2010 07:37:25 -0400 From: "Walter Dnes" Date: Thu, 19 Aug 2010 07:37:25 -0400 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] dmesg warning about mtrr: type mismatch and allocation failed Message-ID: <20100819113725.GA4894@waltdnes.org> 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=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Archives-Salt: 8eb7b132-7f93-42ab-8beb-d2f238a2f696 X-Archives-Hash: abe29aa785a0233fadd4b0a552f19f92 On Mon, Aug 16, 2010 at 05:55:04PM -0500, Paul Hartman wrote > > I had a similar message, it was there because of the fact that i > specified the wrong (or failed to specify?) mtrr method in my kernel > boot parameters for the framebuffer. I'm using uvesafb and in kernel > documentation (/usr/src/linux/Documentation/fb/uvesafb.txt) it > explains the values and even gives an example of this error and what > to do about it: I'm using the Intel driver, which doesn't have those settings. And no, I do not want to drop down to a generic VESA driver with no hardware acceleration. Some more Google searching has turned up a lead. Apparently, it's possible to manually set the mtrr's, using cat and echo with /proc/mtrr According to "lspci -v", my integrated graphics chip has Memory at fb800000 (64-bit, non-prefetchable) [size=4M] Memory at d0000000 (64-bit, prefetchable) [size=256M] My mtrr setup, however, shows up like so... waltdnes@i3 ~ $ cat /proc/mtrr reg00: base=0x000000000 ( 0MB), size= 8192MB, count=1: write-back reg01: base=0x200000000 ( 8192MB), size= 1024MB, count=1: write-back reg02: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable reg03: base=0x0b4000000 ( 2880MB), size= 64MB, count=1: uncachable reg04: base=0x0b8000000 ( 2944MB), size= 128MB, count=1: uncachable reg05: base=0x1fc000000 ( 8128MB), size= 64MB, count=1: uncachable I'll read up more on how to set it up manually. One thing that has my curiousity right now... how come there's a gig of ram in write-back mode *STARTING* at 8 gigs, and ending at 9 gigs minus 1 byte, when I only have 8 gigs of ram in total? -- Walter Dnes