Bug 109550

Summary: [regression][amd tahiti xt][vm fault] Rise of the Tomb Raider hangs the system
Product: DRI Reporter: Sylvain BERTRAND <sylvain.bertrand>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: major    
Priority: medium CC: rverschelde
Version: DRI git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg log
none
dmesg
none
dmesg with context fault none

Description Sylvain BERTRAND 2019-02-05 01:15:47 UTC
I cleared the game on 04/2018. Tested the game today with a full up to date stack, after playing hardly a few secs, I get a system hang, video settings to lowest. All components are from git repos of last sunday:
linux (amd-staging-drm-next), drm, llvm, mesa-gl, mesa-vulkan, xserver, xf86-video-amdgpu.
Cannot even get any logs from the hang.
Comment 1 Sylvain BERTRAND 2019-02-05 01:20:33 UTC
Created attachment 143294 [details]
xorg log
Comment 2 Sylvain BERTRAND 2019-02-05 01:21:43 UTC
Created attachment 143295 [details]
dmesg
Comment 3 Sylvain BERTRAND 2019-02-05 02:06:38 UTC
Created attachment 143296 [details]
dmesg with context fault

I did managed to get some logs
Comment 4 Sylvain BERTRAND 2019-02-10 17:12:03 UTC
linux(amd-staging-drm-next), drm, llvm, mesa (gl and vulkan), xserver, xf86-video-amdgpu from today git, still broken
Comment 5 Sylvain BERTRAND 2019-02-18 17:52:19 UTC
same, all git from yesterday, still broken
Comment 6 Sylvain BERTRAND 2019-02-24 20:01:33 UTC
git update from today: worse, it hangs right upon entering a saved game now.
Comment 7 Martin Peres 2019-11-19 09:12:38 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/691.

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.