From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67888] New: R600g: GPU hang occurs when trying to do GPU profile of Trine 2 apitrace trace
Date: Thu, 08 Aug 2013 07:18:55 +0000 [thread overview]
Message-ID: <bug-67888-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 895 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67888
Priority: medium
Bug ID: 67888
Assignee: dri-devel@lists.freedesktop.org
Summary: R600g: GPU hang occurs when trying to do GPU profile
of Trine 2 apitrace trace
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: fossphreak@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: DRI CVS
Component: DRM/Radeon
Product: DRI
Created attachment 83811
--> https://bugs.freedesktop.org/attachment.cgi?id=83811&action=edit
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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2380 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-08-08 7:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 7:18 bugzilla-daemon [this message]
2013-08-08 13:23 ` [Bug 67888] R600g: GPU hang occurs when trying to do GPU profile of Trine 2 apitrace trace bugzilla-daemon
2013-08-10 8:55 ` bugzilla-daemon
2013-08-11 6:45 ` bugzilla-daemon
2013-08-22 5:59 ` bugzilla-daemon
2013-08-22 6:00 ` bugzilla-daemon
2014-01-23 12:25 ` bugzilla-daemon
2014-01-23 12:26 ` bugzilla-daemon
2019-09-18 19:05 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-67888-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox