Bug 38478

Summary:	r600g fails to identify the screen refresh rate
Product:	Mesa	Reporter:	Stephen Kitt <steve>
Component:	Drivers/Gallium/r600	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	medium
Version:	git
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	Xorg log file [drm] lines from dmesg glxinfo

Description Stephen Kitt 2011-06-19 14:21:51 UTC

Created attachment 48172 [details] [review]
Xorg log file

Hi,

With the current git tree (up to 2fe39b46e73aea37152777fe11d489e0b1bc3f92) I'm only getting 10fps running glxgears on my HD4650; other 3D programs exhibit the same problem.

This is an improvement over previous versions of r600g on my system: before 7.10.3 the driver causes constant freezes, and 7.10.3 works but only at 0.8fps (constantly).

I'm attaching the Xorg log and [drm] info from my kernel log. Let me know what other information you need and I'll happily provide it!

Regards,

Stephen

Comment 1 Stephen Kitt 2011-06-19 14:22:50 UTC

Created attachment 48173 [details]
[drm] lines from dmesg

Comment 2 Alex Deucher 2011-06-19 14:47:05 UTC

Please attach the output of glxinfo.

Comment 3 Stephen Kitt 2011-06-19 14:51:40 UTC

Created attachment 48174 [details]
glxinfo

Here's the information provided by glxinfo.

Comment 4 Alex Deucher 2011-06-21 10:48:14 UTC

What kernel are you using?

Comment 5 Stephen Kitt 2011-06-21 11:41:50 UTC

I'm running Debian's linux-image-2.6.39-2-686-pae 2.6.39-2, which corresponds to 2.6.39.1.

Comment 6 Stephen Kitt 2011-08-13 16:06:22 UTC

I've just figured out what was going on - I noticed after rebooting (to check whether the bug was fixed in 3.0) that the IRQ used by my Radeon card was disabled. It's shared with some of the USB ports and an interrupt arrives before all the drivers have initialised correctly. Reloading the uhci-hcd module re-enables the interrupt and restores full functionality!

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.