Hi, I'm seeing this on a i7 server with 32Gs of RAM as well. It runs raring. Should I post any info on this bug or do you want a separate bug ?
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/930007 Title: When booting with 32GB ram linux fails to find optimal mtrr when i915 (HD 3000) has 512 MB Ram Status in The Linux Kernel: Confirmed Status in “linux” package in Ubuntu: Incomplete Bug description: I have an ASUS P8Z68-V PRO, W/ BIOS 1101, 32GB of RAM and I am running Ubuntu precise 12.04. In the BIOS you can set the amount of memory for the "iGPU", the HD3000 GPU built into my i7-2600K. I just upgraded to 32GB of ram. Before the upgrade, I had this set to 512, had mtrr_spare_reg_nr=1 and everything worked fine. After the upgrade: mtrr_cleanup: can not find optimal value, please specify mtrr_gran_size/mtrr_chunk_size etc. No matter what I set mtrr_spare_reg_nr to I got this error. However, I found that if I turned the amount of memory for the iGPU down to 256, everything works again. The dmesg and other info for when the setting was at 512 can be found on the Post I made before i discovered that changing the iGPU to having 256mb would fix it at http://ubuntuforums.org/showthread.php?p=11677053 After changing iGPU to 256, here is the /proc/mttr /proc/mtrr reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back reg02: base=0x0bf800000 ( 3064MB), size= 8MB, count=1: uncachable reg03: base=0x100000000 ( 4096MB), size= 4096MB, count=1: write-back reg04: base=0x200000000 ( 8192MB), size= 8192MB, count=1: write-back reg05: base=0x400000000 (16384MB), size=16384MB, count=1: write-back reg06: base=0x800000000 (32768MB), size= 512MB, count=1: write-back reg07: base=0x820000000 (33280MB), size= 256MB, count=1: write-back reg08: base=0x82fe00000 (33534MB), size= 2MB, count=1: uncachable reg09: base=0x0d0000000 ( 3328MB), size= 256MB, count=1: write-combining and the dmesg is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/930007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp