GPU Crashes when using Gamescope FSR on Steam Deck

未关闭
#3,020 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
12/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
linux

调研方向

The dmesg trace names the amdgpu driver on device 0000:04:00.0 and a gfx_0.1.0 ring timeout and reset, triggered by the gamescope-wl process when FSR or the Pixel filter is on. Start with the devcoredump at /sys/class/drm/card0/device/devcoredump/data and the GCVM protection fault status in the log. Done would mean a reproduction on a 720p-on-1080p setup and a narrowed cause, which needs driver and compositor knowledge.

由索引模型根据 Issue 内容生成。

描述

Your system information
  • Steam client version: 1793235415
  • SteamOS version: 20261023.100 (Stable)
  • Opted into Steam client beta?: Yes
  • Opted into SteamOS beta?: Yes (Main)
  • Have you checked for updates in Settings > System?: Yes
Please describe your issue in as much detail as possible:

Using FSR on any game for simple upscaling causes a GPU reset on the Steam Deck OLED. This also applies to the Pixel filter.
This can be easily triggered by playing a game at 720p on a 1080p display and turning on one of the Gamescope filters.

Steps for reproducing this issue:
  1. Start a game with a resolution lower than native.
  2. Enable FSR in the performance menu.
  3. Watch as the screen freezes and Steam resets.

dmesg output:

[ 7475.458494] amdgpu 0000:04:00.0: [gfxhub] page fault (src_id:0 ring:88 vmid:6 pasid:2201)
[ 7475.458510] amdgpu 0000:04:00.0:  Process gamescope-wl pid 38042 thread gamescope-xwm pid 38119
[ 7475.458515] amdgpu 0000:04:00.0:   in page starting at address 0x00000b0000060000 from client 0x1b (UTCL2)
[ 7475.458520] amdgpu 0000:04:00.0: GCVM_L2_PROTECTION_FAULT_STATUS:0x006012B0
[ 7475.458523] amdgpu 0000:04:00.0:      Faulty UTCL2 client ID: SQC (inst) (0x9)
[ 7475.458526] amdgpu 0000:04:00.0:      MORE_FAULTS: 0x0
[ 7475.458529] amdgpu 0000:04:00.0:      WALKER_ERROR: 0x0
[ 7475.458532] amdgpu 0000:04:00.0:      PERMISSION_FAULTS: 0xb
[ 7475.458535] amdgpu 0000:04:00.0:      MAPPING_ERROR: 0x0
[ 7475.458537] amdgpu 0000:04:00.0:      RW: 0x0
[ 7480.615985] amdgpu 0000:04:00.0: Dumping IP State
[ 7480.617045] amdgpu 0000:04:00.0: Dumping IP State Completed
[ 7480.617356] amdgpu 0000:04:00.0: [drm] AMDGPU device coredump file has been created
[ 7480.620276] amdgpu 0000:04:00.0: [drm] Check your /sys/class/drm/card0/device/devcoredump/data
[ 7480.620286] amdgpu 0000:04:00.0: ring gfx_0.1.0 timeout, signaled seq=296670, emitted seq=296671
[ 7480.620293] amdgpu 0000:04:00.0:  Process gamescope-wl pid 38042 thread gamescope-xwm pid 38119
[ 7480.620297] amdgpu 0000:04:00.0: Starting gfx_0.1.0 ring reset
[ 7480.620424] amdgpu 0000:04:00.0: Ring gfx_0.1.0 reset succeeded
[ 7480.620430] amdgpu 0000:04:00.0: [drm] device wedged, but no recovery needed
主要语言
没有语言数据
星标
2.7k
派生
89
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ValveSoftware/SteamOS 的其他 Issue

查看 ValveSoftware/SteamOS 的全部 Issue

相似的 Issue

更多 Computer Graphics Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。