NVIDIA / NVIDIA/nvidia-settings
nvidia-settings compiled with NVML_EXPERIMENTAL crashes when coolbits=8 is used
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 345
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Description
nvidia-settings: libXNVCtrlAttributes/NvCtrlAttributesNvml.c:1709: NvCtrlNvmlGetValidAttributeValues: Assertion 'ret2 == NvCtrlAttributeNotAvailable' failed.
I do not know how experimantal the NVML support is, but it seems that some of the attributes are not handled. nvidia-settings -verbose gives WARNING: Unhandled integer attribute GPUGraphicsClockOffsetAllPerformanceLevels (424) of GPU (0)
WARNING: Unhandled integer attribute GPUGraphicsClockOffset (409) of GPU (0)
WARNING: Unhandled integer attribute GPUMemoryTransferRateOffsetAllPerformanceLevels (425) of GPU (0)
WARNING: Unhandled integer attribute GPUMemoryTransferRateOffset (410) of GPU (0) so I believe those are the attributes to be handled. Those probaby also match the PowerMizer options when coolbits=8 is used.
Contributor guide
No contributing guide indexed for this repository
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 in libXNVCtrlAttributes/NvCtrlAttributesNvml.c around line 1709 and reproduce the assertion with nvidia-settings when coolbits=8 is used. Check the four unhandled attributes reported by nvidia-settings -verbose; done means the affected attributes are handled without the crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100