When booting with 32GB ram linux fails to find optimal mtrr when i915 (HD 3000) has 512 MB Ram
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Confirmed
|
Low
|
|||
linux (Ubuntu) |
Incomplete
|
Medium
|
Unassigned |
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_
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://
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.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | removed: needs-upstream-testing |
tags: | added: kernel-bug-exists-upstream |
tags: | removed: kernel-request-3.2.0-15.24 |
Changed in linux: | |
importance: | Unknown → Low |
status: | Unknown → Confirmed |
Do you know if this issue happened in previous version of Ubuntu, or is this a new issue?
Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text.
If this bug is fixed by the mainline kernel, please add the following tag 'kernel- fixed-upstream- KERNEL- VERSION' . For example, if kernel version 3.3-rc2 fixed the issue, the tag would be: 'kernel- fixed-upstream- v3.3-rc2' .
If the mainline kernel does not fix this bug, please add the tag: 'kernel- bug-exists- upstream' .
If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel- unable- to-test- upstream' .
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".
Thanks in advance.
[1] http:// kernel. ubuntu. com/~kernel- ppa/mainline/ v3.3-rc2- precise/