Bug 21136

Summary: OpenGL drawing errors and lockups
Product: DRI Reporter: Sam Morris <sam>
Component: DRM/IntelAssignee: Eric Anholt <eric>
Status: CLOSED FIXED QA Contact: Xorg Project Team <xorg-team>
Severity: critical    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522054
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
blender screenshot
none
celestia screenshot none

Description Sam Morris 2009-04-12 11:05:57 UTC
Forwarded from <http://bugs.debian.org/522054>

Since upgrading to intel 2.6.1 and drm 2.4.5, 3d acceleration has not been working very well on my Samsung Q45 (laptop).

glxgears runs ok (phew!) but Blender no longer redraws its screen, celestia uses very low resolution textures and a program I am developing where I work causes the whole system to freeze (unfortunately I don't have a minimum test case for that last one yet).

This happens with both Linux 2.6.26 and 2.6.29. If I downgrade libdrm2 and libdrm-intel1 to version 2.4.4+git+20090205
+8b88036-1 then things work OK again.
Comment 1 Sam Morris 2009-04-12 11:06:32 UTC
Created attachment 24730 [details]
blender screenshot
Comment 2 Sam Morris 2009-04-12 11:08:47 UTC
Created attachment 24731 [details]
celestia screenshot
Comment 3 Sam Morris 2009-04-27 04:39:20 UTC
Still present in 2.7.0 with drm DRM 2.4.9. Additionally, celestia is now very very slow. As in, 1 FPS slow.
Comment 4 Sam Morris 2009-04-27 04:40:33 UTC
Actually, I just looked at the clock, and it only updates once every three seconds!
Comment 5 Sam Morris 2009-09-23 06:38:55 UTC
I'm now using Xorg 1.6.3 with intel 2.8.1 and drm 2.4.13. Blender is fine. Celestia is still very, very slow however. In the order of several seconds per frame.
Comment 6 Sam Morris 2010-01-12 06:06:13 UTC
Rendering is better with xserver 1.6.5, intel 2.9.1, drm 2.4.15 and 2.6.32.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.