Bug 22921 - [i945GM] Screen goes wild when doing simple 3D work
Summary: [i945GM] Screen goes wild when doing simple 3D work
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: Jesse Barnes
QA Contact: Xorg Project Team
URL: https://bugs.edge.launchpad.net/xserv...
Keywords: NEEDINFO
: 22983 22987 (view as bug list)
Depends on:
Reported: 2009-07-23 18:59 UTC by Bryce Harrington
Modified: 2009-10-26 09:09 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

XorgLog.txt (65.77 KB, text/plain)
2009-07-23 18:59 UTC, Bryce Harrington
no flags Details
increase assumed display fetch latency (533 bytes, patch)
2009-08-31 09:37 UTC, Jesse Barnes
no flags Details | Splinter Review

Description Bryce Harrington 2009-07-23 18:59:39 UTC
Created attachment 27963 [details]

I've seen this with compiz on and off. With compiz _on_ I get wild screen corruption when doing anything like flipping workspaces. With compiz _off_ the same effect happens when running a simple python opengl program. Will attach a video taken with my phone mp4 format, hope you can play it because the ogv version made using ffmpeg2theora is vastly accelerated frame rate, but does show the issue. Also will attach the python code which causes the issue.

ProblemType: Bug
Architecture: i386
Date: Thu Jul 23 15:13:16 2009
DistroRelease: Ubuntu 9.10
MachineType: TOSHIBA Portable PC
Package: xserver-xorg-video-intel 2:2.8.0-0ubuntu1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-3-generic root=UUID=0534c5bb-a9db-4db7-972d-43fb11be0f54 ro quiet splash
 PATH=(custom, user)
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.5-1ubuntu1
 libdrm2 2.4.11-1ubuntu1
 xserver-xorg-video-intel 2:2.8.0-0ubuntu1
 xserver-xorg-video-ati N/A
SourcePackage: xserver-xorg-video-intel
Uname: Linux 2.6.31-3-generic i686
dmi.bios.date: 05/22/2008
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 3.80
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.80:bd05/22/2008:svnTOSHIBA:pnPortablePC:pvrVersion1.0:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: Portable PC
dmi.product.version: Version 1.0
dmi.sys.vendor: TOSHIBA
fglrx: Not loaded
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-3-generic

00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
	Subsystem: Toshiba America Info Systems Device [1179:0001]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
	Subsystem: Toshiba America Info Systems Device [1179:0001]
Comment 2 Gordon Jin 2009-07-27 23:41:09 UTC
*** Bug 22987 has been marked as a duplicate of this bug. ***
Comment 3 Eric Anholt 2009-08-03 10:02:50 UTC
Looks like fifo issues to me.  You might want to try with current drm-intel-next, which has some fifo fixes.
Comment 4 Jesse Barnes 2009-08-07 14:01:47 UTC
Yep, looks like FIFO underruns to me too...  Fixes are in Eric's tree queued for 2.6.31.
Comment 5 Jesse Barnes 2009-08-31 09:37:17 UTC
Created attachment 29042 [details] [review]
increase assumed display fetch latency

Assuming the latest kernel bits don't fix this bug, this patch should.
Comment 6 Jesse Barnes 2009-08-31 11:34:35 UTC
*** Bug 22983 has been marked as a duplicate of this bug. ***
Comment 7 Jesse Barnes 2009-09-11 14:44:19 UTC
Fix in 2.6.31:

commit bcc24fb42585dc9f490cf7789a917358414bdab5
Author: Jesse Barnes <jbarnes@virtuousgeek.org>
Date:   Mon Aug 31 10:24:31 2009 -0700

    drm/i915: increase default latency constant (v2 w/comment)
Comment 8 Jesse Barnes 2009-10-26 09:09:01 UTC
*** Bug 22983 has been marked as a duplicate of this bug. ***

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.