dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-111231-502-gFZqCVZeWm@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111231-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1169 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=111231

--- Comment #14 from deltasquared <ds2.bugs.freedesktop@gmail.com> ---
The apitrace no longer causes issues on my system either if I use
AMD_DEBUG=nodpbb . I also decided to try this on minetest and *so far* (bearing
in mind the issue was indetermistic in the first place, so a decisive ruling 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 artefacts
again.

I did try launching a minetest world with AMD_DEBUG=check_vm instead, however 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 eat
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.

[-- Attachment #1.2: Type: text/html, Size: 2073 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-07-29 19:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27 13:12 [Bug 111231] VM_L2_PROTECTION_FAULT bugzilla-daemon
2019-07-27 13:12 ` [Bug 111231] VM_L2_PROTECTION_FAULT when loading minetest on AMD ryzen 2200G integrated graphics bugzilla-daemon
2019-07-27 13:13 ` [Bug 111231] random VM_L2_PROTECTION_FAULTs when loading a world in " bugzilla-daemon
2019-07-27 13:15 ` bugzilla-daemon
2019-07-27 13:18 ` bugzilla-daemon
2019-07-27 13:20 ` bugzilla-daemon
2019-07-27 13:22 ` bugzilla-daemon
2019-07-27 13:24 ` bugzilla-daemon
2019-07-27 13:26 ` bugzilla-daemon
2019-07-27 13:30 ` bugzilla-daemon
2019-07-27 13:34 ` bugzilla-daemon
2019-07-27 13:34 ` bugzilla-daemon
2019-07-27 13:49 ` bugzilla-daemon
2019-07-27 13:50 ` bugzilla-daemon
2019-07-27 13:57 ` bugzilla-daemon
2019-07-27 13:59 ` bugzilla-daemon
2019-07-29 14:11 ` bugzilla-daemon
2019-07-29 15:56 ` bugzilla-daemon
2019-07-29 19:15 ` bugzilla-daemon [this message]
2019-08-05 13:16 ` bugzilla-daemon
2019-08-08 13:54 ` bugzilla-daemon
2019-08-10 13:18 ` 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-111231-502-gFZqCVZeWm@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).