From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 105425] 3D & games produce periodic GPU crashes (Radeon R7 370)
Date: Sat, 05 May 2018 14:24:29 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0615807525=="
Return-path:
Received: from culpepper.freedesktop.org (culpepper.freedesktop.org
[131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 823116E1D2
for ; Sat, 5 May 2018 14:24:29 +0000 (UTC)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============0615807525==
Content-Type: multipart/alternative; boundary="15255302692.E642B.7335"
Content-Transfer-Encoding: 7bit
--15255302692.E642B.7335
Date: Sat, 5 May 2018 14:24:29 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
https://bugs.freedesktop.org/show_bug.cgi?id=3D105425
--- Comment #69 from iive@yahoo.com ---
I'm really out of ideas...
Could you try using only the radeon kernel driver, just blacklist amdgpu on=
e.
See if the blender trace hangs and netconsole still doesn't give any warnin=
gs.
See if you can completely disable iommu, when using radeon.ko.
I've asked you at least 3 times to test "export mesa_glthread=3Dfalse", but=
you
never included it in your list of things you've tried.=20
Same for `export RADEON_THREAD=3Dfalse`.
I haven't asked you, but add `MESA_DEBUG=3Dflush` to the things to test.
Now, if you have run out of things to test. You can try a prolonged experim=
ent,
that might not even bring usable result.
If we had a case that hanged reliably, one thing to do is to locate the exa=
ct
operation that causes the hang.
So, you start `qapitrace` with the blender trace.=20
You then do a binary search for the frame that causes hang. It's done by
"Lookup State" at a frame number, it would replay the trace to that frame. =
You
start with the full range, let's say [0 - 10000], so you pick the frame from
the middle of that range, in this case frame#5000. If it hangs during repla=
y,
you use [0 - 5000] as interval, if it doesn't hang, then you use the other =
half
[5000-10000] (because the cause of hang mush be there). Then you pick the
middle of the new interval and repeat the experiment.
(e.g. [0 - 2500]; [1250 - 2500]; [1250 - 1875].
Once you locate the exact frame that could cause the first hang, you can do=
the
binary search, but this time on the draw operations inside that frame. It c=
an
help if you set:
"qapitrace->Trace->Options->Only_show_the_following_events->Draw_events".
Now, since crashing to you is kind of random, you might try to disable all
threaded options (all options from above) and run same lookup a dozen of ti=
mes.
If it crashes even once, then it crashes.
Also, be sure to write down the current range, as to not loose it at reboot.
I also strongly encourage you to at least try some other distribution,
something you can start from life-cd or something. Or build your own vanilla
kernel.
--=20
You are receiving this mail because:
You are the assignee for the bug.=
--15255302692.E642B.7335
Date: Sat, 5 May 2018 14:24:29 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://bugs.freedesktop.org/
Auto-Submitted: auto-generated
Comme=
nt # 69
on bug 10542=
5
from iive@yahoo.com
I'm really out of ideas...
Could you try using only the radeon kernel driver, just blacklist amdgpu on=
e.
See if the blender trace hangs and netconsole still doesn't give any warnin=
gs.
See if you can completely disable iommu, when using radeon.ko.
I've asked you at least 3 times to test "export mesa_glthread=3Dfalse&=
quot;, but you
never included it in your list of things you've tried.=20
Same for `export RADEON_THREAD=3Dfalse`.
I haven't asked you, but add `MESA_DEBUG=3Dflush` to the things to test.
Now, if you have run out of things to test. You can try a prolonged experim=
ent,
that might not even bring usable result.
If we had a case that hanged reliably, one thing to do is to locate the exa=
ct
operation that causes the hang.
So, you start `qapitrace` with the blender trace.=20
You then do a binary search for the frame that causes hang. It's done by
"Lookup State" at a frame number, it would replay the trace to th=
at frame. You
start with the full range, let's say [0 - 10000], so you pick the frame from
the middle of that range, in this case frame#5000. If it hangs during repla=
y,
you use [0 - 5000] as interval, if it doesn't hang, then you use the other =
half
[5000-10000] (because the cause of hang mush be there). Then you pick the
middle of the new interval and repeat the experiment.
(e.g. [0 - 2500]; [1250 - 2500]; [1250 - 1875].
Once you locate the exact frame that could cause the first hang, you can do=
the
binary search, but this time on the draw operations inside that frame. It c=
an
help if you set:
"qapitrace->Trace->Options->Only_show_the_following_events-&g=
t;Draw_events".
Now, since crashing to you is kind of random, you might try to disable all
threaded options (all options from above) and run same lookup a dozen of ti=
mes.
If it crashes even once, then it crashes.
Also, be sure to write down the current range, as to not loose it at reboot.
I also strongly encourage you to at least try some other distribution,
something you can start from life-cd or something. Or build your own vanilla
kernel.
You are receiving this mail because:
- You are the assignee for the bug.
=
--15255302692.E642B.7335--
--===============0615807525==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz
dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg==
--===============0615807525==--