https://bugs.kde.org/show_bug.cgi?id=478700
Bug ID: 478700
Summary: kwin_wayland + NVIDIA modesetting - Atomic commits
failed (and crash)
Classification: Plasma
Product: kwin
Version: 5.27.9
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: devillelethiba...@gmail.com
Target Milestone: ---
SUMMARY
When using ``kwin_wayland`` along with NVIDIA modesetting and a powered on AV
HDMI Receiver with the target display turned off, the kwin_wayland session
becomes laggy and grinds to a halt, and sometimes even crashes. A full
backtrace will be provided in the first comment under this bug report.
My computer has a NVIDIA 2080 Super, and it's connected to two powered video
outputs, and an unpowered one:
- powered: an ASUS VG27AQ monitor. Connected using DisplayPort.
- powered (kinda): a DENON HDMI AV Receiver, plugged using HDMI. The receiver
is then in turn connected to my TV via HDMI.
- unpowered: a Valve Index cable without the headset plugged in. Connected via
DisplayPort.
The system functions as intended on Windows : turning on and off the receiver
repeatedly does not incur any issues. However on Arch Linux with the latest-ish
KDE Plasma session and KDE Frameworks, whenever the receiver is connected, two
outputs are recognized: one named "DENON, Ltd. DENON-AVR" with the options to
use 4k@60Hz, 2160p@60Hz, 1080p@120Hz or below (60Hz maximum). And another one
with only 1440p@60Hz (???) with the name "Unknown 1". Whenever this output is
enabled, the problem happens.
STEPS TO REPRODUCE
1. Enable your system to use the NVIDIA modesetting driver
2. Have a HDMI receiver plugged in and turned on, but the target display turned
off.
3. Start the Plasma session under Wayland with NVIDIA modesetting enabled
OBSERVED RESULT
The system experiences horrible lag and slowdowns (the FPS plasma applet says
9FPS, but I suspect it's even lower than that) with 1+ second of delay to my
inputs, and the journal is filled with error messages of one of three kinds,
each one reported below:
```
kwin_wayland[PID]: kwin_wayland_drm: Atomic commit failed! Cannot allocate
memory
kwin_wayland[PID]: kwin_wayland_drm: Presentation failed! Cannot allocate
memory
kernel: [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID
0x00002d00] Failed to map NvKmsKapiMemory <address>
```
EXPECTED RESULT
It should work as intended: a.k.a. not induce this kind of
lag/unresponsiveness.
SOFTWARE/OS VERSIONS (copied from Settings > "About this system")
Operating System: Arch Linux
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.112.0
Qt Version: 5.15.11
Kernel Version: 6.6.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C37
System Version: 1.0
ADDITIONAL INFORMATION
It seems the first launch of kwin_wayland (before crashing) expects some
extensions from the EGL context that cannot be provided. See :
```
kwin_wayland_wrapper[PID]: No provider of eglCreateImageKHR found. Requires
one of:
kwin_wayland_wrapper[PID]: EGL_KHR_image
kwin_wayland_wrapper[PID]: EGL_KHR_image_base
```
This may be connected to the crash, or not...
--
You are receiving this mail because:
You are watching all bug changes.
