| Summary: | R600g: GPU hang occurs when trying to do GPU profile of Trine 2 apitrace trace | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | fossphreak |
| Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | major | ||
| Priority: | medium | CC: | vmerlet |
| Version: | unspecified | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
dmesg contents after GPU hangup occurred
dmesg contents after GPU hangup occurred - Linux kernel 3.11-rc5 |
||
Do you get the same hang with dpm disabled? Yes, I do. 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? Tested with Linux kernel 3.11-rc5 as well. Created attachment 84429 [details]
dmesg contents after GPU hangup occurred - Linux kernel 3.11-rc5
What do you mean by profiling? Is that something apitrace provides? -- 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.
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.