Game: RADV Vega 9 loses GPU during intro cinematic on Linux #1737
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#1737
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Reported on a DM to the bot on Discord from
kenokeefeLongshot version and channel
The attached log identifies the build as
v3.0.0-rc.8; the reporter stated v3.0.0. Exact channel/build provenance needs confirmation.What happened
The game crashes with
VK_ERROR_DEVICE_LOSTnear the end of the intro cinematic, after the title display. The reporter triedRX_VK_MESH_SHADERS=computein the build folder'slongshot_env.txt; it did not prevent the crash.Where / frequency
End of the intro cinematic after title display. Frequency not specified.
GPU and driver
AMD Radeon Graphics (RADV RENOIR), identified in the log; reporter describes the GPU as Vega 9, Vulkan 1.3, Mesa 26. Exact Mesa/driver version needs confirmation.
CPU, RAM, OS
Ryzen 7 5800H, 8 cores / 16 threads; Ubuntu 24.04.5 LTS. RAM not specified.
Logs
Attached
longshot_log.txtexcerpt:The complete log is attached to the report. Kernel/journal messages around the reset were not provided.
Still unknown
Exact release channel/build, exact Mesa driver version, RAM, how often it reproduces, kernel/journal messages around the GPU reset, and confirmation that the environment setting was in the active build's folder (the supplied path indicates
/home/<user>/Games/Longshot/rc/v3.0.0/longshot_env.txt).Files from the Discord report:
From a DM to the bot on Discord from
kenokeefe:Added Linux kernel messages around the GPU reset. The reporter requests that the computer hostname be anonymized; omitted the hostname
noether.From a DM to the bot on Discord from
kenokeefe:The reporter's added kernel messages confirm an AMDGPU graphics-ring timeout and successful ring reset while Longshot's Presentation Thread was active. Hostname omitted from the issue comment.
From a DM to the bot on Discord from
kenokeefe:The reporter reran with
RX_VK_CHECKOINTS=1and provided checkpoint output. Note the variable as typed isCHECKOINTS(notCHECKPOINTS); no confirmation was provided whether that is a typo or the setting was recognized. Output:From a DM to the bot on Discord from
kenokeefe:Reporter supplied the exact
longshot_env.txtcontents for the latest run:RX_VK_MESH_SHADERS=compute,RX_VK_MESH_NOCULL=2c56dc1006942f74, andRX_VK_CHECKPOINTS=1. This confirms the checkpoint setting is correctly spelled in that run; the prior run had the typoRX_VK_CHECKOINTS.