| Summary: | [Navi] Pathfinder: Kingmaker is causing a GPU hang: flip_done timed out error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Shmerl <shtetldik> | ||||
| Component: | DRM/AMDgpu | Assignee: | Default DRI bug account <dri-devel> | ||||
| Status: | RESOLVED MOVED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | not set | ||||||
| Version: | unspecified | ||||||
| Hardware: | x86-64 (AMD64) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Shmerl
2019-11-14 01:54:28 UTC
I experience the same in CS:GO and Shadow of the tomb raider. What I noticed is that the crash only happens when I move the mouse. Also it's somewhat related to the mouse pointer. For example starting a CS:GO game using console commands thus getting rid of the system pointer doesn't result in a crash, but as soon as I open the buy menu or bringing up steam overlay which shows the system pointer it crashes. Neither CS:GO or SOTTR has ingame pointers. Not sure how relevant mouse pointer type part is because there's some exception to this with other games that I tested based on this. GTA5 - ingame pointer - no crash Europa Universalis 4 - ingame pointer - no crash Train Simulator 2020 - no ingame pointer - crash exceptions: Kerbal Space Program - ingame pointer - crash Oxygen Not Included -no ingame pointer - no crash Workaround that worked for me is setting Option "SWCursor" "True" for xorg. Specs: GPU Sapphire Pulse RX 5700 XT Archlinux with mesa-git repo DE: KDE kernel 5.4-rc7 mesa-git 1:20.0.0_devel.117467.9e440b8d0b9-1 llvm-git 10.0.0_r331530.6ef63638cb8-1 I'll give it a test, thanks. Pathfinder: Kingmaker is using in game custom cursor for the reference and it's a Unity game. This bug looks similar to this one: https://bugzilla.kernel.org/show_bug.cgi?id=205169 2 possible workarounds to test: - do not run the game in fullscreen - revert this kernel commit: https://bugzilla.kernel.org/show_bug.cgi?id=205169#c10 (In reply to Pierre-Eric Pelloux-Prayer from comment #3) > - revert this kernel commit: > https://bugzilla.kernel.org/show_bug.cgi?id=205169#c10 Just for the reference: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=617089d5837a Thanks, I'll give reverting it a try later today. So that fix for the infinite loop introduced a regression? Is there a better way that prevents both? Just tested it, and can confirm, that reverting that commit indeed prevents the hang in Pathfinder: Kingmaker! Created attachment 145971 [details] [review] possible fix Does this patch help? (In reply to Alex Deucher from comment #6) > Created attachment 145971 [details] [review] [review] > possible fix > > Does this patch help? Just applied that patch on on top of latest 5.4-rc7+ and tested it. It prevents the hang in Pathfinder: Kingmaker! Thanks! (In reply to Alex Deucher from comment #6) > Created attachment 145971 [details] [review] [review] > possible fix > > Does this patch help? I tried it as well on 5.4-rc7 and fixed every game I mentioned(CS:GO, SOTTR, TS2020, KSP). I had this bug on tested kernels: 5.3.8, 5.3.9, 5.4.0-rc6, 5.4.0-rc7. I can confirm hangs occurred, when the cursor was moved after some time of inactivity (10-60 sec, depending on kernel version. 5.4.0-rc6 was the worst) in Firefox when watching fullscreen video (excluding 5.4.0-rc7), or in games. This bug was accompanied by another one - sluggish cursor, in 5.3 line with screen flickering at the cursor position, in 5.4 line barely visible, occurring every few seconds but without screen flickering, and feels inaccurate. I added this patch https://bugs.freedesktop.org/attachment.cgi?id=145971 on top of 5.4.0-rc7 and hangs are gone (thanks), but laggy cursor is still there. Sapphire Pulse RX 5700 XT Dell U2311Hb, 1920x1080 60.00Hz Kernel: 5.4.0-rc7 Mesa: 19.3.0-rc2 llvm: 9.0.0 -- 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/955. |
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.