Bug 11512

Summary:	r300 lockup with tuxsaver
Product:	Mesa	Reporter:	Eran Tromer <freedesktop2eran>
Component:	Drivers/DRI/r300	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	high	CC:	glisse
Version:	git
Hardware:	All
OS:	All
Whiteboard:
i915 platform:		i915 features:
Attachments:	xorg.conf resulting in lockup

Description Eran Tromer 2007-07-09 10:48:56 UTC

Running Xorg with r300 DRI on a ThinkPad with ATI Mobility Radeon X300, I get system lockups when running certain 3D applications, such as tuxsaver and google-earth.

This applies to all recent Xorg+Mesa+DRM versions, including current git.

The lockups seem to happen when the mouse moves. Adding
  Option      "Silkenmouse" "false"
to the x.org Device section eliminates the hangs with tuxsaver, and reduces their frequency with google-earth.

Xorg.conf attached.

Comment 1 Eran Tromer 2007-07-09 10:59:45 UTC

Created attachment 10637 [details]
xorg.conf resulting in lockup

Comment 2 Adam K Kirchhoff 2007-07-09 12:41:02 UTC

I saw this as well back in March.  Disabling SilkenMouse got it working for me consistently, so I've just left it disabled.  I had the bug tracked down to the merge of the vbo-0.2 branch.  You can read my posts to the dri-devel mailing list here:

http://marc.info/?l=dri-devel&m=117322250405189&w=3

I did not, at the time, try to track down the bug any further since I had a fix for it and just didn't have much free time.

It'd be interesting to see if you can test the mesa tree right before the merge with vbo-0.2 and right after the merge to see if you get the same results I did.

Comment 3 Adam Jackson 2009-08-24 12:27:15 UTC

Mass version move, cvs -> git

Comment 4 Maciej Cencora 2009-10-10 02:54:10 UTC

Can you try newer versions of libdrm, mesa and kernel radeon drm module?

Comment 5 Maciej Cencora 2010-03-07 13:18:40 UTC

Closing due to lack of user feedback.

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.