** Patch added: "mutter_46.2-1ubuntu0.24.04.9~oem1.debdiff" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2111698/+attachment/5880326/+files/mutter_46.2-1ubuntu0.24.04.9~oem1.debdiff
** Tags added: jira-somerville-2157 oem-priority ** Description changed: [Issue] Upstream report: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13759 glxgears -fullscreen does not stick to the refresh rate of the display on Arrow Lake systems. According to upstream report, applying the following MPs can fix the issue: * https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3958 * https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3999 - I've drafted a debdiff for this patch, but I'd like a review from + I've drafted a debdiff for this issue, but I'd like a review from whoever knows the internal workings of KMS. [Reproduce Steps] Ensure nothing else than terminal is running, then run `glxgears -fullscreen` on Intel Arrow Lake with integrated GPU [Expected Behavior] FPS should be close to the refresh rate of the display. [Actual Behavior] From the upstream report (with 75 Hz display): Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 375 frames in 5.0 seconds = 74.992 FPS 286 frames in 5.0 seconds = 57.136 FPS 221 frames in 5.0 seconds = 44.151 FPS 220 frames in 5.0 seconds = 43.953 FPS 216 frames in 5.0 seconds = 43.157 FPS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2111698 Title: On noble with Intel Arrow Lake systems, glxgears FPS is much less than the panel refresh rate To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2111698/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
