NVIDIA / NVIDIA/open-gpu-kernel-modules
GPU stays at maximum power state when using multiple monitor
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.4k
- Forks
- 1.9k
- PR merge metrics
- No merged PRs in 30d
Description
NVIDIA Open GPU Kernel Modules Version
565.77 (older versions are also affected)
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
6.12.1-arch1-1
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
NVIDIA GeForce RTX 2080 SUPER
Describe the bug
With certain combinations of monitor refresh rate, the GPU clocks won’t ramp down at idle (no app using the GPU open) even if I set:
- Powermizer mode to Adaptive or Auto in with both Xorg, Wayland and even TTY.
My GPU clocks never go bellow 1575 and 7750 Mhz at idle and nvidia-smi is reporting P0 in Perf section and 60W, it should be P8 and 22W at idle.
I have 3 monitors:
- Monitor 1: Alienware AW2725DF 2560x1440 360 Hz, Adaptive-Sync, DisplayPort
- Monitor 2: MSI MAG271CQR: 2560x1440 144 Hz, Adaptive-Sync, DisplayPort
- Monitor 3: Iiyama G2250HS: 1920x1080 75Hz, Adaptive-Sync, DisplayPort
The only configuration that doesn’t trigger the issue with more than one monitor is to only use monitor 2 at 144 Hz and monitor 3 at 75 Hz and disabling monitor 1 but this setup with VRR is causing another issue: ps://forums.developer.nvidia.com/t/monitors-literally-stutter-when-vrr-g-sync-is-enabled/256836
GPU doesn't even ramp down even if I am on a TTY console without any processes using GPU running.
To Reproduce
- Have a RTX 2080 SUPER
AND - Connect monitors 1, 2 and 3 and set them at 360 Hz, 144 Hz and 75 Hz respectively
OR - Connect monitors 1 and 2 and set them at 360 Hz and 144 Hz respectively
OR - Connect monitors 2 and 3 and set them at 144 Hz and 60 Hz respectively
Bug Incidence
Always
nvidia-bug-report.log.gz
More Info
- That issue behave as if i enable
disable_vrr_memclk_switchinnvidia-modesetmodule. - With this issue, the GPU doesn't even go to P2 state when CUDA apps are running.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the listed monitor and refresh-rate combinations on Arch Linux, then inspect nvidia-smi output and nvidia-bug-report.log.gz while idle and on a TTY. Done means affected multi-monitor setups return to P8 and about 22W at idle, while CUDA activity still reaches the expected performance state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- computer-graphics, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100