From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98541] [bisected] gpu hang
Date: Thu, 03 Nov 2016 08:52:34 +0000 [thread overview]
Message-ID: <bug-98541-502-2d6wfOA3tK@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98541-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 551 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98541
--- Comment #5 from Nicolai Hähnle <nhaehnle@gmail.com> ---
That's odd. As an alternative, could you please provide a log with
R600_DEBUG=vs,tcs,tes,gs,ps,cs both before (without hang) and after (with hang)
the problematic commit. Also run with GALLIUM_DDEBUG=pipelined; after the hang,
you should get a message about the hang being detected as well as a file in
~/ddebug_dumps/ that ought to be useful. Thanks!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1274 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-11-03 8:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 8:39 [Bug 98541] [bisected] gpu hang bugzilla-daemon
2016-11-02 9:04 ` bugzilla-daemon
2016-11-02 9:13 ` bugzilla-daemon
2016-11-02 11:17 ` bugzilla-daemon
2016-11-03 2:29 ` bugzilla-daemon
2016-11-03 8:52 ` bugzilla-daemon [this message]
2016-11-16 13:32 ` bugzilla-daemon
2016-11-16 13:39 ` bugzilla-daemon
2016-11-16 14:46 ` bugzilla-daemon
2016-11-16 14:58 ` bugzilla-daemon
2016-12-06 7:30 ` bugzilla-daemon
2016-12-08 7:24 ` 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-98541-502-2d6wfOA3tK@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;
as well as URLs for NNTP newsgroup(s).