From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96296] clpeak causes a GPU hang
Date: Wed, 01 Jun 2016 00:22:27 +0000 [thread overview]
Message-ID: <bug-96296-502-TFch2qKxHS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96296-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 585 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96296
--- Comment #3 from Grazvydas Ignotas <notasas@gmail.com> ---
OK so it's the memory bandwidth test that causes the GPU hang, --compute-dp
fails with "No double precision support! Skipped", as expected.
llvm 3.9 doesn't seemed to be released so I've build the trunk, but the hang is
still there. I've been able to capture the logs before the system dies,
attached.
BTW CLOVER_OUTPUT doesn't seem to be handled, did you mean CLOVER_DEBUG_FILE?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1329 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-06-01 0:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 20:47 [Bug 96296] clpeak causes a GPU hang bugzilla-daemon
2016-05-31 22:20 ` bugzilla-daemon
2016-06-01 0:21 ` bugzilla-daemon
2016-06-01 0:22 ` bugzilla-daemon [this message]
2016-06-06 17:59 ` bugzilla-daemon
2016-06-07 15:01 ` bugzilla-daemon
2017-01-27 15:01 ` bugzilla-daemon
2017-04-19 10:46 ` bugzilla-daemon
2017-04-19 10:48 ` bugzilla-daemon
2017-07-28 21:08 ` bugzilla-daemon
2017-07-30 11:47 ` bugzilla-daemon
2017-08-02 22:18 ` bugzilla-daemon
2017-11-04 23:17 ` [Bug 96296] [clover r600g juniper] " bugzilla-daemon
2019-09-18 19:21 ` 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-96296-502-TFch2qKxHS@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