*** This bug is a duplicate of bug 1967707 ***
https://bugs.launchpad.net/bugs/1967707
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1999830
Title:
external screen freeze during display setting in wayland session:
kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR*
Status in mutter package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-525 package in Ubuntu:
Confirmed
Bug description:
- ubuntu 22.04.1
- 5.15.0-56-generic
- mutter 42.5-0ubuntu1
- using gdm3
- nvidia Driver Version: 525.60.11 (nvidia-driver-525)
- prime select to on-demand
- 1 external display, 1 internal LCD
```
Added device '/dev/dri/card1' (nvidia-drm) using non-atomic mode setting.
Added device '/dev/dri/card0' (i915) using atomic mode setting.
Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card1'
Dec 15 22:13:34 gnome-shell[3203]: Created gbm renderer for '/dev/dri/card0'
Dec 15 22:13:34 gnome-shell[3203]: Boot VGA GPU /dev/dri/card0 selected as
primary
Dec 15 22:13:35 gnome-shell[3203]: Secondary GPU initialization failed
(Failed to create gbm_surface: No such file or directory). Falling back to
GPU-less >
Dec 15 22:13:35 gnome-shell[3203]: Using public X11 display :1, (using :2
for managed services)
Dec 15 22:13:35 gnome-shell[3203]: Using Wayland display name 'wayland-0'
```
0. open a terminal `journalctl -f`
1. Open the display setting, switch to join displays, choose external display
as primary.
2. try to change some settings like scale, position of the screen, refresh
rate, etc, then applay
3. repeat above step several times
After 2 changes the external screen freeze forever. Internal screen is still
responsible. On each `Apply` The journal recorded an kernel error about
nvidia_drm and flooded with clutter-frame-clock error.
```
Dec 15 22:18:52 gnome-shell[3203]: Failed to post KMS update:
drmModeAtomicCommit: Invalid argument
Dec 15 22:18:52 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit:
Invalid argument
Dec 15 22:19:25 gnome-shell[3203]: Failed to allocate onscreen framebuffer
for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory
Dec 15 22:19:25 kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]]
*ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to map NvKmsKapiMemory
0x000000005>
Dec 15 22:19:26 gnome-shell[3203]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
Dec 15 22:19:26 gnome-shell[3203]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
Dec 15 22:19:26 gnome-shell[3203]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
Dec 15 22:19:26 gnome-shell[3203]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
Dec 15 22:19:26 gnome-shell[3203]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
Dec 15 22:19:26 gnome-shell[3203]: Failed to post KMS update:
drmModeAtomicCommit: Invalid argument
Dec 15 22:19:26 gnome-shell[3203]: Page flip discarded: drmModeAtomicCommit:
Invalid argument
Dec 15 22:19:26 gnome-shell[3203]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
Dec 15 22:19:26 gnome-shell[3203]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
Dec 15 22:19:26 gnome-shell[3203]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
Dec 15 22:19:26 gnome-shell[3203]:
(../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented:
code should not be reached
```
one may ignore the drmModeAtomicCommit warning, they are always flooding the
log (though it may be related issue)
The clutter warning then flood the log forever till reboot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999830/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
