search

ValveSoftware / Dota-2

Tracker for issues specific to Linux and Mac in the Reborn client. If you have a general issue or non-system-specific feature request please go to dev.dota2.com
472 stars 38 forks source link

Clinkz's Tar Bomb freezes AMD + Linux system #2634

Closed adrfantini closed 7 months ago

adrfantini commented 11 months ago

Your system information

Please describe your issue in as much detail as possible:

The whole system freezes shortly after Tar Bomb is cast.

Steps for reproducing this issue:

  1. Open demo mode with Shadow Shaman (I have not tested with other heroes though)
  2. Create enemy Clinkz
  3. Cast tar bomb
adrfantini commented 10 months ago

Does not happen anymore in the latest update

mamadgang commented 10 months ago

Does not happen anymore in the latest update

i encountered this bug today

mamadgang commented 10 months ago

i think valve dont want to fix it i have to find a solution

adrfantini commented 10 months ago

I'm closing this as it does not affect me anymore

adrfantini commented 10 months ago

It happens again :(

adrfantini commented 9 months ago

This still happens unfortunately @kisak-valve .

I also reinstalled the game, no changes. I monitored dmesg from SSH while this happened, and got no messages. Clean, sudden freeze after using tar bomb.

My only "solution" so far is... banning Clinkz :laughing:

adrfantini commented 9 months ago

Even after the latest update, this bug still exists. I am forced to abandon any game with Clinkz, and got low prio for the first time in my life because of it...

adrfantini commented 8 months ago

Breakthrough!

It also happens with snapfire's ulti! So it is connected with the round spit spell animation or something

adrfantini commented 8 months ago

It still happens. Can I do something to help debug?

adrfantini commented 7 months ago

It still happens. I've been able to get a dmesg output in one case in which the system managed to recover:

[Fri Mar 22 19:37:18 2024] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=292213, emitted seq=292215
[Fri Mar 22 19:37:18 2024] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process dota2 pid 3342 thread VKRenderThread pid 3370
[Fri Mar 22 19:37:18 2024] amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
[Fri Mar 22 19:37:18 2024] amdgpu 0000:03:00.0: amdgpu: MODE1 reset
[Fri Mar 22 19:37:18 2024] amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
[Fri Mar 22 19:37:18 2024] amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
[Fri Mar 22 19:37:18 2024] amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
[Fri Mar 22 19:37:18 2024] [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
[Fri Mar 22 19:37:18 2024] [drm] VRAM is lost due to GPU reset!
[Fri Mar 22 19:37:18 2024] [drm] PSP is resuming...
[Fri Mar 22 19:37:18 2024] [drm] reserve 0xa00000 from 0x81fd000000 for PSP TMR
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b3100 (59.49.0)
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: use vbios provided pptable
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
[Fri Mar 22 19:37:19 2024] [drm] DMUB hardware initialized: version=0x02020020
[Fri Mar 22 19:37:19 2024] [drm] kiq ring mec 2 pipe 1 q 0
[Fri Mar 22 19:37:19 2024] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[Fri Mar 22 19:37:19 2024] [drm] JPEG decode initialized successfully.
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow start
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow done
[Fri Mar 22 19:37:19 2024] [drm] Skip scheduling IBs!
[Fri Mar 22 19:37:19 2024] [drm] Skip scheduling IBs!
[Fri Mar 22 19:37:19 2024] [drm] Skip scheduling IBs!
[Fri Mar 22 19:37:19 2024] [drm] Skip scheduling IBs!
[Fri Mar 22 19:37:19 2024] [drm] Skip scheduling IBs!
[Fri Mar 22 19:37:19 2024] amdgpu 0000:03:00.0: amdgpu: GPU reset(2) succeeded!
[Fri Mar 22 19:37:19 2024] [drm] Skip scheduling IBs!
adrfantini commented 7 months ago

I'm starting to think this was a hardware issue. Closing