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 1OmCj9-0004BK-3r for garchives@archives.gentoo.org; Thu, 19 Aug 2010 21:32:47 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0BAE5E07F6; Thu, 19 Aug 2010 21:32:31 +0000 (UTC) Received: from mail-ew0-f53.google.com (mail-ew0-f53.google.com [209.85.215.53]) by pigeon.gentoo.org (Postfix) with ESMTP id C16CDE07F6 for ; Thu, 19 Aug 2010 21:32:30 +0000 (UTC) Received: by ewy19 with SMTP id 19so1924210ewy.40 for ; Thu, 19 Aug 2010 14:32:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:reply-to:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=Lhh//vRkjyQxgfyUI33ZL+brikv5TuETJMWtwTTEgDY=; b=aDO+FxdFrhCfT+O4gOo7WMTDht937NjqC4s7N0Cqag8ZUWGMYElq0+4Ol8LJFtfD+p YoOpj8oq6G5lpzp/tj3BWXcXOXA3I4fzRTRwFm8IvkZ08pkuo4tbUki1nc+iMHISGlLk vTboMuclWAlFIklb0UTUnqOTnzOgZJo3eOIaA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=nLUsywU662ggLhadiioYklJQ9iVD520DRxpYUgblnxkUYEpIiPyet0igEFg3s3ka8m MfZ25AqvKSyNLdQmBnFJm5pZGgZaVrsKreaSkWBTSggWgfYllvIAcFioc1QdoXg+8Hfr Nin7WIDTI8hrszELDERxsM+DukSbW+Ef2SYRQ= Received: by 10.216.87.208 with SMTP id y58mr327541wee.82.1282253549777; Thu, 19 Aug 2010 14:32:29 -0700 (PDT) Received: from (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id w1sm1376365weq.1.2010.08.19.14.32.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 19 Aug 2010 14:32:28 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] dmesg warning about mtrr: type mismatch and allocation failed Date: Thu, 19 Aug 2010 22:32:17 +0100 User-Agent: KMail/1.13.5 (Linux/2.6.34-gentoo-r1; KDE/4.4.5; x86_64; ; ) References: <20100815232718.GA3864@waltdnes.org> <20100819113725.GA4894@waltdnes.org> <4C6D4412.6010800@gmail.com> In-Reply-To: <4C6D4412.6010800@gmail.com> 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: multipart/signed; boundary="nextPart3603567.KXpctERpYP"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201008192232.27024.michaelkintzios@gmail.com> X-Archives-Salt: a1e08f2c-194d-4880-9ad6-fb00536b1746 X-Archives-Hash: ce3ca52afc0297d74bae452751f4591d --nextPart3603567.KXpctERpYP Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Thursday 19 August 2010 15:47:46 Bill Longman wrote: > On 08/19/2010 04:37 AM, Walter Dnes wrote: > > On Mon, Aug 16, 2010 at 05:55:04PM -0500, Paul Hartman wrote > >=20 > >> 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 > >>=20 > >> to do about it: > > I'm using the Intel driver, which doesn't have those settings. And > >=20 > > 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 > >=20 > > According to "lspci -v", my integrated graphics chip has > > =20 > > Memory at fb800000 (64-bit, non-prefetchable) [size=3D4M] > > Memory at d0000000 (64-bit, prefetchable) [size=3D256M] > > =20 > > My mtrr setup, however, shows up like so... > >=20 > > waltdnes@i3 ~ $ cat /proc/mtrr > > reg00: base=3D0x000000000 ( 0MB), size=3D 8192MB, count=3D1: write-b= ack > > reg01: base=3D0x200000000 ( 8192MB), size=3D 1024MB, count=3D1: write-b= ack > > reg02: base=3D0x0c0000000 ( 3072MB), size=3D 1024MB, count=3D1: uncacha= ble > > reg03: base=3D0x0b4000000 ( 2880MB), size=3D 64MB, count=3D1: uncacha= ble > > reg04: base=3D0x0b8000000 ( 2944MB), size=3D 128MB, count=3D1: uncacha= ble > > reg05: base=3D0x1fc000000 ( 8128MB), size=3D 64MB, count=3D1: uncacha= ble > >=20 > > I'll read up more on how to set it up manually. One thing that has my > >=20 > > 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? >=20 > You might want to have a look in your kernel Documentation directory. > There's a file x86/mtrr.txt that gives you some info. And lots in the fb > subdirectory. You can probably find some other info there, too. There's > lots of the dreaded MTRR info in the kernel_parameters.txt file, so you > can setup the MTRRs at boot time. I've read as much as I could find, but the whole hexadecimal thing has me=20 overwhelmed O_O I think my mtrr is OK, but I do not understand this enough to know if it wo= uld=20 benefit from manual configuration. Walter please break it into small change for me when you sort out yours - y= ou=20 could contact me off list if this is getting too O/T. =2D-=20 Regards, Mick --nextPart3603567.KXpctERpYP Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iEYEABECAAYFAkxtousACgkQVTDTR3kpaLa/MQCeK3stKdbcJT9ALqucHB04xVFr BaIAoMMyUfwwQkWd57+uD9xmIn0Y2H1x =3Bn/ -----END PGP SIGNATURE----- --nextPart3603567.KXpctERpYP--