Bug 17610

Summary:	celestia 1.5.1 locks up the GPU as soon as it creates a dialog box.
Product:	DRI	Reporter:	Chris Rankin <rankincj>
Component:	DRM/other	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Chris Rankin 2008-09-16 12:02:25 UTC

I am running celestia 1.5.1 configured as:

configure --sysconfdir=/etc --with-gnome

The application runs fine until I create a dialog box from the menu bar, at which point the X server stops responding. (The mouse cursor still moves, you can't click on anything and the cursor icon doesn't change any more.) A reboot is then required.

The machine is a dual P4 Xeon with 2 GB of RAM with a Radeon 9550, running Fedora 9.

01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AS [Radeon 9550] (prog-if 00 [VGA controller])
	Subsystem: C.P. Technology Co. Ltd Unknown device 2084
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (2000ns min), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at e0000000 (32-bit, prefetchable) [size=256M]
	Region 1: I/O ports at ec00 [size=256]
	Region 2: Memory at ff8f0000 (32-bit, non-prefetchable) [size=64K]
	Expansion ROM at ff800000 [disabled] [size=128K]
	Capabilities: [58] AGP version 3.0
		Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8
		Command: RQ=32 ArqSz=2 Cal=0 SBA+ AGP+ GART64- 64bit- FW- Rate=x8
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

01:00.1 Display controller: ATI Technologies Inc RV350 AS [Radeon 9550] (Secondary)
	Subsystem: C.P. Technology Co. Ltd Unknown device 2085
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64 (2000ns min), Cache Line Size: 64 bytes
	Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M]
	Region 1: Memory at ff8e0000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-

Comment 1 Michel Dänzer 2008-09-17 00:15:59 UTC

Please try a current drm Git snapshot. There was a bug in the handling of many cliprects which could result in lockups.

Comment 2 Chris Rankin 2008-09-17 03:46:06 UTC

(In reply to comment #1)
> Please try a current drm Git snapshot. There was a bug in the handling of many
> cliprects which could result in lockups.

The latest drm from git gives this warning (2.6.26.4 kernel):

WARNING: modpost: module drm.ko uses symbol 'init_mm' marked UNUSED

I thought the init_mm symbol had been deprecated?

Anyway - using these new kernel modules with my 2.6.26.4 kernel does indeed solve the "dialog box lockup" problem. However, the GPU then locked up during my "Earth to Titan" test. (Start at Earth, select Titan as a destination and press "G"), although bug #13258 does suggest that R300 vertex handling is completely borked so maybe that's no surprise.

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.