From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96271] TF2: GPU lockup on HD 7950
Date: Sun, 29 May 2016 21:15:24 +0000 [thread overview]
Message-ID: <bug-96271-502-r9CEEOufmr@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96271-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 594 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96271
--- Comment #2 from Stephen Liang <hi+freedesktop@stephenliang.pw> ---
One more thing, I did run an apitrace and replayed the apitrace to see if that
reproduces the hang. The replay didn't hang my machine initially but after
running it a 2-3 times, it was able to hang the machine. I would attach the
apitrace but it is 2-3 GB and the hang is several hundreds of thousands of
frames in (and it's not reproducible every time during replay, just sometimes).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1341 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-05-29 21:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 21:07 [Bug 96271] TF2: GPU lockup on HD 7950 bugzilla-daemon
2016-05-29 21:09 ` bugzilla-daemon
2016-05-29 21:15 ` bugzilla-daemon [this message]
2016-05-30 22:01 ` bugzilla-daemon
2016-05-30 22:14 ` bugzilla-daemon
2016-05-30 23:17 ` bugzilla-daemon
2016-05-30 23:29 ` bugzilla-daemon
2016-05-31 11:03 ` bugzilla-daemon
2016-06-01 3:51 ` bugzilla-daemon
2017-04-28 8:11 ` bugzilla-daemon
2017-04-28 18:46 ` bugzilla-daemon
2018-03-31 23:40 ` 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-96271-502-r9CEEOufmr@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