From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 111231] random VM_L2_PROTECTION_FAULTs when loading a world in minetest on AMD ryzen 2200G integrated graphics Date: Mon, 29 Jul 2019 19:15:56 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0380907623==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id B1B416E1D7 for ; Mon, 29 Jul 2019 19:15:56 +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 --===============0380907623== Content-Type: multipart/alternative; boundary="15644277561.C0FcEEb7.30932" Content-Transfer-Encoding: 7bit --15644277561.C0FcEEb7.30932 Date: Mon, 29 Jul 2019 19:15:56 +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=3D111231 --- Comment #14 from deltasquared --- The apitrace no longer causes issues on my system either if I use AMD_DEBUG=3Dnodpbb . I also decided to try this on minetest and *so far* (b= earing in mind the issue was indetermistic in the first place, so a decisive rulin= g is near impossible) I have not re-incurred a crash. Interestingly, what I have noticed is that sometimes when minetest did not = lock up my system before, the loading bar would suffer mild graphical corruption (bits of the black border go white) - quite difficult to capture on camera = due to being so fleeting. So far with nodpbb I have yet to observe these artefa= cts again. I did try launching a minetest world with AMD_DEBUG=3Dcheck_vm instead, how= ever I somehow still managed to get a lock-up that way with similar graphical corruption as the bug description. Alas it seems my btrfs root decided to e= at my dmesg log file when I had to force power off, so unable to see if it was= the dreaded VM_L2_PROTECTION_FAULT again >:( --=20 You are receiving this mail because: You are the assignee for the bug.= --15644277561.C0FcEEb7.30932 Date: Mon, 29 Jul 2019 19:15:56 +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 # 14 on bug 11123= 1 from deltasquared 
The apitrace no longer causes issues on my system either if I =
use
AMD_DEBUG=3Dnodpbb . I also decided to try this on minetest and *so far* (b=
earing
in mind the issue was indetermistic in the first place, so a decisive rulin=
g is
near impossible) I have not re-incurred a crash.

Interestingly, what I have noticed is that sometimes when minetest did not =
lock
up my system before, the loading bar would suffer mild graphical corruption
(bits of the black border go white) - quite difficult to capture on camera =
due
to being so fleeting. So far with nodpbb I have yet to observe these artefa=
cts
again.

I did try launching a minetest world with AMD_DEBUG=3Dcheck_vm instead, how=
ever I
somehow still managed to get a lock-up that way with similar graphical
corruption as the bug description. Alas it seems my btrfs root decided to e=
at
my dmesg log file when I had to force power off, so unable to see if it was=
 the
dreaded VM_L2_PROTECTION_FAULT again >:(

You are receiving this mail because:
  • You are the assignee for the bug.
= --15644277561.C0FcEEb7.30932-- --===============0380907623== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVs --===============0380907623==--