[Bug 1999830] Re: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR*
** Description changed: - 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 or 3 changes the external screen freeze forever. Internal screen is still responsible. Get into journal : + 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 0x0100] Failed to map NvKmsKapiMemory 0x5> 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 KMS update and clutter-frame-clock part since they are always flooding the log. + 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. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999830/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999830] Re: external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR*
** Summary changed: - external screen freeze during display setting when using wayland + external screen freeze during display setting in wayland session: kernel: [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999830/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1999830] [NEW] external screen freeze during display setting when using wayland
Public bug reported: - 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' ``` 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 or 3 changes the external screen freeze forever. Internal screen is still responsible. Get into journal : ``` 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 0x0100] Failed to map NvKmsKapiMemory 0x5> 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 KMS update and clutter-frame-clock part since they are always flooding the log. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1999830 Title: external screen freeze during display setting when using wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999830/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967707] Re: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"
maybe related: > [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID > 0x0100] Failed to map NvKmsKapiMemory Failed to map NvKmsKapiMemory > 0x62c80dd4 Mutter 42.5 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1967707 Title: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967707] Re: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"
flooded with ` gnome-shell[3217]: (../clutter/clutter/clutter-frame- clock.c:332):clutter_frame_clock_notify_presented: code should not be reached` Then flooded with: > Page flip discarded: drmModeAtomicCommit: Invalid argument > Failed to post KMS update: drmModeAtomicCommit: Invalid argument Then external screen freeze but internal LCD works fine. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1967707 Title: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870597] Re: libinput says "your system is too slow"
The problem come back again after recent updates in ubuntu 20.04. System is stuttering when moving mouse and typing on keyboard: mutter3.36.9-0ubuntu0.20.04.2 xserver-xorg-input-libinput 0.29.0-1 libinput10:amd64 1.15.5-1ubuntu0.3 GNOME Shell 3.36.9 xorg-server 2:1.20.13-1ubuntu1~20.04.3 5.15.0-46-generic Lot of errors like following in journald: ``` /usr/lib/gdm3/gdm-x-session[4273]: (EE) client bug: timer event16 debounce short: scheduled expiry is in the past (-2ms), your system is too slow /usr/lib/gdm3/gdm-x-session[4273]: (EE) client bug: timer event16 debounce: scheduled expiry is in the past (-1ms), your system is too slow ``` Other DE does not have this issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1870597 Title: libinput says "your system is too slow" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825066] [NEW] gsd-xsettings have tons of error in syslog
Public bug reported: double monitors on nvidia card. I get tons of err like this: ``` Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist ``` ubuntu 18.04 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1825066 Title: gsd-xsettings have tons of error in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1825066/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
