Bug 115543

Summary:	gl-117 game locks up system tighter than a tick
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Thomas Horsley <tom.horsley>
Component:	X.Org	Assignee:	Stefan Dirsch <sndirsch>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Minor
Priority:	P5 - None	CC:	asklein, vetter
Version:	Beta 4
Target Milestone:	---
Hardware:	i586
OS:	SUSE Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	The /etc/X11/xorg.conf file The output from running glxinfo Xorg.0.log file from the crash session /var/log/messages from around the time of system freeze

Description Thomas Horsley 2005-09-07 01:06:25 UTC

Just for grins I was fooling around with games on my suse 10.0 beta4 system,
and the gl-117 air combat game starts up OK and does its calibration, then
when it is through with that, as soon as I move the cursor over one
of the "buttons" on the screen, my system freezes up solid, only the reset
button can recover.

The open GL chess interface also seems to have problems, but it doesn't
freeze the system, it merely dies as soon as I try to start a game.

I don't consider these problems, since I'm not actually interested in running
any open GL stuff, but I thought someone might like to know.

Possibly relevant information:

The is an old 850MHZ PIII system with a cheap (but fairly new) ATI 9200
agp graphics card running at 1280x768 resolution on a widescreen format
LCD display. The motherboard is an old abit BE6 II motherboard with a 440 BX
chipset.

Comment 1 Martin Lasarsch 2005-09-07 09:20:30 UTC

*** Bug 115542 has been marked as a duplicate of this bug. ***

Comment 2 Stefan Dirsch 2005-09-07 10:17:48 UTC

Probably it's a DRI driver problem. Please attach /etc/X11/xorg.conf,
/var/log/Xorg.0.log and the output of "glxinfo". Thanks.

Comment 3 Thomas Horsley 2005-09-07 21:32:31 UTC

Created attachment 49120 [details]
The /etc/X11/xorg.conf file

Comment 4 Thomas Horsley 2005-09-07 21:33:09 UTC

Created attachment 49121 [details]
The output from running glxinfo

Comment 5 Thomas Horsley 2005-09-07 21:56:42 UTC

Created attachment 49125 [details]
Xorg.0.log file from the crash session

I renamed the log files to get a nice fresh one, ran
the gl-117 program till the system freeze, hit the
reset button, booted "safe" mode, copied the Xorg.0.log
file, then booted again normally. This is that copy, so
it should be as much of the log as made it to disk
before the system froze up.

Comment 6 Stefan Dirsch 2005-09-07 22:04:44 UTC

Thanks. Unfortunately I can't find anything in the X.Org logfile. Maybe we'll 
find sth. in the kernel logfile "/var/log/messages" related to the crash.

Comment 7 Thomas Horsley 2005-09-08 02:01:21 UTC

Created attachment 49140 [details]
/var/log/messages from around the time of system freeze

Here is the /var/log/message file, starting from the
clean boot I did just before running gl-117 and going
through the reboot to safe mode after the system freeze.
The only suspicious thing I see is a message about
modprobe failure on sonypi that may have happened
right around the time of the system freeze.

It probably isn't too significant though, because I
see the same message on subsequent boots as well
when I've had no opengl usage or crashes.

Comment 8 Stefan Dirsch 2005-09-08 02:24:48 UTC

There's nothing suspicious in this file. Looks like the system freezes 
silently. :-(

Comment 9 Stefan Dirsch 2005-09-08 02:30:25 UTC

As "workaround" for now you could try to get the ATI "fglrx" driver working. 
   
http://www.novell.com/products/linuxprofessional/downloads/x11/index.html 
ftp://ftp.suse.com/pub/suse/i386/supplementary/X/ATI/ati-installer-HOWTO.html

Comment 10 Stefan Dirsch 2005-12-14 09:11:34 UTC

I set this to Minor since gl-117 is no longer in our default selection. It has been replaced by xmoto.

Comment 11 Stefan Dirsch 2006-03-18 22:48:10 UTC

Could you test with 10.1 again? Thanks.

Comment 12 Stefan Dirsch 2006-05-23 21:24:54 UTC

Any news on this one?

Comment 13 Stefan Dirsch 2006-06-15 08:21:04 UTC

Since there is no feedback available, let's assume this has been fixed with the new radeon driver in SUSE 10.1. Feel free to reopen, if it isn't.