From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101325] UE4Editor crash after pressing "play" with radeon southern island card (7850 HD)
Date: Mon, 07 Aug 2017 21:21:35 +0000 [thread overview]
Message-ID: <bug-101325-502-CkBYVVRT3T@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101325-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1499 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101325
MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sonichedgehog_hyperblast00@
| |yahoo.com
--- Comment #16 from MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com> ---
I did not expect to find another report on this. I've been struggling with what
appears to be the exact same crash for over 6 months. The difference for me is
that, this is not caused by Unreal Editor 4; It's triggered exclusively by the
KDE desktop, usually when alt-tab switching between windows. My machine is
rendered unresponsive approximately every 1 to 4 days.
I found this after googling parts of my own dmesg output, which seem to be
identical to what you've pasted in the first comment. I too have a RadeonSI
card, in my case a Radeon R7 370 from Gigabyte. My OS is openSUSE Tumbleweed
x64.
More information is available on my report, where I've posted my fair share of
logs and observations on the problem. We should first of all determine if this
is the same issue beyond doubt, then hopefully combining the information we've
both obtained can lead to a solution.
https://bugs.freedesktop.org/show_bug.cgi?id=100306
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3133 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 prev parent reply other threads:[~2017-08-07 21:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 1:19 [Bug 101325] UE4Editor crash after pressing "play" with radeon southern island card (7850 HD) bugzilla-daemon
2017-06-07 1:20 ` bugzilla-daemon
2017-06-07 1:20 ` bugzilla-daemon
2017-06-07 9:47 ` bugzilla-daemon
2017-06-08 1:47 ` bugzilla-daemon
2017-06-08 1:52 ` bugzilla-daemon
2017-06-08 2:26 ` bugzilla-daemon
2017-06-08 21:28 ` bugzilla-daemon
2017-06-10 2:16 ` bugzilla-daemon
2017-06-10 2:18 ` bugzilla-daemon
2017-06-13 16:30 ` bugzilla-daemon
2017-06-15 0:24 ` bugzilla-daemon
2017-06-15 1:08 ` bugzilla-daemon
2017-07-10 11:31 ` bugzilla-daemon
2017-07-10 11:46 ` bugzilla-daemon
2017-07-10 11:48 ` bugzilla-daemon
2017-08-07 21:21 ` bugzilla-daemon [this message]
2017-08-07 21:31 ` bugzilla-daemon
2017-08-07 21:37 ` bugzilla-daemon
2017-08-08 1:07 ` bugzilla-daemon
2017-08-08 1:36 ` bugzilla-daemon
2017-08-08 1:48 ` bugzilla-daemon
2017-08-08 23:35 ` bugzilla-daemon
2017-08-09 13:35 ` bugzilla-daemon
2017-08-26 23:26 ` bugzilla-daemon
2017-08-27 0:03 ` bugzilla-daemon
2019-06-25 1:30 ` bugzilla-daemon
2019-09-25 17:59 ` 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-101325-502-CkBYVVRT3T@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).