Bug 110749 - [Vega 11] [amdgpu retry page fault VM_L2_PROTECTION_FAULT_STATUS] System lock up during playing Steam version of Saints Row 3
Summary: [Vega 11] [amdgpu retry page fault VM_L2_PROTECTION_FAULT_STATUS] System lock...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: highest blocker
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-24 01:20 UTC by Cyrax
Modified: 2019-11-19 09:28 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
contains files generated from output of dmesg, umr and "cat /sys/kernel/debug/tracing/trace" (4.62 MB, application/gzip)
2019-05-24 01:20 UTC, Cyrax 		no flags Details
Xorg log before starting the game (30.81 KB, text/x-log)
2019-05-24 02:03 UTC, Cyrax 		no flags Details
dmesg dump via journalctl -b -1 command (76.00 KB, application/gzip)
2019-05-28 06:07 UTC, Cyrax 		no flags Details
dmesg event umr dumps as usual (2.35 MB, application/gzip)
2019-06-12 04:57 UTC, Cyrax 		no flags Details
View All

Description Cyrax 2019-05-24 01:20:09 UTC 
Created attachment 144337 [details]
contains files generated from output of dmesg, umr and "cat /sys/kernel/debug/tracing/trace"

System hangs shortly (approximately few minutes) after starting playing Saints Row 3. Sound keeps playing but mouse et al doesn't work. Monitor turns itself off after few seconds.

Logging in the system via SSH fails. Only magickal SysRq + REISUB command helps.
Comment 1 Cyrax 2019-05-24 01:29:42 UTC 
OS : Arch Linux with linux-next-git kernel https://aur.archlinux.org/packages/linux-next-git

With latest libdrm-git, mesa-git and llvm-git packages installed.

local/linux-next-git 20190523.r0.gf48b97e163b3-1
    The Linux-next-git kernel and modules
local/linux-next-git-headers 20190523.r0.gf48b97e163b3-1
    Header files and scripts for building modules for Linux-next-git kernel

local/lib32-libdrm-git 2.4.98.r16.g922d9299-2
    Userspace interface to kernel DRM services, git 32-bit version
local/libdrm-git 2.4.98.r16.g922d9299-1
    Userspace interface to kernel DRM services, master git version

local/lib32-llvm-git 9.0.0_r317246.30905a375ea-1
    Collection of modular and reusable compiler and toolchain technologies (32-bit, git)
local/lib32-llvm-libs-git 9.0.0_r317246.30905a375ea-1
    Collection of modular and reusable compiler and toolchain technologies (32-bit, git)
local/llvm-git 9.0.0_r317246.30905a375ea-1
    LLVM development version. includes clang and many other tools
local/llvm-libs-git 9.0.0_r317246.30905a375ea-1
    runtime libraries for llvm-git

local/lib32-mesa-git 19.2.0_devel.111192.8d386e6eef8-1
    an open-source implementation of the OpenGL specification, git version
local/mesa-git 19.2.0_devel.111192.8d386e6eef8-1
    an open-source implementation of the OpenGL specification, git version
Comment 2 Cyrax 2019-05-24 02:03:12 UTC 
Created attachment 144338 [details]
Xorg log before starting the game
Comment 3 Cyrax 2019-05-28 06:07:14 UTC 
Created attachment 144359 [details]
dmesg dump via journalctl -b -1 command

It seems that the error message is different now when forcing Saints Row The Third to run only on two cores via command taskset --cpu-list 0,2

I'm wondering if VirtualBox or LXC containers is cause for this.
Comment 4 Cyrax 2019-06-12 04:57:24 UTC 
Created attachment 144516 [details]
dmesg event umr dumps as usual
Comment 5 wedens13 2019-07-23 05:57:58 UTC 
Seems like another case of https://bugs.freedesktop.org/show_bug.cgi?id=105251
Comment 6 Martin Peres 2019-11-19 09:28:57 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/799.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.