NVIDIA / NVIDIA/open-gpu-kernel-modules
Suboptimal power management at idle
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
515.57
Does this happen with the proprietary driver (of the same version) as well?
No
Operating System and Version
Gentoo
Kernel Release
5.18.8 (custom)
Hardware: GPU
NVIDIA GeForce RTX 3080
Describe the bug
Open driver has higher idle power usage than proprietary one. 44W vs 22W
nvidia-smi with proprietary driver reports:
Clocks
Graphics : 0 MHz
SM : 0 MHz
Memory : 405 MHz
Video : 555 MHz
Voltage
Graphics : 0.000 mV
nvidia-smi with open driver reports:
Clocks
Graphics : 210 MHz
SM : 210 MHz
Memory : 405 MHz
Video : 555 MHz
Voltage
Graphics : 750.000 mV
To Reproduce
I just have to switch from proprietary to open driver and run nvidia-smi to see the difference.
Bug Incidence
Always
nvidia-bug-report.log.gz
Can't share without sanitization and there is a lot to review.
More Info
I am using this card only for compute. It has connected display, but it isn't being used (excluded from Xorg, nvidia-smi reports Display Mode/Active as disabled), display is being driven by other card. Driver persistence is enabled.
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 comparison with nvidia-smi on the open and proprietary drivers using the reported RTX 3080, Gentoo system, and custom 5.18.8 kernel. Compare idle graphics and SM clocks, voltage, and power usage; done means identifying why the open driver remains at 210 MHz and 750 mV or documenting a matching fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- 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
- 30/100