NVIDIA / NVIDIA/open-gpu-kernel-modules

Very slow 3D performance after a while

Open
#671 0 comments 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

555.58

Please confirm this issue does not happen with the proprietary driver (of the same version). This issue tracker is only for bugs specific to the open kernel driver.
  • I confirm that this does not happen with the proprietary driver package.
Operating System and Version

Arch Linux

Kernel Release

Linux Zen 6.9.7-zen1-1-zen

Please confirm you are running a stable release kernel (e.g. not a -rc). We do not accept bug reports for unreleased kernels.
  • I am running on a stable kernel release.
Hardware: GPU

GeForce GTX 1650

Describe the bug

After a while of running any 3D app, performance starts to be very slow.

To Reproduce

After first boot, just play some demanding game. After about 10 minutes it suddenly starts going slow, as seen in this screencast.

On future reboots it seems harder to reproduce, so maybe a heating management issue.

Restarting nvidia-persistenced solves it immediately (systemctl restart nvidia-persistenced.service).

Restarting plasma-kwin_x11, or login out, doesn't.

Bug Incidence

Sometimes

nvidia-bug-report.log.gz

nvidia-bug-report.log.gz

More Info

Lenovo IdeaPad Gaming 3 (81Y4 15IMH05)

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 reviewing the linked nvidia-bug-report.log.gz and reproducing the slowdown with a demanding 3D game on the stated Arch Linux and Linux Zen setup. Compare behavior before and after restarting nvidia-persistenced.service, and use the screencast and reproduction details to investigate the performance change. Done means the reported slowdown is explained and addressed or the issue is narrowed with supporting evidence.

Written by the indexing model from the issue text.

Assessment

Tech stack
arch-linux, c, linux
Domain
operating-systems, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.