Red Hat Bugzilla – Bug 475510
Abysmal Intel OpenGL performance
Last modified: 2009-03-16 17:31:05 EDT
Description of problem:
The performance of Compiz has hit rock bottom - with wobbly windows turned
on, dragging a window is sloooow, with the window lagging behind the mouse
pointer by a good few seconds. Turning wobbly windows off at least makes it
usable, but windows being dragged still lag behind the mouse quite a lot.
Also, Stellarium's performance (running without Compiz) is pretty abysmal,
giving me under 2 frames per second and causing the whole of X to run
cripplingly slowly. It doesn't seem to be using much CPU time so I guess it
hasn't done something crazy like rendering in software (and frankly I'd
expect software rendering to be faster than this anyway).
Since both Compiz and Stellarium are showing bad performance, I suspect a
GPU driver problem. There are a few errors reported in the Xorg log - not
sure if they are related:
(II) intel(0): Attempting memory allocation with tiled buffers.
(EE) intel(0): Failed to set tiling on front buffer: rejected by kernel
(EE) intel(0): Failed to set tiling on back buffer: rejected by kernel
(EE) intel(0): Failed to set tiling on depth buffer: rejected by kernel
(II) intel(0): Tiled allocation successful.
(II) intel(0): EDID for output TMDS-1
(II) intel(0): EDID for output TV
(EE) intel(0): underrun on pipe B!
(II) intel(0): EDID for output VGA
(II) intel(0): EDID for output LVDS
Version-Release number of selected component (if applicable):
Stuff that uses GL is pretty much unusable, whereas it was quite speedy under Fedora 8.
The machine is a Core 2 T5500
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
glxgears shows 319fps.
Probably the same bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/252094
You've unfortunately got a 945 with the nasty swizzling option turned on by the BIOS, which results in a performance penalty due to insufficient workarounds in software. If you short-circuit i915_gem_detect_bit_6_swizzle to return _NONE for both modes, that would answer whether that was the performance problem, at the expense of bad rendering.
If not, needs Xorg.0.log, dmesg, etc.
Ubuntu bug is unrelated -- they've got a bad collection of software.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf (if you have one) whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Well i have a
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)
Linux r2d2 22.214.171.124-170.2.5.fc10.x86_64 #1 SMP Wed Jan 21 01:33:24 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
I have no xorg.conf file and my Xorg.0.log is attached and my problems is pretty the same described by Steve. Now I have any performance issue with games as i used to have on fedora 10 development cycle, but now compositing is cripplingly slow with FPS at 1.
The only error i found on Xorg.0.log is
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) Unable to locate/open config file
(II) Loading extension MIT-SCREEN-SAVER
(EE) intel(0): underrun on pipe B!
I'm also attaching my dmesg output and any other information feel free to ask.
Created attachment 330260 [details]
Created attachment 330262 [details]
(In reply to comment #2)
> You've unfortunately got a 945 with the nasty swizzling option turned on by the
> BIOS, which results in a performance penalty due to insufficient workarounds in
> software. If you short-circuit i915_gem_detect_bit_6_swizzle to return _NONE
> for both modes, that would answer whether that was the performance problem, at
> the expense of bad rendering.
Can you be a bit more explicit on what need to be changed please?
Is 'i915_gem_detect_bit_6_swizzle' a routine?
From which package? Mesa? Kernel?
What line need to be patched to test it?
Care to provide a pseudo-patch?
I guess I understood what you meant. I wrote this quick'n'dirty patch on mesa:
@@ -98,7 +98,7 @@ intel_set_region_tiling_gem(struct intel
region->tiling = get_tiling.tiling_mode;
- region->bit_6_swizzle = get_tiling.swizzle_mode;
+ region->bit_6_swizzle = I915_BIT_6_SWIZZLE_NONE;
This solves Bug #479153 for me !!!!
No more display corruption in Blender icons!!!
My chipset is an Intel 865G.
Don't know if the behavior of my machine is related to this bug but i think it could be worth saying. When i activate compositing on kde 4.2 sometimes something start to suck my processor until everything stops working. Icons on desktop disappears, i can't start any new program, and commands on console return 'too many open files on system' error messages.
Checking /var/log/messages i found messages saying the same 'Feb 13 16:22:05 r2d2 kernel: VFS: file-max limit 101009 reached'. Every time this happened i was with compositing enabled. I never happened with compositing disabled, at least until now.
My video card is 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c).
My running kernel is Linux r2d2 126.96.36.199-170.2.5.fc10.i686 #1 SMP Wed Jan 21 02:09:37 EST 2009 i686 i686 i386 GNU/Linux.
My xorg driver is xorg-x11-drv-i810-2.5.0-4.fc10.i386.
I hope it can help.
Edney, thanks for the help but it would be probably really more profitable if we keep one bug per reporter. Can I ask you please to file your own bug (and refer to attachment 330262 [details] and attachment 330260 [details])?
Reporter, could we please get the requested information from you as well?
Thank you, both.
The information we've requested above is required in order
to review this problem report further and diagnose or fix the
issue if it is still present. Since it has been thirty days or
more since we first requested additional information, we're assuming
the problem is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "CLOSED: INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.
Fedora Bugzappers volunteer triage team