From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72685] New: [radeonsi] artifacts and/or GPU crashes with htile
Date: Fri, 13 Dec 2013 17:24:11 +0000 [thread overview]
Message-ID: <bug-72685-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1213 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=72685
Priority: medium
Bug ID: 72685
Assignee: dri-devel@lists.freedesktop.org
Summary: [radeonsi] artifacts and/or GPU crashes with htile
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: arek.rusi@gmail.com
Hardware: All
Status: NEW
Version: git
Component: Drivers/Gallium/radeonsi
Product: Mesa
Created attachment 90738
--> https://bugs.freedesktop.org/attachment.cgi?id=90738&action=edit
kernel log - system's hung
after this commit:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=8ee7370c9bed0be40c5d134f0b92eb3782c6b7e9
GPU's lost stability. I've tested it on unigine-valley/xonotic(ultimate)/some
wine apps.
Nothing segfaults,no logs, sometimes (with heavy load) gpu crashes with
standard dmesg info:
radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec etc.
kernel 3.13rc2 (dpm on by default) x86&x86_64
llvm 3.5 (svn-197173)
libdrm 2.4.50
GPU cape verde xt
is there any switch to turn off htile by now?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2770 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-12-13 17:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 17:24 bugzilla-daemon [this message]
2013-12-13 18:40 ` [Bug 72685] [radeonsi] artifacts and/or GPU crashes with htile bugzilla-daemon
2013-12-13 22:07 ` bugzilla-daemon
2013-12-13 22:10 ` bugzilla-daemon
2013-12-17 22:14 ` bugzilla-daemon
2013-12-18 2:31 ` [Bug 72685] [radeonsi hyperz] Artifacts in Unigine Sanctuary bugzilla-daemon
2013-12-18 22:58 ` bugzilla-daemon
2013-12-18 22:59 ` bugzilla-daemon
2013-12-18 23:00 ` bugzilla-daemon
2013-12-18 23:22 ` bugzilla-daemon
2013-12-18 23:27 ` bugzilla-daemon
2013-12-19 1:17 ` bugzilla-daemon
2014-01-22 12:02 ` bugzilla-daemon
2014-01-22 12:04 ` bugzilla-daemon
2014-01-22 13:15 ` bugzilla-daemon
2014-02-17 18:58 ` bugzilla-daemon
2014-05-17 14:06 ` bugzilla-daemon
2014-05-17 14:07 ` bugzilla-daemon
2014-05-19 3:54 ` bugzilla-daemon
2014-05-20 19:36 ` bugzilla-daemon
2014-05-22 21:19 ` bugzilla-daemon
2014-05-26 17:32 ` bugzilla-daemon
2014-08-11 6:30 ` bugzilla-daemon
2014-08-11 8:21 ` bugzilla-daemon
2014-08-11 8:33 ` bugzilla-daemon
2014-08-11 8:56 ` bugzilla-daemon
2014-08-16 16:58 ` bugzilla-daemon
2014-08-17 11:40 ` bugzilla-daemon
2014-08-17 14:00 ` bugzilla-daemon
2014-08-17 14:04 ` bugzilla-daemon
2014-08-17 14:45 ` bugzilla-daemon
2014-08-18 1:23 ` bugzilla-daemon
2014-08-24 13:44 ` bugzilla-daemon
2014-08-25 8:51 ` bugzilla-daemon
2014-09-01 19:32 ` 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-72685-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 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).