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: Wed, 07 Jun 2017 09:47:38 +0000 [thread overview]
Message-ID: <bug-101325-502-DzlAPos7Lz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101325-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1543 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101325
--- Comment #3 from Julien Isorce <julien.isorce@gmail.com> ---
This (In reply to Luke from comment #0)
>
> Then the log repeats a few hundred times the non-utf-8 character "\00"
> before it cuts off.
>
Hello, just some naive comments:
I also get some "^@" character after reboot sometimes, this happen because the
kernel is not functional enough to properly write all messages on disk. One
solution is to read these messages just before it freezes (does it freeze btw
?). For example ssh from another machine and type: "dmesg -w" before to start
the test. This will read from the ring buffer directly.
Though the real problem here is "radeon 0000:07:00.0: ring 4 stalled for more
than 10024msec" so it is not really worth to get more messages in this case.
Do you require to hard reboot after these gpu reset failures ? Alternatively
you can try radeon.hard_reset=1 as a kernel param to do a pci reset instead of
a soft reset.
Also maybe you could generate an apitrace (apt-get install apitrace, apitrace
trace /path/to/application ). Then if you reproduce the issue with apitrace
replay application.trace you can attach it to this bug.
About the amdgpu issue maybe you could try to build this kernel
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-4.9 (set
CONFIG_DRM_AMDGPU_SI=y in the .config) which contains some up to date fixes for
amdgpu (and radeon).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2616 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-06-07 9:47 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 [this message]
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
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-DzlAPos7Lz@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