From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104159] llvm 6.0svn: GPU fault/hang with r319975
Date: Thu, 07 Dec 2017 09:06:47 +0000 [thread overview]
Message-ID: <bug-104159-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 941 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104159
Bug ID: 104159
Summary: llvm 6.0svn: GPU fault/hang with r319975
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: haagch@frickel.club
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 136030
--> https://bugs.freedesktop.org/attachment.cgi?id=136030&action=edit
dmesg
RX 480, mesa master.
I only tried 4.15-rc2 with DC and drm-next-4.16 with DC and it happens on both.
With llvm 319975 (and 320007) I get a GPU hang every time I start firefox
nightly (in X).
With llvm 319882 it works fine.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2408 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:[~2017-12-07 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 9:06 bugzilla-daemon [this message]
2017-12-11 10:31 ` [Bug 104159] llvm 6.0svn: GPU fault/hang with r319975 bugzilla-daemon
2017-12-11 10:34 ` [Bug 104159] llvm 6.0svn: firefox " bugzilla-daemon
2017-12-11 10:47 ` bugzilla-daemon
2017-12-12 18:16 ` bugzilla-daemon
2017-12-12 18:17 ` bugzilla-daemon
2017-12-13 8:57 ` bugzilla-daemon
2017-12-14 8:18 ` 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-104159-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.