From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98196] [amdgpu SI] "gpu fault detect" in Tomb Raider
Date: Mon, 10 Oct 2016 15:06:12 +0000 [thread overview]
Message-ID: <bug-98196-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98196
Bug ID: 98196
Summary: [amdgpu SI] "gpu fault detect" in Tomb Raider
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: arek.rusi@gmail.com
Created attachment 127181
--> https://bugs.freedesktop.org/attachment.cgi?id=127181&action=edit
kernel log
Hi,
kernel - drm-next-4.9-wip + drm/amdgpu: disable CRTCs before teardown
mesa,libdrm,amdgpu,llvm form git/svn
This is not regression, this happened since dpm is workable.
GPU/VM faults appears in the menu, benchmark and gameplay as well but not
always.
One of trigger I found in gameplay is compfire.
Probably this problem doesn't performance impact, frame rate is the same as for
radeon.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2487 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-10-10 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 15:06 bugzilla-daemon [this message]
2016-10-10 15:19 ` [Bug 98196] [amdgpu SI] "gpu fault detect" in Tomb Raider 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-98196-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.