Ubuntu
mutter package

Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"

Bug #1967707 reported by Daniel van Vugt
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mutter
New
Unknown
mutter (Ubuntu)
In Progress
Medium
Daniel van Vugt

Bug Description

Nvidia Wayland sessions sometimes flood the log with:

[ 13.105877] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached
[ 13.106163] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached
[ 13.112490] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached
[ 13.125302] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached
[ 13.142242] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached

I've been seeing the issue for months although it only seems to happen *after* something has gone wrong in mutter. Not by default.

See original description
Daniel van Vugt (vanvugt)
tags: added: jammy nvidia nvidia-wayland wayland-session
Changed in mutter (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

It appears the main cause of this is presently bug 1959888 when you log in with a secondary monitor on a secondary (Nvidia) GPU. So the log messages stop once you have that fix. Although I would still like to understand it better because that's the second bug I've seen trigger the same messages.

Changed in mutter (Ubuntu):
importance: Undecided → Medium
status: New → In Progress
no longer affects: nvidia-graphics-drivers-510 (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix proposed: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2358

description: updated
summary: Nvidia Wayland sessions sometimes flood the log with
- [clutter_frame_clock_notify_presented: code should not be reached]
+ "clutter_frame_clock_notify_presented: code should not be reached"
Daniel van Vugt (vanvugt)
Changed in mutter (Ubuntu):
status: In Progress → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in mutter:
status: Unknown → New
Revision history for this message
LittleBigBrain (braingateway) wrote :

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.

Revision history for this message
LittleBigBrain (braingateway) wrote (last edit ):

maybe related:
> [drm:__nv_drm_gem_nvkms_map.part.0 [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to map NvKmsKapiMemory Failed to map NvKmsKapiMemory 0x0000000062c80dd4

Mutter 42.5

https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1999830

Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

Comment #3 is bug 1968040, not this one.

Bug 1999830 may also help to reproduce the issue.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/2489 also shows there are other ways to trigger this warning.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

This should fix most cases of the log flood:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3115

tags: added: logspam
Daniel van Vugt (vanvugt)
Changed in mutter (Ubuntu):
status: Triaged → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.