Well I’d like to know if it is indeed just a reporting error how Nvidia have verified it, what process/tool is used to measure the clock speed and why said tool cannot be implemented into the drivers and/or released to put our minds at rest.
As it stands now, we only have their word and these words are very carefully phrased, from the Phoronix article I linked to in my original post…
At this point, I believe what you are seeing is strictly due to nvidia-settings reporting deficiencies, rather than the driver not taking proper advantage of the GPU clocks.
I think what is getting reported in nvidia-settings (both in the PowerMizer page and GPU3DClockFreqs) is the minimum value of each range.
You can be confident that the clock is certainly not running below what is reported in nvidia-settings, and it is likely running above that.
It doesn’t inspire confidence, just infers some shady goings on.