Kernel Bug Tracker – Bug 12950
[i915] allocate MCHBAR space & enable if necessary
Last modified: 2010-09-03 08:54:33 UTC
Fixes tiling issues and slowdown on i915 chipsets.
Created attachment 20698 [details]
allocate MCHBAR space & enable if necessary
Read this thread for more info:
IMHO this bug should be list as a regression from 2.7.27.X
My test case is a program called stellarium (www.stellarium.org). With 2.6.27.X I get about 15/20 fps and the software in perfectly usable. With 2.6.29 performance drops down to less than 3 fps.
The patch doesn't help for me; I mean the error is gone but the performance remains exactly the same.
The system is an eeePC 900, more details on request.
Made it block bug #11808 on the basis of comment #3.
FWIW, replacing the drivers/gpu/drm and the include/linux/drm with the ones from 2.6.27.X and fixing a trivial (I hope!) compilation problem, I got 20fps with 2.6.29 .
This was, obviously, without userspace changes.
For the record, this patch causes a regression at least on the i945GM, it freezes a few minutes after suspend. See https://bugs.freedesktop.org/show_bug.cgi?id=20520 for details.
Performance regression still present in 2.6.30-rc1
OK, it seems there's no activity on this one.
Anyway, I managed to "solve" it by upgrading my distro's X.org from 1.5.2 to 1.6.1, which comes with intel driver v. 2.7.0 .
This, combined with the i915 patch attached to this bug, even gives some performance improvement compared to 2.6.27.x with X.org v1.5.2 .
This is true for both kernel 220.127.116.11 and 2.6.30-rc3 (modulo that on this one the patch does not apply cleanly but needs a modification in a comment line).
By the way, my distro is OpenSuse 11.1, so not really an obsolete one. The new userspace is from the official X.org repository.
Maybe the kernel devs should have stated more clearly that if you want to run 3D apps with Intel chipset a new X.org is needed.
One last detail: 2.6.30-rc3 without the MCHBAR patch crashes running glxgears (powercycle needed). Another _BAD_ regression, at least compared to 2.6.27.x (didn't try 18.104.22.168 without the patch).
i've added some intel gfx cc's (i hope the right ones)...
do you still need to patch the kernel to avoid a crash? if so, do you have some backtraces?
Well, since then (more than one year), I changed distibution, three xorg versions and 7 kernel versions.
This patch is not necessary anymore.
Good to hear.