Bug 26160

Summary:	Frets on fire causes GPU lockup (rv670)
Product:	Mesa	Reporter:	Francisco J. Vazquez <dv>
Component:	Other	Assignee:	mesa-dev
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium
Version:	git
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Francisco J. Vazquez 2010-01-21 12:30:32 UTC

Sometimes, when browsing the song collection in Frets on Fire 1.3.110 song selection menu (it doesn't happen while playing, or in the main menu) the screen locks up. If I'm lucky I can Ctrl+Alt+F1 to vt1; if not I have to RSEIUB. dmesg shows this:

[drm:radeon_ib_get] *ERROR* radeon: IB(15:0x00000000101F1000:16056)
[drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
[drm:radeon_cs_ioctl] *ERROR* Failed to get ib !
[drm:radeon_ib_get] *ERROR* radeon: IB(15:0x00000000101F1000:16056)
[drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
[drm:radeon_cs_ioctl] *ERROR* Failed to get ib !
[drm:radeon_ib_get] *ERROR* radeon: IB(15:0x00000000101F1000:16056)
[drm:radeon_ib_get] *ERROR* radeon: GPU lockup detected, fail to get a IB
[drm:radeon_cs_ioctl] *ERROR* Failed to get ib !
(repeated many times)

Xorg.log doesn't show anything.

I can kill X, but if I try to restart it I get a garbled screen. I must reboot the computer to get a working X again.

This has been happening for some time (at least since January 4th) with mesa git. Mesa 7.7 doesn't present this problem. This is with kernel 2.6.32 and 2.6.33-rcX, libdrm git or 2.4.17 (it doesn't matter) and xf86-video-ati git. KMS enabled. Other games work ok.

Comment 1 Mike Mestnik 2012-04-29 08:40:47 UTC

Can you get an apitrace?  I'm facing a similar issue, however my ib test is passing.

Comment 2 Francisco J. Vazquez 2012-04-30 01:28:33 UTC

(In reply to comment #1)
> Can you get an apitrace?  I'm facing a similar issue, however my ib test is
> passing.

No, I can't. I don't have that card anymore...

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.