Bug 2428514 - Kernel 6.18.3-200.fc43 causes VK_ERROR_DEVICE_LOST in vkd3d‑proton and a black‑screen hang when launching Cyberpunk 2077 on Intel Arc A770 (xe). Booting 6.17.12-300.fc43 fixes the issue; game launches normally and the error disappears.
Summary: Kernel 6.18.3-200.fc43 causes VK_ERROR_DEVICE_LOST in vkd3d‑proton and a blac...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 43
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Justin M. Forbes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-01-10 22:49 UTC by Greg Procunier
Modified: 2026-01-10 22:52 UTC (History)
14 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Greg Procunier 2026-01-10 22:49:21 UTC
System

  - Fedora 43, KDE Plasma on Wayland
  - GPU: Intel Arc A770 (DG2)
  - Driver: xe (forced via kernel cmdline)
  - Steam + Proton (tried Proton Experimental, Hotfix, GE; same issue on 6.18.3)

Regression window

  - Worked on kernel 6.17.12-300.fc43 (game launches normally).
  - Broken on kernel 6.18.3-200.fc43 (black screen on launch).
  - Reproduced on Jan 10, 2026; confirmed fixed immediately after rebooting into 6.17.12.

Symptoms

  - Launching Cyberpunk 2077 from Steam results in a black screen and hang.
  - Proton log shows repeated VK_ERROR_DEVICE_LOST and swapchain failures under vkd3d‑proton on 6.18.3.
  - Same game/proton configuration on 6.17.12 launches normally and no device‑lost errors appear.

Evidence

  - Bad kernel log (6.18.3) contains repeated:
      - vkd3d-proton: Device ... is lost (VK_ERROR_DEVICE_LOST)
      - swapchain present/acquire failures
  - Good kernel log (6.17.12) lacks VK_ERROR_DEVICE_LOST and only shows benign vkd3d warnings (pipeline cache misses).

Repro steps

  1. Boot kernel 6.18.3-200.fc43
  2. Launch Cyberpunk 2077 from Steam (any Proton version)
  3. Observe black screen/hang and VK_ERROR_DEVICE_LOST in Proton log
  4. Reboot into kernel 6.17.12-300.fc43, repeat launch
  5. Game starts normally

Expected
  Game launches successfully as it does on kernel 6.17.12.



Reproducible: Always


Note You need to log in before you can comment on or make changes to this bug.