NVIDIA / NVIDIA/open-gpu-kernel-modules

Xid 32 crashes with OLED monitor on Wayland (KDE Plasma) - RTX 2080 Ti

Open
#991 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
17.4k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

System Information

  • OS: CachyOS (Arch-based)
  • Kernel: 6.18.2-2-cachyos
  • Driver: nvidia-open 590.48.01
  • GPU: NVIDIA GeForce RTX 2080 Ti (TU102)
  • Desktop: KDE Plasma 6 (Wayland/KWin)
  • Monitor: ASUS XG27ACDMS OLED (2560x1440 @ 144Hz via DisplayPort 1.4)

Description

Random Xid 32 errors causing complete GPU context loss and black screen on KDE Plasma Wayland. The system becomes unresponsive and requires a hard reboot.

Key observation: This issue does NOT occur with an LCD monitor on the same system. The OLED monitor works flawlessly on Windows 11 at full refresh rate (280Hz).

Error Logs

NVRM: GPU at PCI:0000:09:00: GPU-4dfe1525-6c08-3c15-69b4-4141c28dfde6
NVRM: Xid (PCI:0000:09:00): 32, pid=1561, name=kwin_wayland, channel 0x00000059 intr1 00000008 HCE_DBG0 00000c00 HCE_DBG1 00000000
NVRM: Xid (PCI:0000:09:00): 32, pid=1561, name=kwin_wayland, channel 0x00000059 intr1 00000008 HCE_DBG0 00000c04 HCE_DBG1 8210c000

Followed by:

kwin_wayland: Create Context failed "EGL_BAD_CONTEXT"
kwin_wayland: QRhiGles2: Failed to create temporary context
kwin_wayland: Applying output configuration failed!

Steps to Reproduce

  1. Connect ASUS XG27ACDMS OLED monitor via DisplayPort
  2. Run KDE Plasma on Wayland with nvidia-open driver
  3. Use system normally - crash occurs randomly (sometimes after DPMS wake, sometimes during normal use)

Workarounds Attempted (none successful)

  • NVreg_PreserveVideoMemoryAllocations=1
  • NVreg_EnableGpuFirmware=0
  • Lower refresh rate (144Hz instead of 280Hz)
  • VRR disabled on monitor
  • DisplayPort 1.4 mode (not 2.0/2.1)

Additional Context

  • Secondary monitor (1080p LCD) connected to AMD RX 6400 on same system
  • Issue is specific to OLED + nvidia-open + Wayland combination
  • Crashes are random - not always tied to DPMS/suspend

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported Xid 32 and the following EGL_BAD_CONTEXT and QRhiGles2 errors, then reproduce using the ASUS OLED, NVIDIA GeForce RTX 2080 Ti, nvidia-open 590.48.01, and KDE Plasma Wayland setup described. Compare behavior with the LCD monitor and attempted workarounds. Done requires identifying a reproducible cause and preventing the GPU context loss and black screen.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
computer-graphics, desktop, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.