NVIDIA / NVIDIA/open-gpu-kernel-modules

Frame presentation issue. All driver versions

Open
#417 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C
Stars
17.4k
Forks
1.9k
PR merge metrics
No merged PRs in 30d

Description

NVIDIA Open GPU Kernel Modules Version

525.60.11

Does this happen with the proprietary driver (of the same version) as well?

Yes

Operating System and Version

Arch Linux

Kernel Release

6.0.10-zen2-1-zen

Hardware: GPU

GPU 0: NVIDIA GeForce RTX 3060 Ti (UUID: GPU-ba73bc75-4c91-6012-1365-c8e673737f6b)

Describe the bug

issue example at 25% speed from 60fps game, instead of showing proper frame it jumps back to a frame which is 3 frames old and then continues with the most recent one.

This happens with and without compositor, with and without composition/fullcomposition pipeline in any app, browser, etc.
Without compositor and composition pipeline there is multiple tearing lines, in between which it is possible to see those outadet frames.
This also happens on both Xorg and Wayland (wlroots gl and vulkan).
This also happens on any driver version, both propriatary and open.

Only time this doesn't happen is when there is no compositor or compositionpipeline and app/game is in its native fullscreen mode and has vsync turned on and runs on vulkan.

nvidia-settings:
+Sync to VBlank
+Allow Flipping (without it there is tearing, which is constatly present at the top 1/7th part of app's window regardless of its size, same happens without compositor or composition pipeline if app/game has vsync on and in windowed/tiled mode)

To Reproduce

Good way to see it is to open any YT video like this and enjoy the stutters or also multiple tearing lines if no compositor or composition pipeline is present.

Bug Incidence

Always

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

This issue exists as long as I remember myself using Nvidia GPUs across different Linux systems.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the frame stutter with the linked GIF and YouTube example under the reported Arch Linux, kernel, GPU, driver, compositor, Xorg, and Wayland conditions. Review the attached nvidia-bug-report.log.gz and compare the listed presentation configurations; done would require identifying a specific presentation failure and a reproducible validation method.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
computer-graphics, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.