While you're here, please consider supporting GamingOnLinux on:
Patreon,
Liberapay or
PayPal Donation.
We have no adverts, no paywalls, no timed exclusive articles. Just good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!



We have no adverts, no paywalls, no timed exclusive articles. Just good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
Livestreams & Videos
Community Livestreams
- Monday Tactics: „Partisans 1941“ (Proton)
2021-03-08 21:00:00
Popular this week
- Steam Link app now available for the Linux desktop
- Valve makes further improvements to Steam Link and Remote Play Together
- Transport Tycoon Deluxe reimplementation OpenTTD has a fresh Beta with OpenGL
- Building a Retro Linux Gaming Computer - Part 1: Dumpster Diving
- The tenth Norse world sure is busy as Valheim hits 5 million sold
Contact
Latest Comments
-
The February 2021 round-up here's our top articles
- Liam Dawe -
Brace yourself, Winter is coming to Crusader Kings III
- ajgp -
Another Proton Experimental update is out improving VR …
- Beamboom -
Skullgirls: Annie goes up in Beta along with the Season…
- dvd -
Steam Link app now available for the Linux desktop
- sgtnasty369 - See more comments
Latest Forum Posts
View PC info
Last edited by The_Aquabat on 23 January 2021 at 9:49 am UTC
View PC info
View PC info
View PC info
ene 20 17:59:34 Stormbreaker kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Golf With Your pid 4822 thread Golf With :cs0 pid 4831
ene 20 17:59:34 Stormbreaker kernel: amdgpu 0000:07:00.0: amdgpu: GPU reset begin!
ene 20 17:59:34 Stormbreaker kernel: ------------[ cut here ]------------
ene 20 17:59:34 Stormbreaker kernel: WARNING: CPU: 2 PID: 102 at drivers/gpu/drm/amd/amdgpu/../display/dc/dcn20/dcn20_resource.c:3240 dcn20_validate_bandwidth_fp+0xb9/0xd0 [amdgpu]
ene 20 17:59:34 Stormbreaker kernel: Modules linked in: ccm binfmt_misc dm_crypt nls_iso8859_1 intel_rapl_msr intel_rapl_common edac_mce_amd snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_c>
ene 20 17:59:34 Stormbreaker kernel: iommu_v2 gpu_sched i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops crc32_pclmul cec drm i2c_piix4 r8169 ahci realtek libahci wmi gpio_amdpt >
ene 20 17:59:34 Stormbreaker kernel: CPU: 2 PID: 102 Comm: kworker/2:1 Not tainted 5.10.0-pf8 #1
ene 20 17:59:34 Stormbreaker kernel: Hardware name: Gigabyte Technology Co., Ltd. AB350-Gaming/AB350-Gaming-CF, BIOS F50d 07/02/2020
ene 20 17:59:34 Stormbreaker kernel: Workqueue: events drm_sched_job_timedout [gpu_sched]
ene 20 17:59:34 Stormbreaker kernel: RIP: 0010:dcn20_validate_bandwidth_fp+0xb9/0xd0 [amdgpu]
ene 20 17:59:34 Stormbreaker kernel: Code: 48 89 de 31 d2 f2 0f 11 83 50 26 00 00 e8 6f 23 00 00 84 c0 74 14 80 bb 0c 1f 00 00 00 74 0b c6 83 0c 1f 00 00 00 b0 01 eb 02 <0f> 0b 4c 89 bb 50 26 00 00 5b 41 5e 4>
ene 20 17:59:34 Stormbreaker kernel: RSP: 0018:ffffbbe8c0493ba0 EFLAGS: 00010246
ene 20 17:59:34 Stormbreaker kernel: RAX: 00000000c0493b01 RBX: ffff9e6662360000 RCX: 000000000000672d
ene 20 17:59:34 Stormbreaker kernel: RDX: 000000000000672c RSI: 18fd252ab201a4c9 RDI: ffff9e6540043300
ene 20 17:59:34 Stormbreaker kernel: RBP: ffffbbe8c0493bb8 R08: ffffe6054412f800 R09: 00000000000301a0
ene 20 17:59:34 Stormbreaker kernel: R10: 0000000000004000 R11: 0000000000000006 R12: ffff9e6662360000
ene 20 17:59:34 Stormbreaker kernel: R13: 0000000000000050 R14: ffff9e6555c20000 R15: 4079400000000000
ene 20 17:59:34 Stormbreaker kernel: FS: 0000000000000000(0000) GS:ffff9e6772880000(0000) knlGS:0000000000000000
ene 20 17:59:34 Stormbreaker kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
ene 20 17:59:34 Stormbreaker kernel: CR2: 0000156d6dd3e000 CR3: 000000023f95e000 CR4: 00000000003506e0
ene 20 17:59:34 Stormbreaker kernel: Call Trace:
ene 20 17:59:34 Stormbreaker kernel: dcn20_validate_bandwidth+0x2a/0x40 [amdgpu]
ene 20 17:59:34 Stormbreaker kernel: dc_validate_global_state+0x304/0x330 [amdgpu]
ene 20 17:59:34 Stormbreaker kernel: ? dc_resource_state_copy_construct+0x30/0x190 [amdgpu]
ene 20 17:59:34 Stormbreaker kernel: dm_suspend+0x147/0x200 [amdgpu]
ene 20 17:59:34 Stormbreaker kernel: ? amdgpu_device_set_cg_state+0xa4/0xf0 [amdgpu]
ene 20 17:59:34 Stormbreaker kernel: amdgpu_device_ip_suspend_phase1+0x75/0xc0 [amdgpu]
ene 20 17:59:34 Stormbreaker kernel: amdgpu_device_pre_asic_reset+0x332/0x380 [amdgpu]
ene 20 17:59:34 Stormbreaker kernel: amdgpu_device_gpu_recover+0x497/0xbd0 [amdgpu]
ene 20 17:59:34 Stormbreaker kernel: amdgpu_job_timedout+0x103/0x150 [amdgpu]
ene 20 17:59:34 Stormbreaker kernel: drm_sched_job_timedout+0x69/0xf0 [gpu_sched]
ene 20 17:59:34 Stormbreaker kernel: process_one_work+0x228/0x3b0
ene 20 17:59:34 Stormbreaker kernel: worker_thread+0x28d/0x4c0
ene 20 17:59:34 Stormbreaker kernel: kthread+0x136/0x140
ene 20 17:59:34 Stormbreaker kernel: ? process_one_work+0x3b0/0x3b0
ene 20 17:59:34 Stormbreaker kernel: ? kthread_blkcg+0x30/0x30
ene 20 17:59:34 Stormbreaker kernel: ret_from_fork+0x22/0x30
ene 20 17:59:34 Stormbreaker kernel: ---[ end trace 610cb3a6fd409030 ]---
ene 20 17:59:35 Stormbreaker kernel: amdgpu 0000:07:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
ene 20 17:59:35 Stormbreaker kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KGQ disable failed
ene 20 17:59:35 Stormbreaker kernel: amdgpu 0000:07:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
ene 20 17:59:35 Stormbreaker kernel: [drm:gfx_v10_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed
ene 20 17:59:35 Stormbreaker kernel: [drm:gfx_v10_0_cp_gfx_enable [amdgpu]] *ERROR* failed to halt cp gfx
View PC info
ring gfx_0.0.0 timeout
seems it's a well known bug on Mesa some suggested to use AMD_DEBUG=nongg. Didn't work for me. I think I will have to resort to force this game to use Proton.
View PC info
View PC info
mesa devs know of this bug since a long time, it's yet not know if it might be a hardware issue, meaning that some navi cards could be deffective.
from the bug report:
View PC info
the actual devs are actively recommending to use proton if you have issues.
https://steamcommunity.com/app/431240/discussions/2/2930112548441414710/
View PC info
Unfortunately I think this is a long standing bug on Navi hardware that won't get fixed in the near future, so I hope my advice of trying to run this game with Proton is useful for someone on navi.