GPU Crashes when using Gamescope FSR on Steam Deck

Aperta
  • Qualcosa non va?
#3,020 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
12/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
linux
Ambito
computer-graphics, operating-systems

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
Nessun dato sulla lingua
Stelle
2.7k
Fork
89
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ValveSoftware/SteamOS

Tutte le issue di ValveSoftware/SteamOS

Issue simili

Altre issue su Computer Graphics

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.