Bug 23104 - [R300] Xserver crashes enabling visual effects
Summary: [R300] Xserver crashes enabling visual effects
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: 7.4 (2008.09)
Hardware: All Linux (All)
: high major
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-03 03:57 UTC by Bryce Harrington
Modified: 2009-09-01 02:25 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
gdb.txt (31.10 KB, text/plain)
2009-08-03 03:57 UTC, Bryce Harrington
no flags Details
dmesg (123.11 KB, text/plain)
2009-08-03 03:58 UTC, Bryce Harrington
no flags Details
XorgLogOld.txt (81.03 KB, text/plain)
2009-08-03 03:59 UTC, Bryce Harrington
no flags Details
XorgLog.txt (73.74 KB, text/plain)
2009-08-03 03:59 UTC, Bryce Harrington
no flags Details
glxinfo.txt (6.40 KB, text/plain)
2009-08-03 03:59 UTC, Bryce Harrington
no flags Details

Description Bryce Harrington 2009-08-03 03:57:28 UTC
The xserver crashes when enabling visual effects.

To reproduce:
1. Log into GDM
2. System>Preferences>Appearance>Visual Effects>Normal
Detecting driver dialog shows, "Unable to enable effects" dialog shows a slit second before returning to GDM login.

Note can enable visual effects by running "compiz --replace" from the command-line. X crashes when quitting compiz in this case.

ProblemType: Bug
Architecture: i386
Date: Mon Aug 3 10:55:51 2009
DistroRelease: Ubuntu 9.10
MachineType: Dell Inc. Inspiron 6000
Package: xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu4
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-4-generic root=UUID=f330234e-6a21-4d7e-9fff-33d5411efe54 ro quiet splash
ProcEnviron:
 LANGUAGE=en_NZ.UTF-8
 PATH=(custom, no user)
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.5-1ubuntu1
 libdrm2 2.4.12-1ubuntu1
 xserver-xorg-video-intel 2:2.8.0-0ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu4
SourcePackage: xserver-xorg-video-ati
Uname: Linux 2.6.31-4-generic i686
dmi.bios.date: 07/22/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 0X9238
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/22/2005:svnDellInc.:pnInspiron6000:pvr:rvnDellInc.:rn0X9238:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 6000
dmi.sys.vendor: Dell Inc.
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-4-generic
Comment 1 Bryce Harrington 2009-08-03 03:57:57 UTC
Created attachment 28290 [details]
gdb.txt
Comment 2 Bryce Harrington 2009-08-03 03:58:26 UTC
Created attachment 28291 [details]
dmesg
Comment 3 Bryce Harrington 2009-08-03 03:59:00 UTC
Created attachment 28292 [details]
XorgLogOld.txt
Comment 4 Bryce Harrington 2009-08-03 03:59:17 UTC
Created attachment 28293 [details]
XorgLog.txt
Comment 5 Bryce Harrington 2009-08-03 03:59:42 UTC
Created attachment 28294 [details]
glxinfo.txt
Comment 6 Bryce Harrington 2009-08-03 04:02:58 UTC
The above Ubuntu bug is being forwarded from Robert Ancell, who maintains compiz for Ubuntu.

00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03)
	Subsystem: Dell Device [1028:0188]
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M22 [Mobility Radeon X300] [1002:5460]
	Subsystem: Dell Device [1028:2003]

Comment 7 Michel Dänzer 2009-08-03 04:12:06 UTC
That compiz doesn't start in the first place is probably a compiz wrapper script failure.

The crash on compiz exit should be fixed by xserver commits 2075d4bf9e53b8baef0b919da6c44771220cd4a5 and 3020b1d43e34fca08cd51f7c7c8ed51497d49ef3 .
Comment 8 Robert Ancell 2009-08-03 07:42:23 UTC
The patches fix the problem for me, thanks.
Comment 9 Michel Dänzer 2009-09-01 02:25:48 UTC
Fixed in xserver 1.6.3.901.


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.