From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96296] clpeak causes a GPU hang
Date: Tue, 31 May 2016 20:47:42 +0000 [thread overview]
Message-ID: <bug-96296-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 936 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96296
Bug ID: 96296
Summary: clpeak causes a GPU hang
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: notasas@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
AMD JUNIPER (DRM 2.43.0 / 4.6.0)
Mesa 12.1.0-devel (git-3581812)
llvm-3.8 1:3.8-2ubuntu3
clpeak - https://github.com/krrishnarraj/clpeak.git
As soon as it starts it's float8 test (earlier ones run fine), the machine
locks up and does not recover. Perhaps it attempts to execute some fp64
instructions that are missing on Juniper?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2342 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 reply other threads:[~2016-05-31 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 20:47 bugzilla-daemon [this message]
2016-05-31 22:20 ` [Bug 96296] clpeak causes a GPU hang bugzilla-daemon
2016-06-01 0:21 ` bugzilla-daemon
2016-06-01 0:22 ` bugzilla-daemon
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.