From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108350] amd-staging-drm-next-git witcher3 crashes and graphical oddities
Date: Sat, 13 Oct 2018 03:52:39 +0000 [thread overview]
Message-ID: <bug-108350-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 997 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=108350
Bug ID: 108350
Summary: amd-staging-drm-next-git witcher3 crashes and
graphical oddities
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: gort818@gmail.com
Created attachment 142008
--> https://bugs.freedesktop.org/attachment.cgi?id=142008&action=edit
Dmesg showing the gpu hang
On the first run of Witcher 3 with amd-staging-drm-next-git the game loads with
strange graphics, if I close the game and load again the gpu hangs and halts my
system.
Witcher 3 worked fine with linux 4.18.12
I am running arch linux with mesa-git and llvm-svn
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2432 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:[~2018-10-13 3:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-13 3:52 bugzilla-daemon [this message]
2018-10-13 3:54 ` [Bug 108350] amd-staging-drm-next-git witcher3 crashes and graphical oddities bugzilla-daemon
2018-10-13 4:17 ` [Bug 108350] amd-staging-drm-next-git witcher3 crashes and graphical oddities vega10 radv bugzilla-daemon
2018-10-15 15:47 ` bugzilla-daemon
2018-11-06 1:00 ` bugzilla-daemon
2018-11-23 19:42 ` bugzilla-daemon
2018-12-17 0:10 ` 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-108350-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.