Bug 67888 - R600g: GPU hang occurs when trying to do GPU profile of Trine 2 apitrace trace
Summary: R600g: GPU hang occurs when trying to do GPU profile of Trine 2 apitrace trace
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-08 07:18 UTC by fossphreak
Modified: 2019-09-18 19:05 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg contents after GPU hangup occurred (198.22 KB, text/plain)
2013-08-08 07:18 UTC, fossphreak 		Details
dmesg contents after GPU hangup occurred - Linux kernel 3.11-rc5 (156.38 KB, text/plain)
2013-08-22 06:00 UTC, fossphreak 		Details
View All

Description fossphreak 2013-08-08 07:18:55 UTC 
Created attachment 83811 [details]
dmesg contents after GPU hangup occurred

I had used apitrace to trace Trine 2 OpenGL calls. When I tried to profile the trace, display corruption and GPU hangup occurred.
Comment 1 Alex Deucher 2013-08-08 13:23:09 UTC 
Do you get the same hang with dpm disabled?
Comment 2 fossphreak 2013-08-10 08:55:05 UTC 
Yes, I do.
Comment 3 fossphreak 2013-08-11 06:45:38 UTC 
It doesn't seem to be clear in the dmesg output - I am using the vanilla Linux 3.11-rc2 kernel. I can recompile the kernel with extra debugging options turned on if required.

Do you need any other information?
Comment 4 fossphreak 2013-08-22 05:59:00 UTC 
Tested with Linux kernel 3.11-rc5 as well.
Comment 5 fossphreak 2013-08-22 06:00:01 UTC 
Created attachment 84429 [details]
dmesg contents after GPU hangup occurred - Linux kernel 3.11-rc5
Comment 6 Marek Olšák 2014-01-23 12:25:44 UTC 
What do you mean by profiling? Is that something apitrace provides?
Comment 7 GitLab Migration User 2019-09-18 19:05:16 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/458.

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.