mtrr allocation failed. Graphics performance may suffer. Intel hd2000 iGPU
Hi slackers.
Recently, during the boot time I've noticed the warning: "mtrr allocation failed, graphics performance may suffer". I was wondering if this is a serious problem? I've noticed that sometimes, during the HD video playback image would become choppy here and there, every now and then... Could the mtrr failed allocation cause that? Here is the output of cat /proc/mtrr: Code:
$ cat /proc/mtrr Cheers! ;) |
I have this issue with intel sandy bridge with 13.37 and 14 as well. I have no solution, just wanted to let you know your not alone on this.
|
Looks like the problem is present for a long time now:
-RedHat bug report, -possible workaround (I haven't test it yet). There was a post on a RedHat bug report which says that problems (in Fedora Core 17) disappeared after upgrading the kernel to version 3.4.0. Too bad Pat didn't include 3.4 kernel to Slackware 14.0. Old Fogie, thank you for your feedback... I'm sorry to hear you have the same problems... If I find a solution I will post it here. If someone already knows the solution to the problem please provide it, it will be much appreciated! Adding enable_mtrr_cleanup mtrr_spare_reg_nr=1 to kernel parameters didn't work for me. Thank you! Best regards. |
Try the workaround, but also look in 'dmesg' for the full output, to see if there are any free registers. Of course, you can also compile your own kernel if you say it will fix it. Use the config file in /testing directory plus one of these guides to compile a new kernel:
http://docs.slackware.com/howtos:sla...git_repository http://docs.slackware.com/howtos:sla...kernelbuilding I know many people are afraid of it, but it can not only boost performance and stability, but also solve problems. |
H_TeXMeX_H thank you for your suggestions and for the links... I did try the workaround but no success. mtrr values were the same and the dmesg part for the mtrr was the same:
Code:
# dmesg | grep -i mtrr Your help is appreciated! Best regards. |
I'm running kernel 3.4.X series kernel since it was released. In fact I get this on all kernels 3.2.X thru 3.6.X. But I've settled in on 3.4.X as it's the only Linux kernel that seems to work right with my hardware. I hope it's supported for a while :) On all of the above mentioned kernels, I have DRM working, the 3d performance seems to work fine even though I get this message. I had googled it for a while and turned the music up and hoped it would go away ( a car analogy :) ). I'm not sure what they mean/say/recommend on that LKML post or if it is applicable to me or not. ZOK4 I'm interested as well as to your results with a 3.4 kernel as well.
|
Just an update of the situation... This weekend I had some spare time so I decided to take the challenge and try to compile my very first Lnux kernel. First time I did it i got kernel panic. So after few minutes of going trough my .config file I found out that I didn't check the ext4 file system for compilation (so stupid of me). Yesterday I tried again, and this time everything was fine. No mtrr allocation failed error on the boot. But system hangs when entering runlevel 4 (it can not go to x session). I'm not sure what I did wrong...
The /proc/mtrr file is the same as before: Code:
$ cat /proc/mtrr Code:
# dmesg | grep -i mtrr 1) Problem is solved 2) I did something wrong in the .config file and the driver doesn't load (thus causing the system hang on entering runlevel 4) - this one is more likely :banghead: If I manage to figure out what was my mistake I'll let you know. Best regards! ;) |
On my system:
Code:
bash-4.2$ cat /proc/mtrr Code:
MTRR default type: uncachable |
Hi! Here is the requested part of the dmesg for the default 3.2.29 kernel:
Code:
[ 0.000000] MTRR default type: uncachable dmesg for 3.5.4 kernel (which I compiled without i915 module :redface: ): Code:
[ 0.000000] MTRR default type: uncachable I hope third time Linux kernel compilation will be the charmed one :D Best regards! |
You should set:
MTRR cleanup enable value = 1 MTRR cleanup spare reg num = 1 Maybe it will help. |
Quote:
|
Yes, but do it through one of the make options, don't edit the config yourself.
|
All times are GMT -5. The time now is 08:47 PM. |