Bug 109445

Summary: Graveyard Keeper: Lockup in under 5min of play.
Product: DRI Reporter: Mike Mestnik <cheako+bugs_freedesktop_org>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED NOTOURBUG QA Contact:
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
URL: https://store.steampowered.com/app/599140/Graveyard_Keeper/
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
ar file containing glxinfo and Xorg.log
none
Renderdoc capture under DXVK none

Description Mike Mestnik 2019-01-23 22:00:06 UTC 
When I play graveyard keeper, native or via wine, my system locks-up(does not respond to ping or ssh, but dose continue to spin fan) after under 5min of play. 
 I can't even get to a point where i can save my progress. 

I'm able to load it under renderdoc, but am unable to create a capture.  Playing under renderdoc results in lower framerate, but little else seems different(still locks-up).

bnieuwen2uizen, on IRC, asked me to open a bug report.

ThinkPad E585
8GB RAM, 8GB Swap.
AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx
Manufacturer: LENOVO
Product Name: 20KV000YUS

Debian sid multi-arch
Graveyard Keeper is a 32bit Windows app, can't confirm native architecture.
Comment 1 Mike Mestnik 2019-01-23 22:01:16 UTC 
Created attachment 143210 [details]
ar file containing glxinfo and Xorg.log
Comment 2 Mike Mestnik 2019-01-24 06:14:25 UTC 
Created attachment 143217 [details]
Renderdoc capture under DXVK
Comment 3 Michel Dänzer 2019-01-24 09:07:48 UTC 
*** Bug 109444 has been marked as a duplicate of this bug. ***
Comment 4 Bas Nieuwenhuizen 2019-01-24 21:31:42 UTC 
since you mentioned your system does not respond to ping or ssh I wonder if it is actually not a gpu problem, but more generally being under load.

maybe try idle=nomwait? That solved regular lockup problems on my 2500U.

At the same time locking up consistently within 5 minutes sounds pretty bad, so I'm not sure this will fix it.
Comment 5 Bas Nieuwenhuizen 2019-01-24 21:32:08 UTC 
to clarify, try idle=nomwait on the kernel commandline.
Comment 6 Mike Mestnik 2019-01-25 04:35:05 UTC 
"idle=nomwait" fixed this, though later there was a problem on-resume.

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.